TM4C123GH6PM: ERROR IN TARGET DETECTION

Hi,

 Was the board working before? If it was working before, do you remember what you might have changed in your code (i.e. change the system clock so the frequency becomes less than 10x over the JTAG frequency or you have configured some GPIO pins that were by default to be used for JTAG interface) prior to having the target connection problem?

 Do you have another board that you also try? Just wanted to make sure if it is related to any driver or CCS issues.

 Lastly, can you manually launch the target configuration?

 1. Right-click on your target configuration and select Launch Selected Configuration.

2. In the Debug window, right-click on the Stellaris In-Circuit Debug Interface_0 and select "Connect Target"

Feel your pain - and just as you note - this incidence proves FAR TOO HIGH!

As vendor's Charles well notes - important projects MUST anticipate such issues - multiple target platforms provide added "recovery options."

It is important that you clearly respond to the questions/issues noted by Charles. I would also note that, "Projects are pending ONLY due to that" proves "highly" optimistic - and equally unlikely...

Yes, the board was working before. I haven't changed any GPIO which was to be configured as JTAG pin. I was doing the TiVa C launchpad workshop series only. 

I tried connecting the target manually as well but again I'm not able to connect the target. It's showing "Unable to connect target board". I don't have other TiVa C launchpad else than this one. Is there any other method to recover the board again?

Thanks for your valuable suggestions.

hello charles,

yes ,using Lm flash programmer i unlocked the device .but on doing the ICDI firmware update meassage popping up is "FAILED TO CONNECT TO THE DEVICE".

Greetings Charles,

You/I have written about the frequency of such issues - cannot be good - yet (many) here see no evidence of time/effort expenditure to reduce (ideally eliminate) such issue.     (its occurrence here is (almost) daily!)

As always - in the attempt to be constructive - may I direct your attention to poster's (recent) report, "the ICDI firmware update message popping up is "FAILED TO CONNECT TO THE DEVICE."      (I've added the highlight)

My concern - was it (really) the objective of poster to, "Update ICDI firmware?"      I think not - doubt we've reached that stage (yet).      Thus - why did that "ICDI Update" message appear - and should not such critical an operation be,  "better guard-banded or (even) restricted" - to prevent the horrors of ICDI corruption?      

Now firm/I have not used "ICDI" for many years - yet should the "Unlock Device" procedure - upon completion - default to or pass "too easily" to, "Update ICDI Firmware?"      That appears certain to "cause issues" - should it prove the case...       Better restricting the ability to, "Update ICDI firmware"   (i.e. via prompt,  "do you "really" want to update the ICDI's firmware - Caution!) may be warranted...)