• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 550 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.

C6670 Ethernet boot: interframe spacing requirement

Victor Kazmirenko
Guru 13202 points

Hello!

I am experimenting with C6670 Ethernet boot. I'd like to ask for clarification.

What is required time spacing between Ethernet frames during boot table transfer process?

There is a reason I am asking. In my setup I was using virtual machine with Linux to boot and I have succeeded with boot when no intentional gap were inserted between the frames. However, partner of mine working in other environment found, that boot process does not complete. Experimentally we found, that minimal pause, like usleep(0) resolves the problem. So I'd like to know, what is exact requirement.

If that does matter, we use Ethernet frames with payload of 1468 bytes sans all headers, resulting in frame total length of 1514 bytes.

Thanks in advance.

  • 0
    TI__Guru** 116170 points

    I don`t think we have come across this issue while working with Ethernet boot on the device. I am checking internally if anyone else has had this issue.

    I will get back to you after I hear from the validation team.

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Guru 13202 points

    Hello!

    Any updates on the topic?

    I'd like to point your attention, that 'pcsendpkt' program from mcsdk_2_01_02_06\tools\boot_loader\examples\ethernet\Ethernet_boot\ does contain a large useless loop in the code between sending consecutive frames. That makes me suspect some gap is required, but not documented. Here is a piece:

    /* add delay between packets */
            for(i=0; i<DELAY; i++) {
                tmp4 = tmp3;
                tmp3 = tmp4;
            }