TM4C129XNCZAD: controller not getting program

Hello Ramesh,

The screenshot did not load, please try and upload it again. Select the Insert/Edit Media option.

Just to take a shot in the dark, if you think the device has gotten locked, you can use LM Flash Programmer to do a Debug Port Unlock on the Other Utilities tab.

Hi,

 Below the error I am getting

Downloading \\mstm1bdfs01\mst-home\bom50\home\nagarr4\study\project_Recharger\EMI\EMILAB_Results\TUV\07022019\UIS_Board_Tests_EVT_4mA_5MHz.bin to TM4C129XNCZAD via JTAG-Interface@1000kHz

Programming Thread started.

Device "TM4C129XNCZAD" selected.

TotalIRLen = 4, IRPrint = 0x01

JTAG chain detection found 1 devices:

#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP

Scanning AP map to find all available APs

AP[0]: Stopped AP scan as end of AP map seems to be reached

Iterating through AP map to find AHB-AP to use

Scanning AP map to find all available APs

AP[0]: Stopped AP scan as end of AP map seems to be reached

Iterating through AP map to find AHB-AP to use

TotalIRLen = 4, IRPrint = 0x01

JTAG chain detection found 1 devices:

#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP

Could not find core in Coresight setup

Programming Thread exited

Initialization of debug session failed.

Could not connect to target.

Also tried to erase the program in the controller through jtag (j link ) the following error I am getting

Erasing TM4C129XNCZAD via JTAG-Interface@1000kHz

Erase Thread started.

Device "TM4C129XNCZAD" selected.

TotalIRLen = 4, IRPrint = 0x01

JTAG chain detection found 1 devices:

#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP

Scanning AP map to find all available APs

AP[0]: Stopped AP scan as end of AP map seems to be reached

Iterating through AP map to find AHB-AP to use

Scanning AP map to find all available APs

AP[0]: Stopped AP scan as end of AP map seems to be reached

Iterating through AP map to find AHB-AP to use

TotalIRLen = 4, IRPrint = 0x01

JTAG chain detection found 1 devices:

#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP

Could not find core in Coresight setup

Erase Thread exited

Initialization of debug session failed.

Could not connect to target

let us know any information

Greetings Ralph,

Should not it be mentioned - that, 'Poster's last: method/program/handling' most likely 'Caused such Issue' - and unless 'found & corrected' - he stands, 'Primed for Immediate, Issue Re-Entry!'

A mismatch in Setting MCU Speed or the (deliberate or unintended Re-Purpose of JTAG Pins) stand as, 'Most reasonable (and likely) of suspects' - and should be 'VERY CAREFULLY INVESTIGATED' and CORRECTED/MADE PROPER!

Hello cb1,

That is very true as well, yes when the board is recovered and verified to be working with a known good example, the code that caused the device to be locked needs to be reviewed starting with the clock settings.

Hi,

 We are also using CCS ,Also same program working in other boards.

Not working we done unlock for the controller as per below document

Reference :Using TM4C12x Devices Over JTAG Interface.pdf

Section : unlock Sequence Using Uniflash and XDS Debug Probes & page 25 (using XDS200 debug probes)

But still getting same error

Hello Ramesh,

Did you get confirmation that the Debug Port Unlock was successful?

If so, can you try downloading the BIN file with CCS Uniflash? Even if it was made in Keil, it should be loadable with Uniflash as long as it's a .bin.

If you power up the custom board and use a scope on the TDO signal (with the pull-up on TDO) do you see any toggling on the pin, even without any JTAG connection being launched? And if so, at what frequency?

Hi Ralph

Yes we able to observed Debug port unlock successful. But we tried to load the .bin file through J flash following error getting

Downloading H:\study\project_Recharger\EMI\EMILAB_Results\TUV\07022019\UIS_Board_Tests_EVT_4mA_5MHz.bin to TM4C129XNCZAD via JTAG-Interface@1000kHz
Programming Thread started.
Device "TM4C129XNCZAD" selected.
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
 #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map seems to be reached
Iterating through AP map to find AHB-AP to use
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map seems to be reached
Iterating through AP map to find AHB-AP to use
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
 #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
Could not find core in Coresight setup
Programming Thread exited
Initialization of debug session failed.
Could not connect to target.
 

For  erasing following error getting

Erasing TM4C129XNCZAD via JTAG-Interface@1000kHz
Erase Thread started.
Device "TM4C129XNCZAD" selected.
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
 #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map seems to be reached
Iterating through AP map to find AHB-AP to use
Scanning AP map to find all available APs
AP[0]: Stopped AP scan as end of AP map seems to be reached
Iterating through AP map to find AHB-AP to use
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
 #0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
Could not find core in Coresight setup
Erase Thread exited
Initialization of debug session failed.
Could not connect to target.
 

Also tried bin file with CCS uniflsh

the .bin file not loading we checking the hardware pin configurations( jtag pull up and pull down).

We are checked TDO signal no signal toggling in the pin

ramesh n said:

Also tried bin file with CCS uniflsh

Crack staffer (et moi)  read that earlier as, 'Uni-FISH!.'     Indeed ... vowels (a) DO serve a purpose! 

Quick trip to Wikipedia:  'Uni-FISH' - "An Aquatic environment - initially inhabited by multiple fish - with (one/largest) proving especially hungry/aggressive - thus now alone!"    Cross referenced to, 'Last Mohican' - for those 'shore-bound.'

Hello Ramesh,

How many boards are exhibiting this issue? And how many total boards do you have running with the same program?

If the Debug Port unlock is a success then you shouldn't have issues with the programming.

After the Debug Port unlock, can you try reading the Flash memory from the device?

Hi Raalph Jacobi,

 Thanks for the support,

Only one board we are facing the issue and we are verified the same program more then 10 boards is working fine.

Regards

Ramesh N

Hello Ramesh,

And have you tried reading the Flash after a successful debug port unlock? If so what happens?

Also have you tried using a different programmer or cable just to rule out something with the programming tool?

Hi Ralph Jacobi,

I did not tried reading the flash. If you tell me procedure we will try to read the flash.

I tried Another j link (jtag) but results are same.

Hello Ramesh,

You can do that with CCS Uniflash going to the memory tab and clicking "Read Target Device".