BBSHD still runs but no software/display can read or write controller anymore – possible UART/firmware corruption?
I’m trying to diagnose a weird BBSHD issue and I’m running out of ideas.
The motor still powers on and the bike runs normally, but I can no longer communicate with the controller through ANY software or display-based tuning method.
What happened:
Any help from people who’ve actually recovered a “runs normally but unreadable” BBSHD would be hugely appreciated.
I’m trying to diagnose a weird BBSHD issue and I’m running out of ideas.
The motor still powers on and the bike runs normally, but I can no longer communicate with the controller through ANY software or display-based tuning method.
What happened:
- I was modifying settings on the BBSHD
- Afterward, communication with the controller stopped working
- Since then, no tool can properly read/write the controller
- Multiple programming attempts
- Different software:
- Bafang Config Tool
- Speeed app
- EggRider
- other tuning/config apps
- Different USB ports/computers
- Tried disconnecting peripherals
- Bike still runs normally
- Display still powers on
- Motor still functions
- EggRider also cannot read/write the controller
- Programming cable also cannot read/write the controller
- This makes me think it’s not just a display issue
- No permanent error codes on display
- Controller is responsive enough to operate the motor normally
- Does this sound more like:
- corrupted firmware/EEPROM
- damaged UART communication section
- partially bricked MCU
- something else?
- Is there an actual recoverable stock BBSHD firmware available anywhere?
- not config files, actual firmware
- Has anyone recovered a controller in this exact state using:
- STC ISP
- Daniel Nilsson firmware tools
- bootloader recovery
- UART reflashing?
- If both EggRider and programming cable fail to communicate, does that strongly point toward hardware failure?
Any help from people who’ve actually recovered a “runs normally but unreadable” BBSHD would be hugely appreciated.