Event
RDK X5 repeatedly reports errors and fails to boot after flashing the image; community recommends checking power supply and reflashing miniboot
1 reports · 1 sources
After an RDK X5 user flashed the official image, the development board failed to boot. The D-Robotics developer community replied that the logs still stop at the BOOTROM/BL1/BL2 stage, indicating that the image on the SD card has not yet been read. There is currently no confirmed final resolution to the issue. The troubleshooting suggestions given by the community are: first disconnect the chassis wiring and peripherals, switch to the official required 5V/5A adapter for power supply via Type-C, and observe the indicator lights; if the bare board still prints logs looping from the beginning, then XBurn must be used to reflash the miniboot firmware in the onboard NAND via Serial+USB with xmodem_fastboot.
Report timeline
- RDK X5 repeatedly errors and fails to boot after image flashing; community investigation points to power supply and miniboot
An RDK X5 user cannot boot after flashing the official image, and community replies note that the log is still stuck at the BOOTROM/BL1/BL2 stage, meaning the SD card image has not yet been read. Troubleshooting suggestions: first disconnect the chassis wiring and peripherals, switch to the official-required 5V/5A adapter for Type-C power, and observe the indicator light; if the bare board still prints logs looping from the start, use XBurn with Serial+USB and xmodem_fastboot to reflash the miniboot firmware in the onboard NAND.
D-Robotics Developer Community ·