> 
> Hey,
> 
> After going from Vendor SPL/OpenSBI/U-Boot to OpenSBI v1.4++ plus
> v2024.07-rc4 SPL/U-Boot I ran into a boot loop problem relating to
> PCI:
>       U-Boot 2024.07-rc4 (Jun 13 2024 - 15:09:34 +0100)
> 
>       CPU:   sifive,u74-mc
>       Model: StarFive VisionFive 2 v1.2A
>       DRAM:  4 GiB
>       Core:  136 devices, 26 uclasses, devicetree: board
>       WDT:   Not starting watchdog@13070000
>       MMC:   mmc@16010000: 0, mmc@16020000: 1
>       Loading Environment from SPIFlash... SF: Detected gd25lq128 with page
> size 256 Bytes, erase size 4 KiB, total 16 MiB
>       OK
>       StarFive EEPROM format v2
> 
>       --------EEPROM INFO--------
>       Vendor : StarFive Technology Co., Ltd.
>       Product full SN: VF7110A1-2249-D004E000-00000540
>       data version: 0x2
>       PCB revision: 0xa1
>       BOM revision: A
>       Ethernet MAC0 address: 6c:cf:39:00:17:95
>       Ethernet MAC1 address: 6c:cf:39:00:17:96
>       --------EEPROM INFO--------
> 
>       starfive_7110_pcie pcie@2b000000: Starfive PCIe bus probed.
>       starfive_7110_pcie pcie@2c000000: Starfive PCIe bus probed.
>       In:    serial@10000000
>       Out:   serial@10000000
>       Err:   serial@10000000
>       Net:   eth0: ethernet@16030000, eth1: ethernet@16040000
>       starting USB...
>       Bus xhci_pci: Register 5000420 NbrPorts 5
>       Starting the controller
>       USB XHCI 1.00
>       scanning bus xhci_pci for devices...
>       U-Boot SPL 2024.07-rc4 (Jun 13 2024 - 15:09:34 +0100)
>       DDR version: dc2e84f0.
>       Trying to boot from SPI
> 
> This only appeared after I refreshed the environment by running.
> `env default -a -f; env save`. Before that things worked "fine", I suppose 
> because
> nothing actually touched PCI. I've just disabled PCI for now and things are
> working once more. I've not attempted to bisect/debug this, cos that's not the
> fastest process while running U-Boot out of flash.
> 
> In case it is relevant, the board I have is one of the "super early bird" 
> ones.
> 
> Cheers,
> Conor.

CC  Hal

Reply via email to