Cubietruck - Cubieboard 3 does not boot from SD-card - Buster 21.02.3 / 21.02.01

[AlbertB]

Hi,

I am having a hard time getting Armbian to boot on my Cubietruck. I have recorded some serial output but it does not show anything helpfull (at least for me). It just stopps at "Starting kernel". Verbosity is set to 7.

Serial output 21.02.3
https://pastebin.com/DMWRzTgn

Serial output 21.02.1
https://pastebin.com/a9Hasywc

I tried the same SD-card and power supply with Arch for ARM. Arch boots fine.

Serial output Arch Linux:
https://pastebin.com/bMPf3gfx

What further options do I have to debug this? As I am not really familiar with Arch I'd rather run a Debian / Ubuntu based OS.

 

Best regards,
Albert

[AlbertB]

I tried to get more log output by changing armbianEnv.txt. Set verbosity to 8 and used extraargs for kernel loglevel. It now looks like this:

verbosity=8
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun7i-a20
rootdev=UUID=dedfc644-5a63-4c33-a195-c8484ef0efd5
rootfstype=ext4
extraargs=loglevel=8

But serial output still isn't very verbose:

https://pastebin.com/bFreCMcJ

 

Isn't /boot/armbianEnv.txt the right place to do this?

[AlbertB]

I tried the recovery method described here: https://docs.armbian.com/User-Guide_Recovery/#u-boot-shell-access but I got an error on the first ext4load command.

 

=> setenv bootargs init=/bin/bash root=/dev/mmcblk0p1 rootwait console=ttyS0,115200
=> ext4load mmc 0 0x49000000 /boot/dtb/${fdtfile}
** File not found /boot/dtb/sun7i-a20-cubietruck.dtb **

 

What does this mean? I am a bit lost on u-boot console. After some google searches and try and error I think I found a command to list the SD card file system. Apparently the file is there.

 

=> ext2ls mmc 0 /boot/dtbs
<DIR>      36864 .
<DIR>       4096 ..
           89523 am335x-baltos-ir5221.dtb
<...>
           40859 sun7i-a20-bananapro.dtb
           43895 sun7i-a20-cubietruck.dtb
           42618 sun7i-a20-itead-ibox.dtb
           26469 sun8i-a23-polaroid-mid2809pxe04.dtb
           32156 sun8i-a33-ga10h-v1.1.dtb
<...>

 

Then I noticed a small difference. ext4load was /boot/dtb/${ftdfile} but the path on ext2ls was /boot/dtbs. So I changed that and it went a bit further but in the end it still stops at starting kernel...

 

=> setenv bootargs init=/bin/bash root=/dev/mmcblk0p1 rootwait console=ttyS0,11520
print bootargs
bootargs=init=/bin/bash root=/dev/mmcblk0p1 rootwait console=ttyS0,11520
=> ext4load mmc 0 0x49000000 /boot/dtbs/${fdtfile}
43895 bytes read in 7376 ms (4.9 KiB/s)
=> ext4load mmc 0 0x46000000 /boot/zImage
7406192 bytes read in 532 ms (13.3 MiB/s)
=> env set fdt_high ffffffff
=> bootz 0x46000000 - 0x49000000
## Flattened Device Tree blob at 49000000
   Booting using the fdt blob at 0x49000000
   Using Device Tree in place at 49000000, end 4900db76

Starting kernel ...