On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote:
> 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.
[...]
> I upgraded only u-boot.bin from bookworm/sid/experimental
[...]
> The unstable and experimental versions both caused a reset
> after run bootcmd and before "Starting Linux...".
[...]


After upgrading rpi firmware files to latest release/tag
also the unstable and experimental u-boot seemed to boot
fine (no reset, garbage on console after linux started).


### unstable u-boot with rpi firmware-1.20221104.tar.gz

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

DRAM:  3.9 GiB
RPI 4 Model B (0xc03111)
Core:  209 devices, 16 uclasses, devicetree: board
MMC:   mmcnr@7e300000: 1, mmc@7e340000: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... 
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> 
U-Boot> run bootcmd
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
U-Boot menu
1:      Debian GNU/Linux 5.7.0-1-arm64
2:      Debian GNU/Linux 5.7.0-1-arm64 (rescue target)
Enter choice: 1:        Debian GNU/Linux 5.7.0-1-arm64
Retrieving file: /boot/initrd.img-5.7.0-1-arm64   
Retrieving file: /boot/vmlinuz-5.7.0-1-arm64
append: root=LABEL=root ro rootwait console=ttyS1,115200
Retrieving file: /usr/lib/linux-image-5.7.0-1-arm64/broadcom/bcm2711-rpi-4-b.dtb
## Flattened Device Tree blob at 02600000
   Booting using the fdt blob at 0x2600000
   Using Device Tree in place at 0000000002600000, end 000000000260896e

Starting kernel ...

[... garbage characters...]


### experimental u-boot with rpi firmware-1.20221104.tar.gz

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

DRAM:  948 MiB (effective 3.9 GiB)
RPI 4 Model B (0xc03111)
Core:  209 devices, 16 uclasses, devicetree: board
MMC:   mmcnr@7e300000: 1, mmc@7e340000: 0
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
In:    serial  
Out:   serial  
Err:   serial  
Net:   eth0: ethernet@7d580000
PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00  
scanning bus xhci_pci for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
U-Boot>
U-Boot>
U-Boot>
U-Boot> run bootcmd
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
U-Boot menu
1:      Debian GNU/Linux 5.7.0-1-arm64
2:      Debian GNU/Linux 5.7.0-1-arm64 (rescue target)
Enter choice: 1:        Debian GNU/Linux 5.7.0-1-arm64
Retrieving file: /boot/initrd.img-5.7.0-1-arm64
Retrieving file: /boot/vmlinuz-5.7.0-1-arm64
append: root=LABEL=root ro rootwait console=ttyS1,115200
Retrieving file: 
/usr/lib/linux-image-5.7.0-1-arm64/broadcom/bcm2711-rpi-4-b.dtb  
## Flattened Device Tree blob at 02600000
   Booting using the fdt blob at 0x2600000
Working FDT set to 2600000
   Using Device Tree in place at 0000000002600000, end 000000000260896e
Working FDT set to 2600000

Starting kernel ...

[...garbage characters...]


Regards,
Andreas Henriksson

Reply via email to