• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 101 subscribers
  • Views 259 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM3351: USB boot timeout

Michael Shklyarman
Genius 12850 points

Part Number: AM3351

Champs,

A customer has successfully booted a custom board over USB, and written boot images into NAND. Now, we are trying to let USB boot timeout and jump to NAND boot but this does not seem to happen. I am not able to find the duration of the timeout in case of failed peripheral boot in the TRM. Questions:

1. How long is the timeout?

2. How exactly the timeout is implemented? Is it watchdog based? Is it possible for the USB (network) boot to get stuck in a state where failure isn't properly registered and RBL won't proceed to the next device in the list?

thank you

Michael

  • 0
    TI__Guru**** 177101 points

    Hi Michael,

    I am routing your query to our ROM expert for comments.

  • +1 in reply to Bin Liu
    TI__Guru* 92350 points

    Michael, i checked this a long time ago.  For client boot, if you connect to windows host with no proper driver loader, the timeout is 20 seconds (enumeration fails, no RNDIS driver).  For a linux host, if the DHCP or TFTP server exists, but the MLO does not, there is a 5 second timeout.  For no TFTP server response, there are 5 retries every 1 minute, so there will be a 5min timeout

    Regards,

    James