• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 824 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.

TM4C129ENCPDT: Does the BOOTP ROM feature work in XM4C129ENCPTI2 ?

john hoffman
Intellectual 750 points
Part Number: TM4C129ENCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL

The title is correct.

After struggling with trying to get BOOTP to work I started looking carefully at the errata and the TARGET_IS_TM4C129RAx macros.

I then looked at the MCU and discovered we bought XM4C129ENCPTI2 chips insted of TM4C129ENCPTI2 chips.

We have ordered the correct parts but I am curious if this feature is supported or not in both parts.

My understanding is that simply erasing the flash and powering up will result in bootp packets being emitted.

I don't see this in wireshark and LMFLASH does not work over ethernet. 

LMFLASH does work when direct connected to ICDI.

  • 0
    TI__Guru**** 191906 points
    Hi John,

    The XM4C129 is a pre-qualified part. The XM4C129 and TM4C129 should have the ROM bootloader for Ethernet. In the EK-TM4C1294XL LaunchPad we actually have the XM4C1294NCPDT on it. Are all the XM4C129 units you have have the same problem? With the TM4C129 units you now have, do you have any problems with Ethernet?
  • 0 in reply to Charles Tsai
    Intellectual 750 points
    We have a development kit which also has the XM part. I think it is the launch pad.
    I erased the flash using IAR iJet debugger and power cycled.
    I then sniffed for BOOTP protocol using wireshark. Nothing from this device.
    We Stellaris parts from a prior product that immediately transmit BOOTP requests from ROM bootloader when erased.
    I do see those packets in wireshark.
    The TM4C129 MCU is our stellaris replacement. We are just now getting into the port. So far the ROM bootloader over ENET does not appear to work.
  • 0 in reply to john hoffman
    TI__Guru**** 191906 points

    Hi John,

    Can you first try if the LaunchPad is working properly from the Ethernet ROM bootloader stand point? If it works, then you can isolate the problem as to focus on the differences between the launchPad and your custom board from the hardware standpoint . 

    On your development LaunchPad can you do the below?

     1. In the Configuration tab, go to the Quick Set and select TM4C1294XL LaunchPad

     2. In the Flash Utilities tab, click the Erase button to erase the flash. 

     3. Go back to Configuration tab and under the Quick Set select Manual Configuration. Under the interface select Ethernet. Provide the IP address and MAC address. See below example. You will have your own MAC and IP addresses.

      4. Under Program tab, select the .bin file that you want to download to the MCU using the ROM bootloader. I just tried to download a blinky example. You can use the wireshark to monitor the traffics. 

      5. Click the Program button.

  • 0 in reply to john hoffman
    Intellectual 750 points

    Ok, the issues i found are:
    I have one bad board oo 12 that does not issue BOOTP. (Don't you know it was the board I worked with from the beggining). That's why we build more than 1.
    We had an older build of lmflash (1470) that does not support TIVA. After upgrading to build 1613 lmflash works properly now on our boards and the launch pad..

    Oh ya.. thx for the responses. You have no idea how helpful it is to have someone knowledgeable to bounce ideas off of.

  • 0 in reply to john hoffman
    TI__Guru**** 191906 points
    Hi John,
    Glad your problem is solved!
  • 0 in reply to Charles Tsai
    Guru 117855 points

    Hi Charles,

    Bravo on the highly disciplined/detailed tech guidance - appears (just) what this poster needed.     (and great that he properly registered his appreciation.)

    When/if you have some free time - might you assist us in the, "Pilot's pre-flight checklist" - for our recently upgraded Cessna?     (I've already completed, "Check for presence - and "reasonable" intactness - of the Prop" - yet (more) such high detail IS required...AND appears, "Down your alley!"    Thanks)