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.

TM4C1294KCPDT: Device not getting programmed

Part Number: TM4C1294KCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL, UNIFLASH

We are getting problem while programming through Blackhawk XDS100V2.

 

Device used: TM4C1294KCPDT.

 

PFA screenshot of the error message.

 

Please help us to resolve the problem immediately.

  • What board is the TM4C129 on? Is it a new custom board? If so, please check power, both 3.3V and 1.2V, and GND connections. Verify that the oscillator is operating. Finally double check your JTAG connections.
  • Hi bob,

    It is a new custom board. We have cross checked 3.3V , 1.2V & GND connections, all are OK.

    Oscillator is also working fine.

  • Some suggestions:

    To check if your problem is related to the XDS100:

    - Can you program any other board with your interface? Are you sure the drivers are installed properly and working?

    - Not too common, but long USB cables or connected to hubs tend to cause headaches.

    To check if it is a problem with your board:

    - Can you program it using a "simpler" interface (I really mean using a EK-TM4C1294XL Launchpad to program your board via ICDI)?

    Did you try to unlock your JTAG port?

    Bruno

  • I suggest you double check the JTAG connections. If you want, post a picture of your schematic showing the JTAG connections you used. Then verify your target configuration. I assume you created your own target configuration with XDS100v2-USB and a TM4C129xx. It should look something like the picture below:

    If the configuration looks good, what happens when you press the "Test Connection" button?

  • Hi bob,

    the problem has been solved some days ago & the TM4C programmed.

    But now again its started to show the same error.

    is it a problem with the controller? or with JTAG programmer? not able to decide properly.

    Also Reset is not is coming from JTAG connector. But its been able to program different design boards.

  • When you have problems programming the board, have you tried the "Test Connection" I suggested above? JTAG signals are very sensitive to reflections and cross talk. A reflection on the TCK line will cause the microcontroller to see an extra clock edge and we out of synchronization with the JTAG programmer. This can often be seen as an intermittent problem.

    The device "Reset" is not required by the JTAG programmer as a system reset can be generated by scan. Device reset is not available on the 14-pin TI header. Test reset (nTRST) is a reset to the JTAG state machine. Depending on the programmer's software this signal may not be asserted as the JTAG test reset state can also be achieved by scan.
  • Hi bob,

    Checked in alternate PCs & the device is programming, i think its driver issues.

    I used uniflash to load the program.

    But i uninstalled all drivers & reinstalled ,tried but it seems to be not programming.

    Again checked in another PC it is programming.

    Can u help with this. I have updated drivers. 

  • Hello again,
    If you can please check and answer the 4 investigation questions that I suggested early in Mar 15th above, it will help trying to isolate the cause of your problem.
    Bruno