Radxa rock-3c stuck at login & no hdmi

[socrates018]

Hello, I just flashed the latest minimal img  from the github releases (Armbian_community_26.2.0-trunk.7_Rock-3c_trixie_current_6.12.58_minimal.img.xz) but I see no output on hdmi and it gets stuck at login, nothing I type works.

[eselarm]

Good that you posted serial console output. A bit more and text (starting at power on when U-Boot starts) would be clearer, but I think the 2 top lines with 'Android' mentioned already indicate what is wrong I think; ROCK3C has SPI-flash where also the bootloader (U-Boot usually) can be stored and this has priority over SD-card bootloader. So it seems older/incompatible Android U-Boot variant in the SPI-flash loads Linux and as you use mainline Linux kernel, this won't work correctly as you see. On my ROCK3A, almost similar SoC I get all sorts of strange crashes/hangs in that situation.

 

So use MaskROM mode to wipe SPI-flash or write a correct U-Boot version to it; see https://docs.radxa.com/en/rock3/rock3c/low-level-dev/3c-maskrom?host_os=Linux_MacOS

 

Other option maybe is to boot with an image that has vendor kernel (I use 6.1.115 on my ROCK3A with legacy U-Boot) so then the board can be operated via serial console and from there write the SPI-flash with dd or flashcp (see /dev/mtd*).

Edited Tuesday at 09:32 AM by eselarm

[socrates018]

Thanks for replying, I hadn't noticed the android thing, I have two sd cards one with the radxa android 14 and the other with the debian bullseye from radxa. I didn't mess with the SPI flash because both work correctly, does android flash the spi when booting, I don't understand how it works with the default debian but not here?  I will try to maskrom mode and update. Btw here is the whole boot sequence in case it helps (I tried an older armbian build here but still the same). 

serial_log.txt