Good that you share the bootloader log from the serial cable. I see it stall already pretty early. I would check things with respect to:
DDR Version 1.30 20230417
I don’t have this SBC myself, but it seems OK version. I have noticed problems with other versions, but forgot the details.
So if RAM seems OK, it could be a power or something related to SD-card. That is something you need to figure out yourself. Related to SD-card can also an USB SD-card adapter that is the cause of the problem.
Hi radrocks, many thanks for the answer. So, this board is new, never used. I know this doesnt mean 100% ok, but one expects it.
So if I understand correctly I can connect the USB card reader/writer to one of the USB ports and see if it boots from the reader instead from the onboard microsd reader ?
Do I need to do any kind of setting set up before ?
How the exact boot process for ROCK Pi works ? I mean, does the SOC looks for a specific partition at startup ? I know some SoC boards must have a FAT partition on a SD card to readt initial stuff from there. Is there some documentation on the radxa wiki ?
You can write the U-Boot binary to and empty SD-card at sector 64. So just blind/fixed location. The SoC reads that and that U-Boot contains code to read from USB stick. But that U-Boot already hangs in your case. That is rare, so only options I know of is that the contents on the SD-card are not the same as in the image. Is rare, but I have seen it on Armbian forum. The person who got that issue did binary compare image and the SD-card contents (before boot) and did not match. Was a problem with USB and/or card writer.
Other is PSU. Might dip below 5V too much, then SBC hangs. As I mentioned, you need to check yourself. I have had some strange issues with with my ROCK3A because I fed it with 5V (RPI5 27W PSU, but looking in detail, the ROCK3a should be fed with higher voltage. I do that now, and all strange issues gone.
Or your board is just broken. Then send it back and ask money back.
I see from Radxa ROCK 4B that it has SPI-flash, so there could be a corrupt variant of U-Boot in there, but unlikely as it is new board you say end then it should be empty. But maybe wipe it in maskROM mode.
Dear radrocks, many thanks for this tips. I will be playing a bit with the other OS´s and see if this makes a change. Will also make sure I get a good power for it, altough I bought a package with cable and power adapter which came from Radxa, so I suppose they know what they ship.
Ok, that should not be my case as my board is v1.3 and one of things I read is that it does NOT have the SPI chip on it, if I understood it correctly. There is a pplace for it, but you have to solder it by yourself.
You could also try to use an external (Armbian) image with very latest U-Boot and kernel. And use their Imager, it does auto verify, so bit easier I would say. But the Radxa build show work.
But if real HW problem, it won’t make a difference I would say, you might see slightly different serial log then, maybe that gives a hint.
Great, ok. Will try to play a bit with it in the next days and see what I can get. BTW, can I only put the uboot on the sdcard to see if it works ? Where can I find the correct uboot ?
Hi, from this page here Partitions - Rockchip Wiki i see the location start and end address is there some specific type of partition that is needed ? I mean in gfdisk you can set up the exact type of partition. Should it be which one Linux EF00 or 8300 or which type ?
As for the u-boot you mention to look for look for linux-u-boot-rockpi-4bplus-edge