• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 29 subscribers
  • Views 2345 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

tm4c123gh6pm: TM4C123: Could Not Find An Cortex-M Device in the JTAG chain!

Binghui Xiu
Prodigy 40 points
Part Number: TM4C123GH6PM

I am using Keil uVision, my device is tm4c123gh6pm.

Everything works fine unless it indicates that "Could not find an Cortex-M device in the JTAG chain!".

I checked the forum to solve it, it seems my trouble is worse than that.

That I don't have any attached devices at all!

I tried to install it and it seems that installation is ok but it just doesn't work!

From device manager, I didn't find the device either.

How may I bring it back to work please?

Thanks!

  • 0
    Guru 117850 points

    Might you have (mistakenly & unwantedly) impacted the MCU (serving as "ICDI") on your (assumed) LPad?    (LPad's MCU - matches one you note)

    The absence of the "two" Stellaris notations w/in Device Manager appears (as you've noted) to be your issue.    If true - would not your Forum Search (box atop the forum page) keyword, "Recovery of ICDI" (or similar) prove your best bet?     (Firm/I avoid this misfortune by employing J-Link - proven superior to vendor's ICDI)

    It would pay you greatly - as well - to (really) "try to recall" what actions you performed - just prior to this misfortune.    (i.e. He who does not study history - is "condemned to repeat it!")    Such would be very much unwelcome - and quite possibly - avoided...

  • 0 in reply to cb1_mobile
    Prodigy 40 points

    cb1_mobile said:

    Might you have (mistakenly & unwantedly) impacted the MCU (serving as "ICDI") on your (assumed) LPad?    (LPad's MCU - matches one you note)

    The absence of the "two" Stellaris notations w/in Device Manager appears (as you've noted) to be your issue.    If true - would not your Forum Search (box atop the forum page) keyword, "Recovery of ICDI" (or similar) prove your best bet?     (Firm/I avoid this misfortune by employing J-Link - proven superior to vendor's ICDI)

    It would pay you greatly - as well - to (really) "try to recall" what actions you performed - just prior to this misfortune.    (i.e. He who does not study history - is "condemned to repeat it!")    Such would be very much unwelcome - and quite possibly - avoided...

    Thank you for advice. I tried my best to recall what I've done before it happened. I just cannot remember what I did. It seems I just finished my assignment and my instructor checked it and then I start a new one to find everything is changed! I re-open my previous project, the ICDI could not be found either. But I would follow your advice to search "Recovery of ICDI" to try my lucky. Thanks once again!

  • 0 in reply to Binghui Xiu
    Guru 117850 points

    You may be able to "Aid your recall" by carefully reviewing your "most recent" programs - especially those "loaded upon your board."

    It is quite possible to cause JTAG Lock-Out issues by: a) Re-purposing the JTAG signal lines and/or b) improperly configuring the system clock.

    Yet - with that said - you appear to have (somehow) suffered some disruption to the MCU serving as "ICDI" - and it is that, "ICDI MCU's operation" - which is revealed w/in the Control Panel's, "Device Settings." And - unfortunately for you - now is absent.

    Vendor agents are most qualified for such "Rescue Operations" - they (surely) encounter such issues far more often than we "outsiders."    Still - do continue your search efforts - just in case vendor arrival is delayed...   (note that it is the "weekend" - most often only "small/truly dedicated" firms work then..."

    Know that (many) here "Feel your pain" - and hope that vendor agents may guide your board to, "FULL & Quick Recovery."

  • 0 in reply to cb1_mobile
    Prodigy 40 points
    But if it is locked, how to unlock it? There is no connection, the application cannot find a communicate way to unlock it.
  • 0 in reply to Binghui Xiu
    Guru 117850 points

    There is a difference between, "Malfunction of the ICDI" versus "Target Board" Lock-Out.

    You've not told us the result of your "Forum Search" - seeking, "Restoral of the ICDI MCU's performance."   Should "ICDI problems be your issue - unless you employ another means of "interacting w/your MCU Target" - your attempt at ICDI Restoral (as stated) should continue.

    Another LPad - or a more proper "Pro JTAG Probe" - may enable your use of your Target MCU - by bypassing the (likely) disrupted ICDI MCU.     Again - Forum Search - (still) awaits your arrival - ready to supply much needed detail...   

    You've mentioned your "instructor's" viewing/handling your board - is he/she not available to "instruct you" - in this (likely) "Restoral of ICDI" regard?