TM4C123BH6ZRB: Different behavior between Date Codes

Hi Sebastian,

  Can you elaborate what you meant the chip is destroyed. Can you still unlock the device? Can you still connect to the device? As far as I can tell, both are rev7 silicon and left one was manufactured in 2019-May and the right side one was manufactured in 2019-December. I can check internally if there is any known issue with the lots for the 2019-December builds. 

HI,

  We check the internally and the yield is normal and no outliers or any special processing. How many chips do you see the problem or just one. Please also reply me on what exactly you meant the device is destroyed. 

Hey Charles,

thanks for lookin into it. We need to wait till tuesday for the SW department to return to work to get more insights.

We have 4 out of 6 TM4C123 who are not reacting via Debbuger

As a debugger a EK-TM4C123GXL is used with a connector from the JTAG

Hi Sebastian,

  Thanks for the update. Let me try to understand a little bit better on the debug environment.

  - You are trying to use the EK-TM4C123GXL LaunchPad as a debug probe to debug your target device TM4C123BH6ZRB. Is this a correct understanding?

  - What if you use other debug probes (e.g. XDS200 or others). Will you see the problem as reported?

  - Can you monitor the JTAG interface between the EK-TM4C123GXL and the target device on a scope? Is there any over-voltage on the JTAG signals?

  Please also note that while it is technically ok to use the  EK-TM4C123GXL as a debug probe with blue wires connecting to the target, the launchPad is not meant to replace a commercially available debug probes for full software development. Some of the debug probes such as XDS100v2 can be obtained for about $100. Higher performance debug probe such as XDS200 can be obtained for about $300. 

Hi Charles,

With not functional i got the feedback from the SW deparment, there is no erase, program oder anything else possible with the device (either with CCS or LM Flash Programmer

See below

Connection with LM FLash Programmer + Launchpad

Erase:

Program:

Hardware Reset:

Hi,

  Your images were not uploaded successfully. Please use the icon below to upload your images. 

Sorry here with Images:

Thanks for the images. This only tells there is a JTAG connection issue. It doesn't prove the fact that the device is destroyed as you mentioned in the original post although a damaged chip cannot be ruled out.

Can you please answer the questions I asked in my last reply. Let me repeat the same question again with additional questions. 

  - You are trying to use the EK-TM4C123GXL LaunchPad as a debug probe to debug your target device TM4C123BH6ZRB. Is this a correct understanding?

  - Can you show the Windows Device manager. Do you see the ICDI enumeration.

  - What program was in the flash memory before you try to connect? Were you able to connect to the device before but after some program was loaded, it does not load again? If there is a misconfiguration of clock, for example, kills all the clocks for low power mode without a mechanism to wake up the device can result in the debugger unable to connect to the device. 

  - What if you use other debug probes (e.g. XDS200 or others). Will you see the problem as reported? If you can connect using other debug probes then the device is not destroyed. It is a debug probe issue to look at. 

  - Can you monitor the JTAG interface between the EK-TM4C123GXL and the target device on a scope? Is there any over-voltage on the JTAG signals?

  Please also note that while it is technically ok to use the  EK-TM4C123GXL as a debug probe with blue wires connecting to the target, the launchPad is not meant to replace a commercially available debug probes for full software development. Some of the debug probes such as XDS100v2 can be obtained for about $100. Higher performance debug probe such as XDS200 can be obtained for about $300. 

  Also wanted to give a heads-up. There is a US holiday coming and i will be on vacation for the rest of the week.