RPI-4B aarch64 does not boot

This forum is for topics dealing with problems with software specifically in the AArch64 repo.

RPI-4B aarch64 does not boot

Postby dk23 » Sat Jan 07, 2023 9:35 pm

RPi-4B 4GB 2018 New install with Aug 2022 aarch64 image will not boot. However, new installs with PIOS 32 or 64, and Arch 32 will. Looks like a SD card problem. Used same card for other tests and tried a new card for last mainline aarch64 test with same result. Interestingly the SD card boots ok on a different RPi-4. Must be a hardware issue with the RPi. serial console (output repeats the block until power off. )

$this->bbcode_second_pass_code('', '
[ 3.471072] raspberrypi-firmware soc:firmware: Attached to firmware from 2022-07-25T15:10:17
[ 3.659865] dwc2 fe980000.usb: supply vusb_d not found, using dummy regulator
[ 3.667252] dwc2 fe980000.usb: supply vusb_a not found, using dummy regulator
[ 3.775074] dwc2 fe980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM
[ 3.828110] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 3.833523] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[ 3.841296] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000040000000890
[ 3.851168] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.18
[ 3.859564] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.866895] usb usb1: Product: xHCI Host Controller
[ 3.871843] usb usb1: Manufacturer: Linux 5.18.1-1-aarch64-ARCH xhci-hcd
[ 3.878645] usb usb1: SerialNumber: 0000:01:00.0
[ 3.883627] hub 1-0:1.0: USB hub found
[ 3.887482] hub 1-0:1.0: 1 port detected
[ 3.891759] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 3.897150] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[ 3.904665] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[ 3.911171] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.18
[ 3.919665] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.926996] usb usb2: Product: xHCI Host Controller
[ 3.931944] usb usb2: Manufacturer: Linux 5.18.1-1-aarch64-ARCH xhci-hcd
[ 3.938743] usb usb2: SerialNumber: 0000:01:00.0
[ 3.943675] hub 2-0:1.0: USB hub found
[ 3.947530] hub 2-0:1.0: 4 ports detected
[ 3.965682] sdhci-iproc fe300000.mmc: allocated mmc-pwrseq
[ 4.020599] mmc0: SDHCI controller on fe300000.mmc [fe300000.mmc] using PIO
[ 4.067962] ALSA device list:
[ 4.070997] No soundcards found.
[ 4.108699] mmc1: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA
[ 4.117083] mmc0: new high speed SDIO card at address 0001
[ 4.120622] Freeing unused kernel memory: 6464K
[ 4.127338] Run /init as init process
[ 4.139882] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 4.164843] mmc1: ADMA error: 0x02000000
[ 4.168843] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 4.175383] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00001002
[ 4.175387] mmc1: sdhci: Blk size: 0x00007008 | Blk cnt: 0x00000001
[ 4.175391] mmc1: sdhci: Argument: 0x00000000 | Trn mode: 0x00000013
[ 4.175394] mmc1: sdhci: Present: 0x1fff0206 | Host ctl: 0x00000011
[ 4.175397] mmc1: sdhci: Power: 0x0000000f | Blk gap: 0x00000080
[ 4.175400] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x00007d07
[ 4.175403] mmc1: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
[ 4.221091] mmc1: sdhci: Int enab: 0x03ff100b | Sig enab: 0x03ff100b
[ 4.221095] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[ 4.221098] mmc1: sdhci: Caps: 0x45ee6432 | Caps_1: 0x0000a525
[ 4.240679] mmc1: sdhci: Cmd: 0x0000333a | Max curr: 0x00080008
[ 4.240682] mmc1: sdhci: Resp[0]: 0x00000920 | Resp[1]: 0x0076b27f
[ 4.240685] mmc1: sdhci: Resp[2]: 0x325b5900 | Resp[3]: 0x00400e00
[ 4.240688] mmc1: sdhci: Host ctl2: 0x00000008
[ 4.264765] mmc1: sdhci: ADMA Err: 0x00000001 | ADMA Ptr: 0xc3000200
[ 4.264767] mmc1: sdhci: ============================================
[ 4.264770] mmc1: sdhci: c3000200: DMA 0xf3400000, LEN 0x0008, Attr=0x21
[ 4.284613] mmc1: sdhci: c3000208: DMA 0x00000000, LEN 0x0000, Attr=0x03
[ 4.284786] mmc1: error -5 whilst initialising SD card
[ 4.306490] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[ 4.314900] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 4.322155] usb 1-1: Product: USB2.0 Hub
[ 4.329050] hub 1-1:1.0: USB hub found
[ 4.333121] hub 1-1:1.0: 4 ports detected
[ 4.591100] mmc1: ADMA error: 0x02000000
[ 4.595098] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[ 4.601629] mmc1: sdhci: Sys addr: 0x00000000 | Version: 0x00001002
[ 4.608160] mmc1: sdhci: Blk size: 0x00007008 | Blk cnt: 0x00000001
[ 4.614690] mmc1: sdhci: Argument: 0x00000000 | Trn mode: 0x00000013
[ 4.618887] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd
[ 4.621219] mmc1: sdhci: Present: 0x1fff0206 | Host ctl: 0x00000011
[ 4.621223] mmc1: sdhci: Power: 0x0000000f | Blk gap: 0x00000080
[ 4.621226] mmc1: sdhci: Wake-up: 0x00000000 | Clock: 0x0000a707
[ 4.621229] mmc1: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000
[ 4.621231] mmc1: sdhci: Int enab: 0x03ff100b | Sig enab: 0x03ff100b
[ 4.621234] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[ 4.621237] mmc1: sdhci: Caps: 0x45ee6432 | Caps_1: 0x0000a525
[ 4.673715] mmc1: sdhci: Cmd: 0x0000333a | Max curr: 0x00080008
[ 4.680243] mmc1: sdhci: Resp[0]: 0x00000920 | Resp[1]: 0x0076b27f
[ 4.686772] mmc1: sdhci: Resp[2]: 0x325b5900 | Resp[3]: 0x00400e00
[ 4.693301] mmc1: sdhci: Host ctl2: 0x00000008
[ 4.697801] mmc1: sdhci: ADMA Err: 0x00000001 | ADMA Ptr: 0xc3000200
[ 4.704328] mmc1: sdhci: ============================================
')
dk23
 
Posts: 25
Joined: Wed Feb 04, 2015 4:18 pm

Re: RPI-4B aarch64 does not boot

Postby solskogen » Sat Jan 07, 2023 10:29 pm

If it boots of another Pi. Could you try updating it and perhaps use the linux-rpi kernel instead?
solskogen
 
Posts: 161
Joined: Mon Nov 18, 2013 10:41 am

Re: RPI-4B aarch64 does not boot

Postby lategoodbye » Sun Jan 08, 2023 11:30 am

This is neither a SD card nor a kernel issue. It's cause by the bootloader like U-Boot which providing the wrong DT data.

Here is the related U-Boot patch:
https://lists.denx.de/pipermail/u-boot/ ... 91456.html
lategoodbye
 
Posts: 116
Joined: Sat Dec 29, 2018 1:24 am

Re: RPI-4B aarch64 does not boot

Postby Nickolay » Tue Jan 10, 2023 11:53 am

It's known issue for Pi 4 new revision.
Workaround:
1. How to fix (has some inaccuracies)
viewtopic.php?f=67&t=15422&start=10#p67207
2. A fix for the fix in message above
viewtopic.php?f=67&t=15422&start=10#p67236
Nickolay
 
Posts: 2
Joined: Tue Jan 10, 2023 11:41 am

Re: RPI-4B aarch64 does not boot

Postby graysky » Tue Jan 10, 2023 12:40 pm

$this->bbcode_second_pass_quote('Nickolay', 'I')t's known issue for Pi 4 new revision.


To be clear, what is the revision affected? If you or anyone has an affected board, once you get it booted, please post the output of:
$this->bbcode_second_pass_code('', '
grep Model /proc/cpuinfo
Model : Raspberry Pi 4 Model B Rev 1.4
')
graysky
Developer
 
Posts: 1728
Joined: Sun Jun 26, 2011 6:56 am
Location: /run/user/1000

Re: RPI-4B aarch64 does not boot

Postby dk23 » Tue Jan 10, 2023 9:11 pm

The solution that I used was to boot on a different RPi and change to linux-rpi kernel

$this->bbcode_second_pass_code('', '
$ grep Model /proc/cpuinfo
Model : Raspberry Pi 4 Model B Rev 1.1
')
dk23
 
Posts: 25
Joined: Wed Feb 04, 2015 4:18 pm

Re: RPI-4B aarch64 does not boot

Postby lategoodbye » Wed Jan 11, 2023 5:22 pm

$this->bbcode_second_pass_quote('graysky', '')$this->bbcode_second_pass_quote('Nickolay', 'I')t's known issue for Pi 4 new revision.


To be clear, what is the revision affected? If you or anyone has an affected board, once you get it booted, please post the output of:
$this->bbcode_second_pass_code('', '
grep Model /proc/cpuinfo
Model : Raspberry Pi 4 Model B Rev 1.4
')


AFAIK there is no reliable mapping between the board revision from /proc/cpuinfo (which is btw only available for linux-rpi and not in mainline) and the SoC stepping. So we need to rely on the DT passed by the firmware. That's the reason why Nickolay suggested "hack" works.

Nevertheless i raised this topic on u-boot mailing list:
https://lore.kernel.org/u-boot/DFAFD637 ... s.net/T/#t
lategoodbye
 
Posts: 116
Joined: Sat Dec 29, 2018 1:24 am
Top

Re: RPI-4B aarch64 does not boot

Postby h4o » Wed Jan 11, 2023 8:35 pm

I had a similar issue and couldn't quite figure out why I wasn't able to boot the aarch64 kernel on the RPi4B and came across the following: viewtopic.php?f=67&t=15422&start=10

It basically requires you to do the following if you created the sdcard as the instructions told you to:
Before unmounting the sdcard open the boot.txt on the boot partition, replace the last two occurences of ${fdt_addr_r} with ${fdt_addr} in boot.txt (see code block below) and execute mkscr afterwards. For mkscr you need uboot-tools on the system you are preparing the sdcard on.

$this->bbcode_second_pass_code('', '# Set root partition to the second partition of boot device
part uuid ${devtype} ${devnum}:2 uuid

setenv bootargs console=ttyS1,115200 console=tty0 root=PARTUUID=${uuid} rw rootwait smsc95xx.macaddr="${usbethaddr}"

if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /Image; then
if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /dtbs/${fdtfile}; then
if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /initramfs-linux.img; then
booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr};
else
booti ${kernel_addr_r} - ${fdt_addr};
fi;
fi;
fi')
h4o
 
Posts: 4
Joined: Wed Jan 11, 2023 8:25 pm

Re: RPI-4B aarch64 does not boot

Postby Nickolay » Wed Jan 11, 2023 11:11 pm

I agree with lategoodbye, it is U-boot issues related to an incorrect processing of the DT for SoC rev. C0

My Pi 4 is based on SoC rev. C0

$this->bbcode_second_pass_code('', '# cat /sys/firmware/devicetree/base/model
Raspberry Pi 4 Model B Rev 1.5')

P.S. There are bug reports for the same issue from Raspberry Pi 4 Model B Rev 1.4 owners
Nickolay
 
Posts: 2
Joined: Tue Jan 10, 2023 11:41 am

Re: RPI-4B aarch64 does not boot

Postby uhhyeahbret » Sun Jan 29, 2023 12:57 am

I installed uboot-tools, but don't see a mkscr command anywhere. Any other ideas where to find that?

EDIT: nm, viewtopic.php?f=67&t=15422&start=10#p67207 has a good description of how to run it.
uhhyeahbret
 
Posts: 12
Joined: Thu Sep 03, 2015 11:10 am

Next

Return to ARMv8

Who is online

Users browsing this forum: No registered users and 13 guests