Got Rock 5, preparing for install and feedback

SCerovec · 04-03-2023, 01:42 PM

Got a 16GB RAM Rock 5.

I want to express my gratitude for all the work put forth to prepare the images and maintain the downloads for the numerous boards and options.

Looking forward for feedback as i delve into the process of trying to make it my daily driver.

Stay tuned...

sndwvs · 04-07-2023, 11:53 AM

have you tried images?
on the Radxa website they wrote about the correct work.

SCerovec · 04-07-2023, 01:05 PM

Hello there

Yes, In fact I downloaded the XFCE4 image and flashed it to a freshly bought SD card and - nothing

As i went about reading all i could get/find/figure out - I found out the following:

1. I lack proper tools to check/test/grade my USB Type C chargers if fit or not for the task (waiting for an upgraded tester now)
2. All my chargers / power supplies are questionable (returned one to the store, bought another, waiting for a third one in transit...)
3. Same goes for my cables (well i sorted that one partway out, but Type C data cables are picky, iffy and expensive)

(ง`_´)ง

Code:

 # $_

Luckily my CLI-fu serves me still well and i was able to test run all three boot-loaders at RADXA's, then i found out:

4. My (t)rusty serial converters are just that ((t)rusty) - obsolete - i can't go by in 2023 with CP2101 any more - out with the old, in with the new - i ordered some CH340 hopefully soon to come...

As it turned out the 1500000 (carefully when counting those zeros!) bps the Rock 5 uses is just out of reach of the CP2101 that tops out at 912600 bps

some non typical tips that might apply to other Slackers:
a. if the serial port isn't auto detected - check if you rebooted since you upgraded the kernel (don't ask, okay?)
b. file:~/.minirc.rock5

Code:

pu port             /dev/ttyUSB0
pu baudrate         1500000
pu bits             8
pu parity           N
pu stopbits         1
pu rtscts           No

call it with:

Code:

minicom rock5

c. file: ~/.bashrc

Code:

[snip] <--- don't copy and paste this snip-mark, i have much more unrelated stuff there as so might You !!
alias minicom='minicom -w -t xterm -l -R UTF-8'
[snip]

TL;DR:
i'm gearing up ...

sndwvs · 04-07-2023, 01:31 PM

I use

Code:

sudo screen /dev/ttyUSB0 1500000,cs

I don't have rock 5, but everything works fine on orange pi 5

SCerovec · 04-07-2023, 01:51 PM

Quote:

Originally Posted by sndwvs

I use

Code:

sudo screen /dev/ttyUSB0 1500000,cs

I don't have rock 5, but everything works fine on orange pi 5

screen is good too and i believe there is an option for it to enable 256 colors if the terminal supports that too?

sndwvs · 04-07-2023, 02:38 PM

I just use tmux inside or set

Code:

export TERM=screen-256color

variable inside too.

SCerovec · 04-08-2023, 08:22 AM

further investigation was conducted:

file: ~/.local/bin/bauds.sh

Code:

#!/bin/sh

#
# https://superuser.com/questions/488449/is-there-any-way-to-check-which-baud-rates-are-supported-on-a-serial-device
#

mapfile -t devs < <(
    /bin/ls -l /sys/class/tty |
        sed -ne '
            /\/virtual\//d;
            s@^.* \(tty[^ ]\+\) -> .*@\1@p
        '
)
ans=yes hfile=/usr/include/asm-generic/termbits.h
mapfile -t bauds < <(
    sed -nr 's/^#define\s+B([0-9]{2,})\s+.*/\1/p' <$hfile
)
for tty in ${devs[@]};do
    echo "[ $tty ]"
    column < <(
        for rate in ${bauds[@]};do
            stty -F /dev/$tty $rate &>/dev/null
            printf '%8d %-3s\n' $rate ${ans[$?]:-no}
        done
    )
done

i find this script quite useful for this endeavor as it clearly lists the supported baud rates per present serial port/line loud and clear

my earlier recorder serial console command:

Code:

$ screen -T screen-256color /dev/ttyUSB0 115200,-crtscts

(found it in a file: ttyUSB.sh:

Code:

screen -T screen-256color /dev/ttyUSB0 115200,-crtscts

)
my current outputs with PL2101 converter attached (this machine has native serial port):

Code:

[ ttyS0 ]
      50 yes	     150 yes	    1200 yes	    9600 yes	  115200 yes	  576000 no 	 1500000 no 	 3500000 no 
      75 yes	     200 yes	    1800 yes	   19200 yes	  230400 no 	  921600 no 	 2000000 no 	 4000000 no 
     110 yes	     300 yes	    2400 yes	   38400 yes	  460800 no 	 1000000 no 	 2500000 no 
     134 yes	     600 yes	    4800 yes	   57600 yes	  500000 no 	 1152000 no 	 3000000 no 
[ ttyS1 ]
      50 no 	     150 no 	    1200 no 	    9600 no 	  115200 no 	  576000 no 	 1500000 no 	 3500000 no 
      75 no 	     200 no 	    1800 no 	   19200 no 	  230400 no 	  921600 no 	 2000000 no 	 4000000 no 
     110 no 	     300 no 	    2400 no 	   38400 no 	  460800 no 	 1000000 no 	 2500000 no 
     134 no 	     600 no 	    4800 no 	   57600 no 	  500000 no 	 1152000 no 	 3000000 no 
[ ttyS2 ]
      50 no 	     150 no 	    1200 no 	    9600 no 	  115200 no 	  576000 no 	 1500000 no 	 3500000 no 
      75 no 	     200 no 	    1800 no 	   19200 no 	  230400 no 	  921600 no 	 2000000 no 	 4000000 no 
     110 no 	     300 no 	    2400 no 	   38400 no 	  460800 no 	 1000000 no 	 2500000 no 
     134 no 	     600 no 	    4800 no 	   57600 no 	  500000 no 	 1152000 no 	 3000000 no 
[ ttyS3 ]
      50 no 	     150 no 	    1200 no 	    9600 no 	  115200 no 	  576000 no 	 1500000 no 	 3500000 no 
      75 no 	     200 no 	    1800 no 	   19200 no 	  230400 no 	  921600 no 	 2000000 no 	 4000000 no 
     110 no 	     300 no 	    2400 no 	   38400 no 	  460800 no 	 1000000 no 	 2500000 no 
     134 no 	     600 no 	    4800 no 	   57600 no 	  500000 no 	 1152000 no 	 3000000 no 
[ ttyUSB0 ]
      50 no 	     150 no 	    1200 yes	    9600 yes	  115200 yes	  576000 yes	 1500000 no 	 3500000 no 
      75 no 	     200 no 	    1800 yes	   19200 yes	  230400 yes	  921600 yes	 2000000 no 	 4000000 no 
     110 no 	     300 yes	    2400 yes	   38400 yes	  460800 yes	 1000000 yes	 2500000 no 
     134 no 	     600 yes	    4800 yes	   57600 yes	  500000 yes	 1152000 no 	 3000000 no

stay tuned...

SCerovec · 04-08-2023, 08:28 AM

FWIW it can be worse:

Code:

$ bauds.sh 
[ ttyS0 ]
      50 no 	     300 no 	    9600 no 	  460800 no 	 1500000 no 
      75 no 	     600 no 	   19200 no 	  500000 no 	 2000000 no 
     110 no 	    1200 no 	   38400 no 	  576000 no 	 2500000 no 
     134 no 	    1800 no 	   57600 no 	  921600 no 	 3000000 no 
     150 no 	    2400 no 	  115200 no 	 1000000 no 	 3500000 no 
     200 no 	    4800 no 	  230400 no 	 1152000 no 	 4000000 no 
[ ttyS1 ]
      50 no 	     300 no 	    9600 no 	  460800 no 	 1500000 no 
      75 no 	     600 no 	   19200 no 	  500000 no 	 2000000 no 
     110 no 	    1200 no 	   38400 no 	  576000 no 	 2500000 no 
     134 no 	    1800 no 	   57600 no 	  921600 no 	 3000000 no 
     150 no 	    2400 no 	  115200 no 	 1000000 no 	 3500000 no 
     200 no 	    4800 no 	  230400 no 	 1152000 no 	 4000000 no 
[ ttyS2 ]
      50 no 	     300 no 	    9600 no 	  460800 no 	 1500000 no 
      75 no 	     600 no 	   19200 no 	  500000 no 	 2000000 no 
     110 no 	    1200 no 	   38400 no 	  576000 no 	 2500000 no 
     134 no 	    1800 no 	   57600 no 	  921600 no 	 3000000 no 
     150 no 	    2400 no 	  115200 no 	 1000000 no 	 3500000 no 
     200 no 	    4800 no 	  230400 no 	 1152000 no 	 4000000 no 
[ ttyS3 ]
      50 no 	     300 no 	    9600 no 	  460800 no 	 1500000 no 
      75 no 	     600 no 	   19200 no 	  500000 no 	 2000000 no 
     110 no 	    1200 no 	   38400 no 	  576000 no 	 2500000 no 
     134 no 	    1800 no 	   57600 no 	  921600 no 	 3000000 no 
     150 no 	    2400 no 	  115200 no 	 1000000 no 	 3500000 no 
     200 no 	    4800 no 	  230400 no 	 1152000 no 	 4000000 no

on my other machine

investigating options in the time before the CH340 reaches me right now...

SCerovec · 04-08-2023, 09:28 AM

Who could've guessed that i have a better serial converter just lying around?

Code:

[snip]
[ ttyUSB0 ]
      50 yes	     300 yes	    9600 yes	  460800 yes	 1500000 yes
      75 yes	     600 yes	   19200 yes	  500000 yes	 2000000 yes
     110 yes	    1200 yes	   38400 yes	  576000 yes	 2500000 yes
     134 yes	    1800 yes	   57600 yes	  921600 yes	 3000000 yes
     150 yes	    2400 yes	  115200 yes	 1000000 yes	 3500000 no 
     200 yes	    4800 yes	  230400 yes	 1152000 yes	 4000000 n0

dmesg:

Code:

 ftdi_sio 2-1.6:1.0: FTDI USB Serial Device converter detected
 usb 2-1.6: Detected FT232RL
 usb 2-1.6: FTDI USB Serial Device converter now attached to ttyUSB0

Guru meditation:

Code:

DDR Version V1.08 20220617
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=16 Size=4096MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=16 Size=4096MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=16 Size=4096MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=16 Size=4096MB
Manufacturer ID:0xff 
CH0 RX Vref:26.7%, TX Vref:22.8%,22.8%
CH1 RX Vref:30.7%, TX Vref:21.8%,21.8%
CH2 RX Vref:27.7%, TX Vref:23.8%,22.8%
CH3 RX Vref:26.7%, TX Vref:22.8%,22.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-g3caf61a44c2-220414 #stephen (Sep 29 2022 - 18:14:19)
Trying to boot from MMC2
spl: partition error
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(806278dba1...) + OK
## Checking uboot 0x00200000 ... sha256(1b840c0f8f...) + OK
## Checking fdt 0x00309838 ... sha256(d32827d3ac...) + OK
## Checking atf-2 0x000f0000 ... sha256(c00c7fd75b...) + OK
## Checking atf-3 0xff100000 ... sha256(71c3a5841b...) + OK
## Checking atf-4 0xff001000 ... sha256(2301cf73be...) + OK
Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)
Total: 663.297 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-405-gb52c2eadd:derrick.huang
NOTICE:  BL31: Built : 11:23:47, Aug 15 2022
INFO:    spec: 0x1
INFO:    ext 32k is not valid
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    system boots from cpu-hwid-0
INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO:    BL31: Initialising Exception Handling Framework
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

It seems there is something off?

SCerovec · 04-08-2023, 09:35 AM

when i boot w/o the SD card inserted:

Code:

DDR Version V1.08 20220617
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=16 Size=4096MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=16 Size=4096MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=16 Size=4096MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=16 Size=4096MB
Manufacturer ID:0xff 
CH0 RX Vref:26.7%, TX Vref:22.8%,22.8%
CH1 RX Vref:30.7%, TX Vref:21.8%,21.8%
CH2 RX Vref:27.7%, TX Vref:23.8%,22.8%
CH3 RX Vref:26.7%, TX Vref:22.8%,22.8%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-g3caf61a44c2-220414 #stephen (Sep 29 2022 - 18:14:19)
Trying to boot from MMC2
MMC: no card present
mmc_init: -123, time 0
spl: mmc init failed with error: -123
Trying to boot from MMC1
Card did not respond to voltage select!
mmc_init: -95, time 14
spl: mmc init failed with error: -95
Trying to boot from MTD2
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(806278dba1...) + OK
## Checking uboot 0x00200000 ... sha256(6a08776395...) + OK
## Checking fdt 0x0030a010 ... sha256(d32827d3ac...) + OK
## Checking atf-2 0x000f0000 ... sha256(c00c7fd75b...) + OK
## Checking atf-3 0xff100000 ... sha256(71c3a5841b...) + OK
## Checking atf-4 0xff001000 ... sha256(2301cf73be...) + OK
Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)
Total: 498.796 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-405-gb52c2eadd:derrick.huang
NOTICE:  BL31: Built : 11:23:47, Aug 15 2022
INFO:    spec: 0x1
INFO:    ext 32k is not valid
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    system boots from cpu-hwid-0
INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO:    BL31: Initialising Exception Handling Framework
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-g3caf61a44c2-220414 #stephen (Sep 29 2022 - 18:14:19 +0800)

Model: Radxa ROCK 5B
PreSerial: 2, raw, 0xfeb50000
DRAM:  15.7 GiB
Sysmem: init
Relocation Offset: edb6d000
Relocation fdt: eb9f9cd8 - eb9fecc8
CR: M/C/I
Using default environment

SF: Detected sfc_nor with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Bootdev(atags): mtd 2
PartType: EFI
DM: v2
No misc partition
boot mode: None
FIT: No boot partition
No resource partition
No resource partition
No resource partition
Failed to load DTB, ret=-19
No find valid DTB, ret=-22
Failed to get kernel dtb, ret=-22
Model: Radxa ROCK 5B
CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)
  b0pll 24000 KHz
  b1pll 24000 KHz
  lpll 24000 KHz
  v0pll 24000 KHz
  aupll 24000 KHz
  cpll 1500000 KHz
  gpll 1188000 KHz
  npll 24000 KHz
  ppll 1100000 KHz
  aclk_center_root 702000 KHz
  pclk_center_root 100000 KHz
  hclk_center_root 396000 KHz
  aclk_center_low_root 500000 KHz
  aclk_top_root 750000 KHz
  pclk_top_root 100000 KHz
  aclk_low_top_root 396000 KHz
No misc partition
Net:   No ethernet found.
Hit key to stop autoboot('CTRL+C'):  0
PCIe-0 Link Fail

Device 0: unknown device
no mmc device at slot 1
no mmc device at slot 0

Device 2: Vendor: 0x2207 Rev: V1.00 Prod: sfc_nor
            Type: Hard Disk
            Capacity: 16.0 MB = 0.0 GB (32768 x 512)
... is now current device
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **

Device 1:
Device 0: unknown device
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No working controllers found
failed to find reset-gpios property
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-rockchip
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
starting USB...
No working controllers found
failed to find reset-gpios property
No ethernet found.
Could not get mtd 0
## Booting FIT Image FIT: No boot partition
FIT: No fit blob
FIT: No FIT image
Unknown command 'bootrkp' - try 'help'
=>

It seems as if the uboot on the SD card is missng or something?

sndwvs · 04-08-2023, 09:53 AM

it feels like it's loading from spi.
here is the testing

SCerovec · 04-09-2023, 05:13 AM

Quote:

Originally Posted by sndwvs

have you tried images?
on the Radxa website they wrote about the correct work.

Been there,

What is this and why there is no mention of what to do with the kernel packages there or the image(s) i pointed at?

Also, who is mara?

Right now i'm considering to organize a build host and try tackle the building of an working procedure as this one clearly fails for an unknown to me reason.

sndwvs · 04-09-2023, 05:44 AM

Quote:

Originally Posted by SCerovec

Been there,

What is this and why there is no mention of what to do with the kernel packages there or the image(s) i pointed at?

README.TXT describes writing to the sdcard. Packages with the kernel are already installed, but they can be updated using standard tools in an already configured environment.

Quote:

Originally Posted by SCerovec

Also, who is mara?

this is my theme.

SCerovec · 04-09-2023, 12:10 PM

News Flash:
Got the Debian image working, now back to make Slackware work too.

That was with the SPI zeroed (i'll keep it zeroed for the while)

Did it with Etcher the Radxa website proposes for the tool...

Stay tuned...

SCerovec · 04-09-2023, 05:34 PM

i'be bitten the bullet and booted the orange pi 5 core image on my raxda rock 5:

Code:

[snip] 
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-rk3588s (Feb 25 2023 - 00:05:39 +0200)

Model: Orange Pi 5
PreSerial: 2, raw, 0xfeb50000
DRAM:  15.7 GiB
Sysmem: init
Relocation Offset: eda2e000
Relocation fdt: eb9f8ba8 - eb9fecb8
CR: M/C/I
Using default environment

no mmc device at slot 1
mmc@fe2c0000: 1 (SD), mmc@fe2e0000: 0
Bootdev(atags): mmc 1
MMC1: Legacy, 52Mhz
PartType: EFI
DM: v2
boot mode: None
Model: Orange Pi 5
CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)
  b0pll 24000 KHz
  b1pll 24000 KHz
  lpll 24000 KHz
  v0pll 24000 KHz
  aupll 24000 KHz
  cpll 1500000 KHz
  gpll 1188000 KHz
  npll 24000 KHz
  ppll 1100000 KHz
  aclk_center_root 702000 KHz
  pclk_center_root 100000 KHz
  hclk_center_root 396000 KHz
  aclk_center_low_root 500000 KHz
  aclk_top_root 750000 KHz
  pclk_top_root 100000 KHz
  aclk_low_top_root 396000 KHz
Net:   No ethernet found.
Hit key to stop autoboot('CTRL+C'):  0 
switch to partitions #0, OK
mmc1 is current device
mmc@fe2c0000: 1 (SD)
mmc@fe2e0000: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
2602 bytes read in 6 ms (422.9 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
139 bytes read in 7 ms (18.6 KiB/s)
53837 bytes read in 37 ms (1.4 MiB/s)
31781376 bytes read in 9554 ms (3.2 MiB/s)
libfdt fdt_getprop(): FDT_ERR_NOTFOUND
** File not found /dtb/rockchip/overlay/rockchip-fixup.scr **
6476262 bytes read in 532 ms (11.6 MiB/s)
Fdt Ramdisk skip relocation
## Loading init Ramdisk from Legacy Image at 0a200000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    6476198 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 0x0a100000
   Booting using the fdt blob at 0x0a100000
   reserving fdt memory region: addr=a100000 size=73000
   Using Device Tree in place at 000000000a100000, end 000000000a175fff
can't found rockchip,drm-logo, use rockchip,fb-logo
WARNING: could not set reg FDT_ERR_BADOFFSET.
failed to reserve fb-loader-logo memory
Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000)
Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000)
Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000)
Total: 10736.24 ms

Starting kernel ...

[    0.731143] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.
[    0.935938] mmc2: tuning execution failed: -5
[    0.936326] mmc2: error -5 whilst initialising SD card
[    1.007979] mmc2: tuning execution failed: -5
[    1.060746] mmc2: error -84 whilst initialising SD card
[    1.136903] mmc2: tuning execution failed: -5
[    1.200726] mmc2: error -84 whilst initialising SD card

Got quite past where i was stuck:

Apparently the u-boot image is at fault?

What gives?