Hello
We made the new board TMS320C6678.
Unfortunately, we do not have EVM.
We are checking tftp boot.
However, when tftp boot is executed, the message is displayed endlessly as follows.
I found the condition that tftp boot completes.
1. Power on the board.
2. Ping or arping from the host to the board.
host (ping or arping) => board (tms320c6678)
3. The board finishes booting after downloading app.out.
Is it true that tftp boot works this way?
I do not think this is a normal operation.
Can you tell us what we need to check and what needs to be corrected?
In addition, is there a way to output a message to the uart in ibl's ethboot.c?
I tried mprintf and uart_write_string but the device is not bootable.
The message below does not appear.
==================================================
IBL version: 1.0.0.17
IBL: PLL and DDR Initialization Complete
IBL Result code 00
IBL: Booting from ethernet
ipaddr: C0A800C3
serveripC0A800B9
netmask: FFFFFF00
hwaddr: 0EB7477278A7
filename: app.out
mdiolengh: 0A00
IBL: Booting from ethernet
ipaddr: C0A800C3
serveripC0A800B9
netmask: FFFFFF00
hwaddr: 0EB7477278A7
filename: app.out
mdiolengh: 0A00
IBL: Booting from ethernet
ipaddr: C0A800C3
serveripC0A800B9
netmask: FFFFFF00
hwaddr: 0EB7477278A7
filename: app.out
mdiolengh: 0A00
IBL: Booting from ethernet
ipaddr: C0A800C3
serveripC0A800B9
netmask: FFFFFF00
hwaddr: 0EB7477278A7
filename: app.out
mdiolengh: 0A00
=================================================
