• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 1437 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.

Accidentally erased flash/MAC on TM4C129XNCZAD Evaluation Board

Marshall Folkman
Intellectual 720 points
Other Parts Discussed in Thread: TM4C129XNCZAD, LMFLASHPROGRAMMER

I think I accidentally erased the flash/MAC on my TM4C129XNCZAD Evaluation Board. I opened the LM Flash Programmer 1588 tool and attempted to "Debug Port Unlock" with the "Fury, DustDevil, and Blizzard Classes" option selected, as shown below.

However, as you can see, the MAC Address seems to be lost and won't even discover my device to load changes. As I follow the instructions shown below (aka. I unplug the device from my computer and then plug it into my computer again as I am holding down the reset button).

I then recieve the following error message.

Also, if it helps, the only LED light on on the board is the orange "5V ON" light. The "3.3V ON" light and the debugger LED's are not light up.

Marshall

  • 0
    TI__Guru**** 244400 points
    Hello Marshall

    The current version of LMFlashProgrammer is 1613. Did you try a readback of the MAC address using this version of LMFlashProgrammer?

    Also can you send a snapshot of the board indicating which LED's are ON?

    The EK-TM4C1294 has a sticker on the back or in the box with the MAC Address.

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Intellectual 720 points

    I tried it on version 1613. The MAC address does not readback. I am using the TM4C129X, not the TM4C1294...if that matters. But no I do not see a sticker on the back or in the box about the MAC address. Do I absolutely need the MAC address to fix this?

    Here is the picture you requested...

  • 0 in reply to Marshall Folkman
    TI__Guru**** 244400 points
    Hello Marshall,

    Sorry, I got it confused with the LaunchPad. Can you check if the 3.3V regulator (U7) input and output are working fine? Was there anything else being done during the process which could have caused an over-current to U7.
    If the output of U7 is not at 3.3V then basically the debugger TM4C123 and the main device TM4C129 are not going to function and hence the error message. What I can suggest is to revert the board to factory connections and then try again to see if 3.3V comes up, If still it does not then replace U7.
    There is a rather unsafe method of removing jumper J8 and use a 3.3V external power supply with current limit at no more than 200mA to power the board. Why unsafe, is because I have not tried it yet...

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Intellectual 720 points
    I'm sorry, what is U7?
  • 0 in reply to Marshall Folkman
    TI__Guru**** 244400 points
    Hello Marshall,

    U7 is the regulator TPS62177DQC for converting 5V to 3.3V for supplying VDD and VDDA of TM4C129 main uC and TM4C123 ICDI. Please refer to schematics in the DK-TM4C129x User Guide Page 33

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Intellectual 720 points
    Using a multimeter, I do not get 3.3V at the "3.3V ON" terminal (lower left side of the board), but when I take off the J8 Jumper and measure the voltages of those pins, I get 0V for the "POWER" pin and about 3.3V for the "3.3V" pin. When I put the jumper back on and measure (connecting the two pins) I get practically 0V.

    Also I really don't see how I could have fried anything because it started doing this as I attempted to load code onto the board, it told me that it was trying to erase flash due to some error. Not wanting it to erase the flash memory, I disconnected the device from my computer. The device was working right before that. The only difference I made in my code is that I included a PinMux Generated file to configure my pins, which is something I have never tried before. I had already configured the peripherals and tested them. I was using converting things over to Pin mux to allow for easier reconfigurations in the future if needed. I went through the program and erased all of the tivaware lines that were redundant. I really don't think that this could have caused an overcurrent problem, but I guess anything is possible.
  • 0 in reply to Marshall Folkman
    Intellectual 720 points
    Also, U7 is very small. How should I go about getting it replaced? Can I send it in to TI, or do I need to take care of it myself?
  • 0 in reply to Marshall Folkman
    TI__Guru**** 244400 points
    Hello Marshall,

    Before replacing U7 do run the test as suggested. TI will not be replacing the parts and it is upto the user (unless the board came broken)

    Regards
    Amit
  • 0 in reply to Amit Ashara
    Intellectual 720 points
    It looks as though I will need to replace U7. Thank you Amit for your diligent efforts to help me.

    Marshall