• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 102 subscribers
  • Views 2241 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.

Keystone 2: ARM booting through ethernet (u-boot)

Ville Baillie
Genius 3480 points

Hi there,

I would like to use ethernet boot mode (ARM boot master) to run u-boot binary on the Hawking (TCI6636) chip.

The toolchain for making .out (ELF) file to .eth fileis used to convert the u-boot binary. pktsend.exe is then used to deliver the payload. U-boot does not then start.

Is there a different toolchain that should be used to achieve this booting mechanism?

Kind Regards,

Ville Baillie

  • 0
    TI__Guru* 81335 points

    Hi Ville,

    As of now ARM Ethernet boot is not supported in MCSDK 3.x. Your understanding may be correct. 

    1. Is this a hard requirement to boot from Ethernet?

    2. Are you working on EVM or Custom Board? 

    Thanks.

  • 0 in reply to Raja
    Genius 3480 points

    Hi Rajasekaran,

    This is a custom board. ARM ethernet bootmode is required at time of factory production (where the flash is blank and there is no access to CCS).

    Is there an erratum on ARM ethernet booting?

    Thanks

    Ville

  • 0 in reply to Ville Baillie
    TI__Guru* 81335 points

    Hi Ville,

    There is no issue with ARM Ethernet Boot. I am working with the team get more information on ARM Ethernet booting.

    Thank you for your patience.

  • 0 in reply to Raja
    TI__Guru* 81335 points

    Hi Ville,

    ARM Ethernet boot support may available in MCSDK release. I will keep you posted on this.

    Thanks.

  • 0 in reply to Raja
    TI__Intellectual 840 points

    Hi Ville,

    Please take a look at the Keystone II ARM Bootloader User Guide here: http://www.ti.com/lit/ug/spruhj3/spruhj3.pdf

    Section 3.8 will overview Ethernet boot. For ARM master booting, the image should be built into a BLOB (binary large object file .bin) and transferred using a BootP/TFTP protocol.

    I hope this helps. Please let me know if you have any other questions.

    Regards.

  • 0 in reply to Jon M
    Intellectual 840 points
    Hi,
    I am using EVM66AK2Hx kit. I am planning to load u-boot.bin thro ethernet booting.
    For doing this, I have set bootmode #5 (ARM RBL ENET) in BMC.

    My doubts are
    1.As per section 3.8 in document spruhj3.pdf, what should be source and destination ipaddresses? (will DIX frames carry those info?)

    2.How to make DIX frames. Is there any utility available for conversion?

    3. is u-boot.bin in blob format? or is there any tool chain available to convert it in blob format?

    4.In addition to this how the bootloader will fetch data from the tftp server without having server ipaddress?

    Kindly clarify.

    Regards,
    Sivanantham
  • 0 in reply to Sivanantham S
    TI__Guru** 116100 points

    Please refer to the following TI links.
    processors.wiki.ti.com/.../KeystoneII_Boot_Examples
    PATH: ~\keystone2_boot_examples-keystone2_boot_examples-master\keystone2_boot_examples-keystone2_boot_examples\examples\k2h\uboot

  • 0 in reply to Titusrathinaraj Stalin
    Intellectual 260 points

    Hi Ville, how has your ethernet boot been working out for you?

    Raja, we are also in the same boat, we have to use ethernet boot as that is how our system is designed.  We have not been getting 100% reliable booting, and have started examining the packets coming out of the keystone 2 part.  We are seeing packets with invalid preamble's 9 6 octets of 0x55 instead of the 7 expected).  The shorter preamble seems to be indicating a request for "carrier extenstion" although I am not sure what that is.

    We also get a lot of "Frame check sequence: 0x00000000 [incorrect, should be 0x5f00909c]" errors in wireshark, does the keystone 2 not use frame #'s?

    We have setup our system such that when it fails to download uboot, we toggle RESETFULL on the keystone2 till uboot is downloaded into RAM.  Our first attempt successfully gets uboot about 82% of the time, and the rest we have to retry using the reset method described above.  

    How rigorously is the keystone 2 ethernet boot method tested?  How can we get some technical input regarding this?

    Thanks