Hello. After burning Efuse to the Nanopi Neo Core, I can't boot from emmc. It works from the SD card, so I try loading everything into emmc: spl, uboot. But spl doesn't find u-boot, as far as I understand. I'm using the u-boot and dts config from the Nanopi Neo, with some edits to mmc2, since it's not available in the Neo. U-Boot SPL 2024.07 (Feb 25 2026 - 15:51:42 +0300) DRAM: 512 MiB Trying to boot from MMC1 CMD_SEND:0 ARG 0x00000000 MMC_RSP_NONE CMD_SEND:8 ARG 0x000001aa RET -110 CMD_SEND:55 ARG 0x00000000 RET -110 CMD_SEND:0 ARG 0x00000000 MMC_RSP_NONE CMD_SEND:1 ARG 0x00000000 RET -110 Card did not respond to voltage select! : -110 spl: mmc init failed with error: -95 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ###

Well don't know exactly how the board got bricked, but I would guess the armbian-config did not flash the SPI right and somehow my SD card got screwed too. armbian-install did it right. I was able to get it back by using the rkdeveloptool tool from my mac mini. For whoever runs into this problem this is what I had to do: Get a usb-c cable connected to the "DP Display Port" and connect to another machine to troubleshoot, disconnect the power source before you do this. Before you connect the cable, press the Maskrom button. This should allow you to access the SPI from your troubleshooting machine. I played around with the windows tool RKDevTool with no luck. I ended up compiling rkdeveloptool in my mac mini m4 and this one did work. Anywho, once you have the board hooked up and in Maskrom mode, you need to get your hands on the SPI Loader *.bin. It's somewhere in the resources page of radxa. The one I used is rk3588_spl_loader_v1.15.113.bin. After this you flash the board with the following commands: The following command should show you the board info and confirm it's connected in Maskrom mode. ./rkdeveloptool ld ./rkdeveloptool db rk3588_spl_loader_v1.15.113.bin ./rkdeveloptool ef ./rkdeveloptool rd This allowed me to boot aging from SD, even though I had to reflash the SD because somehow it also went bad. Not sure if it was because of all the testing or armbian-config screwed it up. After all this, I was booting again, and I did an armbian-install to move again the content of the SD to the nvme. I again, did an install/update MTD flash and boot from MTD first and this time around it all worked. I'm able to boot from SD first and if not SD is present it boots from NVME.

booting from sd should work even with proper mtd in place. Get usb uart adapter and provide boot logs.

@Nick A Thank you very much. Newbies will try. 😅

Hello! Are there any plans for a stable minimal/IOT release for the Rock 4D, and if so, what’s the timetable? Thanks!