On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote:
> rpi_4
> rpi_4_32b

I dug up my old dusty rpi4 which I probably haven't touched
since last time we spoke about u-boot on it.


I've tested only the 64bit (arm64) version so far.

The version that was on the sd-card since last time:
U-Boot> ver
U-Boot 2020.07+dfsg-1 (Jul 08 2020 - 23:29:02 +0000)

gcc (Debian 9.3.0-14) 9.3.0
GNU ld (GNU Binutils for Debian) 2.34.90.20200706
U-Boot> 


I upgraded only u-boot.bin from bookworm/sid/experimental
on the firmware partition (nothing else touched, and I'm not
really sure what state it was in since last time but probably
a bootable system atleast).

Testing/bookworm u-boot.bin seems to boot fine (although
serial console became garbage after Linux started, but
it seemed to run but I didn't investigate much).

The unstable and experimental versions both caused a reset
after run bootcmd and before "Starting Linux...".
U-Boot itself seemed to run fine though, it was running bootcmd
that caused the reset. Maybe I need to upgrade the rpi firmware,
or maybe it's related to what else is on the old sd-card that
was in the box.


# testing u-boot

U-Boot> ver
U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 19:14:13 +0000)

gcc (Debian 11.3.0-1) 11.3.0
GNU ld (GNU Binutils for Debian) 2.38
U-Boot> 

# unstable u-boot

U-Boot> ver
U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +0000)

gcc (Debian 12.2.0-10) 12.2.0
GNU ld (GNU Binutils for Debian) 2.39.50.20221208
U-Boot> 




U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +0000)

DRAM:  3.9 GiB
RPI 4 Model B (0xc03111)
Core:  135 devices, 14 uclasses, devicetree: board
MMC:   mmcnr@7e300000: 1, emmc2@7e340000: 0
Loading Environment from FAT... Unable to read "uboot.env" from
mmc0:1...
In:    serial
Out:   serial
Err:   serial
Net:   eth0: genet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (!SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
Port not available.
Hit any key to stop autoboot:  0
"Synchronous Abort" handler, esr 0x96000044
elr: 000000000009f3a8 lr : 000000000009572c (reloc)
elr: 000000003b36c3a8 lr : 000000003b36272c
x0 : 000000003af52610 x1 : 000000003af52680
x2 : 0000000000000051 x3 : 6964003b6963765f
x4 : 000000003b3d0890 x5 : 000000003b3d0890
x6 : 000000000000005b x7 : 000000003b3d0e30
x8 : 000000003b3d0820 x9 : 0000000000000008
x10: fffffffffffffff0 x11: 0000000000000006
x12: 000000000001869f x13: 000000003af3e708
x14: 000000003af3e810 x15: 0000000000000000
x16: 000000003b36d548 x17: 596fcb0297bbddff
x18: 000000003af48d70 x19: 0000000000000071
x20: 000000003b3d0880 x21: 0000000000000000
x22: 0000000000000005 x23: 000000000000000a
x24: 0000000000000001 x25: 000000003b3e4cd8
x26: 0000000000000000 x27: 000000003b3c4851
x28: 000000000000006d x29: 000000003af3d9e0

Code: a9410803 8b130001 b2400273 f9000413 (f9000c62)
Resetting CPU ...

resetting ...










# experimental u-boot


U-Boot> ver
U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +0000)

gcc (Debian 12.2.0-10) 12.2.0
GNU ld (GNU Binutils for Debian) 2.39.50.20221208
U-Boot> 

U-Boot> run bootcmd
"Synchronous Abort" handler, esr 0x96000044
elr: 000000000009f7e0 lr : 0000000000095e0c (reloc)
elr: 000000003b36c7e0 lr : 000000003b362e0c
x0 : 000000003af59470 x1 : 000000003af59490
x2 : 0000000030636d6d x3 : 5f646d63746f6f00
x4 : 0000000000000070 x5 : 000000003b3d0e08
x6 : 000000000000005b x7 : 000000003b3d13a8
x8 : 0000000000000050 x9 : 0000000000000008
x10: fffffffffffffff0 x11: 0000000000000006
x12: 000000000001869f x13: 000000003af3e708
x14: 000000003af3e810 x15: 0000000000000000
x16: 000000003b36d994 x17: d9ff4b22fffbdcff
x18: 000000003af48d70 x19: 0000000000000021
x20: 000000003b3d0df8 x21: 000000003af59d80
x22: 000000003af59b20 x23: 0000000000000010
x24: 0000000000000008 x25: 000000003b3e5258
x26: 0000000000000002 x27: 000000003b3c4e54
x28: 0000000000000073 x29: 000000003af3da10

Code: a9410803 8b130001 b2400273 f9000413 (f9000c62) 
Resetting CPU ...

resetting ...


U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +0000)
[...]

Reply via email to