On 08:48-20240220, Jan Kiszka wrote: > 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 am pretty sure ethernet is not enabled in upstream u-boot. > >>>> ... > >>>> --- > >>>> > >>>> 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...) It was more of a "lets standardize one way of booting across all ARM devices as much as we can" effort - EBBR and others inclusive. To that effort, distro_boot and bootstd have made significant steps forward. NOTE: yocto, buildroot etc will need a few tweaks to get things operational unfortunately. BUT, note: bootstd was what beagleplay was introduced upstream as default in the first place - so all we are finding is that introduced behavior. > >> > > > > 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. boot_targets=mmc1 mmc0 usb pxe networking ran into some significant challenges. I was hoping to get networking merged but the series got offset and network never made it.. Dropping pxe from boot_targets => setenv boot_targets mmc1 mmc0 usb => print bootmeths bootmeths=script extlinux efi pxe => print boot_targets boot_targets=mmc1 mmc0 usb => bootflow scan -l Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning bootdev 'mmc@fa00000.bootdev': 0 extlinux ready mmc 1 mmc@fa00000.bootdev.part_ /extlinux/extlinux.conf Scanning bootdev 'mmc@fa10000.bootdev': 1 extlinux ready mmc 1 mmc@fa10000.bootdev.part_ /extlinux/extlinux.conf Unknown uclass 'usb' in label No more bootdevs --- ----------- ------ -------- ---- ------------------------ ---------------- (2 bootflows, 2 valid) => -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
