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.

Omap5 is not getting booted if the ethernet cable is not connected

In the OMAP5 GLSDK 6.03.00.01 Release Notes, the following known issue is captured:

  • OMAPS00305059: Omap5 is not getting booted if the ethernet cable is not connected

I have observed this as well. Any idea when this will be resolved?

Why is the ethernet cable needed to complete boot? Is it just for the DHCP transaction to supply the board an IP address or is the board looking for files on the network?

Thank you in advance,

Joe

  • Hello Joe,

    No files are downloaded from the network.  It is just the DHCP transaction as you suspected in your post.

    GLSDK team is working on fixing these limitations. I am not sure when this will be fixed since GLSDK6_03 was release pretty soon, end of December as I recall.

    Best Regards,

    Yordan

  • Yordan.

    Now that I know its just the DHCP transaction that is needed to boot, I can build my prototype with the EVM knowing I just need a DHCP server and not full network connectivity.

    Thank you for your reply.

    Regards,

    Joe

  • Hi Joe,

    maybe you want to give it a try if you don't need the network feature upon boot: In one of my former setups I have seen the same issue and removed the ip=dhcp option in the kernel command line supplied by U-boot - there are boot script templates in the GLSDK board-support/prebuilt-images directory that can be used to create a new boot script using mkimage.

    Regards,

    Marc