Seems I’ve gone a bit too far with firmware and bricked my board. After compiling and flashing a mainline U-Boot directly to the SPI NOR flash mtdblock0, the board fails to boot into any OS image from the SD card or eMMC.
To resolve this, I have attempted the following:
- Clearing the SPI NOR Flash: Attempted to erase the SPI flash using
rkdeveloptool
in Maskrom mode, following the procedures outlined in the official Radxa documentation. Unfortunately, this did not resolve the issue. Relatively certain in the ROCK5 ITX this only operates on eMMC - Flashing eMMC: Tried flashing both the SPI image and the latest Bookworm KDE image to the eMMC. In line with the observation above, while the flashing process completes successfully, the board still fails to boot.
I have thoroughly reviewed the available documentation and community forums but have not found a solution. Looking for help with the following:
- Manual SPI NOR Flash Erasure: Is there a hardware method, such as specific jumper settings, to manually clear or disable the SPI NOR flash to restore boot functionality?
- Force Boot Order: Does some way to force the boot sequence to ignore the SPI flash and use eMMC or SD card by default exist?
- Alternative Recovery Methods: Are there other recommended procedures to recover the board from this state? Perhaps a way to force
rkdeveloptool
to flash to a specific block device?