I have a question about the fallback boot mode of the BeagleY-AI.
In the schematic, I saw that Ethernet is selected as the fallback boot mode.
So far, I have only used network booting for the Linux side (Kernel/DTB via TFTP and RFS via NFS), not for U-Boot. However, this could be an interesting use case for bootstrapping systems without an SD card, or when DFU is not available to load U-Boot, for example.
I searched for documentation on how to use this feature. I found something in the AM67A TRM, which at least explained the technical background, but of course it did not provide any examples of usage. The TI SDK documentation didn’t help me much either. This is also because it references vendor-class-identifiers from the AM335x.
Overall, I expected to see packets from the board when booting it without an SD card inserted. I had hoped to see something that would allow me to obtain the actual vendor-class identifier for properly configuring my DHCP server.
The following sentence is written inside TRM (under 5.4.5.1.2 Ethernet Loading Process):
After device configuration, the bootloader performs a standard BOOTP/TFTP boot. The device sends a BOOTP request with its MAC address to a host TFTP server to be assigned an IP from a pool of addresses. The timeout for each BOOTP packet is 4 seconds, and the ROM will attempt 10 BOOTP retries, after which the boot mode will fail.
So there should be packages visible, or?
It’s possible that my approach was simply incorrect. I tried the following: `sudo tcpdump -i enp1s0 -v -n port 67 or port 68`
So, my question is: Has anyone tried this successfully? If so, what might I have missed?