• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 374 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.

Original question:

AM625: tispl download u-boot

AM625: Uboot dowload by tftp

Huy Khuat
Intellectual 621 points
Part Number: AM625


Tool/software:

Hi TI expert,

I want to reopen the ticket https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1424939/am625-tispl-download-u-boot.

Regarding the old ticket, we encountered an issue when tispl.bin loads u-boot.img, which dropped the first four frames and slowed down the boot process. We worked around this by reducing the timeout duration, which improved the loading speed of u-boot.img. However, when u-boot.img is loading the kernel, the TFTP server sends an error code to the bus in response to the frame loading u-boot.img.


I have attached the Wireshark file below.

1300.wireshark.zip

Could you help us analyze this issue and suggest a solution?

Thanks,

Huy

  • 0
    TI__Genius 17245 points

    Hello Huy,

    Is this the same exact issue as described in the linked thread: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1424939/am625-tispl-download-u-boot?

    If so, I can reopen the linked thread to continue the conversation there. 

    If this is a different related issue, we can continue the investigation here.

    Assuming this a different related issue:

    1. Do you observe these TFTP error packets (the packets with the error codes) only when loading the kernel image? I.e. the error packets are consistently observed every time when loading the kernel image?

    2. Do you observe these TFTP error packets after U-boot is loaded and U-boot is not actively trying to load the kernel image? The point I'm trying to ask is if these error packets are observed after some delay after U-boot is loaded and not necessarily a result of loading the kernel image?

    3. What SDK version are you using?

    Huy Khuat said:
    We worked around this by reducing the timeout duration, which improved the loading speed of u-boot.img.

    4. How are you reducing the timeout duration? Are you changing anything related to the Ethernet packet size? We ask this because we see a lot of fragmented frames in your Wireshark capture.

    -Daolin

  • 0 in reply to Daolin Qiu
    Intellectual 621 points

    Hi Daolin,

    Yes, it is the same issue described in the linked thread. You can reopen the linked thread.

    1. Yes, as I observed, this error always occurs when loading the kernel image.

    2. Yes, I observed these TFTP error packets after U-Boot is loaded, even when U-Boot is not actively trying to load the kernel image. The errors appear after some delay following the loading of U-Boot and are not necessarily a result of loading the kernel image. 

    I attached the log and Wireshark capture when trying this case.report_2_20_25.zip

    3. we are using sdk 8.6: ti-processor-sdk-linux-am62xx-evm-08.06.00.42

    4. I changed the codes here:

    This configuration CONFIG_NET_BYPASS_BROADCAST is enabled only when I build tisbl.bin.

    Thanks for the quick support!

    Huy

  • 0 in reply to Huy Khuat
    TI__Genius 17245 points

    Hello Huy,

    Huy Khuat said:
    Yes, it is the same issue described in the linked thread. You can reopen the linked thread.

    The other thread is now unlocked, please make sure to respond to the other thread with an update on what had changed since the last communication 2 months ago and the current observed issue (i.e. the details in this thread).

    Since it is the same issue, let us continue the conversation on the other thread to keep the information consistent.

    -Daolin 

  • 0 in reply to Daolin Qiu
    Intellectual 621 points

    Hi Daolin,

    I still see that thread is locked, can you check it again for me?

    Thanks,

    Huy

  • 0 in reply to Huy Khuat
    TI__Genius 17245 points

    Hi Huy,

    Thanks for bringing this to my attention. I think the post got locked automatically after I unlocked it yesterday. I've unlocked it again and put a response to the thread to see if that keeps the thread open.

    Please let me know if you still have trouble responding to the unlocked thread.

    -Daolin