On 19.02.24 19:37, Jan Kiszka wrote:
On 17.02.24 12:36, Alexander Sverdlin wrote:
Hi Jan!
On Sat, 2024-02-17 at 09:42 +0100, Jan Kiszka wrote:
U-Boot 2024.01 (Feb 15 2024 - 01:43:17 +0100)
SoC: AM62X SR1.0 HS-FS Model: Texas Instruments AM625 SK DRAM: 2 GiB Core: 56 devices, 23 uclasses, devicetree: separate MMC: mmc@fa10000: 0, mmc@fa00000: 1 Loading Environment from nowhere... OK In: serial@2800000 Out: serial@2800000 Err: serial@2800000 Net: eth0: ethernet@8000000port@1 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device SD/MMC found on device 1 Failed to load 'uEnv.txt' Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': No EFI system partition No EFI system partition Failed to persist EFI variables Scanning bootdev 'mmc@fa00000.bootdev': Scanning bootdev 'mmc@fa10000.bootdev': Unknown uclass 'usb' in label link up on port 1, speed 100, full duplex BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 ...
I suppose TI's BSP has older U-Boot... So it's not providing necessary script for BOOTSTD, I suppose?
You can make the BeagleBone boot via EFI, but it requires a hybrid partition table (ROM loader want DOS, EFI needs GPT). A Debian integration with this can be found for Isar [1] in this series [2]. It's only using upstream sources (plus still one u-boot patch to get wifi working).
If you want legacy script booting, I suspect you need to flip some extra switches explicitly by now.
Thanks for the hints! I'm wondering, if this was a deliberate "let's stop booting all the pre-existing embedded distros" decision? (buildroot, yocto/meta-ti...)
FWIW, I'm not seeing other boot methods being specifically disabled in beagleplay in 2024.01 or even newer. I didn't try the result, but this may actually be some other issue and real bug, nothing obviously intended.
I'm not even sure about this anymore, though there is still a bug, just a different one:
... U-Boot 2024.04-rc2-00040-g3e6f2a94bfc (Feb 20 2024 - 08:42:59 +0100)
SoC: AM62X SR1.0 GP Model: BeagleBoard.org BeaglePlay DRAM: 2 GiB Core: 98 devices, 27 uclasses, devicetree: separate MMC: mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2 Loading Environment from nowhere... OK In: serial@2800000 Out: serial@2800000 Err: serial@2800000 Net: No ethernet found.
Press SPACE to abort autoboot in 2 seconds => print bootmeths bootmeths=script extlinux efi pxe => bootflow scan -l Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning bootdev 'mmc@fa00000.bootdev': 0 efi ready mmc 2 mmc@fa00000.bootdev.part_ efi/boot/bootaa64.efi Scanning bootdev 'mmc@fa10000.bootdev': 1 extlinux ready mmc 1 mmc@fa10000.bootdev.part_ /extlinux/extlinux.conf Unknown uclass 'usb' in label "Synchronous Abort" handler, esr 0x86000004, far 0x3030303030303840 elr: 3030302fb0bc0840 lr : 3030302fb0bc0840 (reloc) elr: 3030303030303840 lr : 3030303030303840 x0 : 00000000ffffffed x1 : 0000000000000000 x2 : 0000000000000002 x3 : 00000000ffb49d30 x4 : 00000000fffd4c00 x5 : 00000000ffb49d50 x6 : 0000000000000000 x7 : 00000000ffb4e890 x8 : 0000000000006924 x9 : 00000000ffb1212c x10: 0000000000000003 x11: 0000000000006914 x12: 00000000ffb1221c x13: 00000000ffb12b40 x14: 00000000ffb12b40 x15: 00000000ffb12535 x16: 00000000fff8a9d4 x17: 0000000000000000 x18: 00000000ffb23da0 x19: 0000314074726f70 x20: 00000000fffed000 x21: 00000000fffef000 x22: 0000000000000000 x23: 00000000fffef000 x24: 00000000fffef000 x25: 0000000000000000 x26: 00000000fffc7174 x27: 0000000000000000 x28: 0000000000000000 x29: 74656e7265687465
Same with 2024.01 release.
Jan