This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM625: Ethernet Backup Boot Mode

Part Number: AM625
Other Parts Discussed in Thread: SK-AM62-LP

Tool/software:

We have a custom board using the AM6232, the Ethernet Phys are Micrel XZ8041 in RMII mode.

I have created the 3 files needed files from ti-u-boot-2024.04 and copied them to my DHCP/TFP server which is connected to the AM62 via a USB Ethernet port i.e. a dedicated port.

On power up I can see the initial TFTP for tiboot.bin work and the SPL executes.

Despite seeing the Phy being detected and the link being valid I do not see any tx output for the BOOTP broadcast.

Are there some areas you could suggest for me to look at to try and diagnose why the tx is not making it to the Ethernet output ?

Boot log is attached.

Thank you.

U-Boot SPL 2024.04-00002-gbaa288e477f-dirty (Mar 27 2025 - 09:38:30 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
SPL initial stack usage: 13392 bytes
Trying to boot from eth device
ethernet@8000000port@1 connected to Micrel KSZ804 mode rmii
eth0: ethernet@8000000port@1
ethernet@8000000port@1 Waiting for PHY auto negotiation to complete..... done
link up on port 1, speed 100, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17

Retry time exceeded; starting again
udma_stop_mem2dev: peer not stopped TIMEOUT !
Problem booting with BOOTP
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

  • Additionally, can you verify/share the following 

    1. Does Ethernet function properly when in U-boot prompt with the Ethernet PHY and RMII mode that you are using? Not Ethernet boot but testing Ethernet communication when U-boot is fully loaded.

    2. Are the device tree modifications you made for U-boot the same as your device tree for Linux where you previously confirmed Ethernet functionality was working in Linux?

    3. Can you share the .config for r5 and a53 stages as well as the full DTS you used for U-boot?

    -Daolin

  • Hi Daolin,

    1. if I stop u-boot in the console from an SD card boot I can DHCP and TFTP files with no problem.

    The servers are the same as when I try ethernet boot.

    2. Yes, they are the same.

    I'll try and locate the configs used for the buid.

    Regards

    Neil

  • The processor we are now looking at using does not support ethernet boot so I will close this thread. Thank you.