Daniel Ritchie

I wonder if this is related. Discord user @SvaenGheld figured out this can be resolved by upgrading the firmware (3.9 -> 3.10 if I recall): https://discord.com/channels/1216765309076115607/1237741463832363039/1378393049146589267

Initially I added `ENABLE_EXTENSIONS=mesa-vpu` but saw in the [docs](https://docs.armbian.com/Developer-Guide_Build-Switches/#advanced) that ENABLE_EXTENSIONS are expected to be build time options, meaning any other extensions will wipe out this change and cause issues...

I took more time to understand the conflicts here, and I am no longer confident that there is a simple/easy path to enabling the hardware. Initially I was of the...

FYI here's a first pass... leaving here for reference but happy to put more work into communicating / integrating options (ideally I'd like a selector for one of the options,...

Thank you @khanh-it. I suspect there could be more configurations that have not made their way into formal support but yours is at least one potential "everything" so I have...

FYI - main hackathon page ref is broken too "Follow the tutorial here" about half way down the page. https://huggingface.co/LeRobot-worldwide-hackathon

I think there is not a lot for this that isn't very low level, but it would be a great project addition. Can you be more clear about the specifics...

As an observation, board rev V0.1 (beta, 2025/09/05) shows voltage at 6.8-6.9v with the 6.3v power supply (actual measured output is 7.22v) "present_input_voltage": [69, 0] ...and with the 7.3v power...

I published a basic utility to check what your motors are reporting. Git clone: `brainwavecollective/reachy-mini-motor-controller` and... ``` git checkout 589-debug cd reachy-mini-motor-controller/tools/motor_dump cargo run -- COM6 my-motor-dump 10 11 12...

I'm guessing this could be related to #589; you'll need to pull the fault codes from the motors to confirm why they have stopped responding.