EK-TM4C123GXL: Debugger part of Micro controller getting heated up

thank you very much Jacobi

i tried with CCS also i got error like frequency out of range and the emulator IC is getting heated up so much that i cant able to touch it is their any issue in Hardware 

Several further questions should add necessary detail:   (Note:  this is NOT meant as an "interrogation" - instead attempts to "tease out" key data - not yet  supplied/known...)

• Had your board (ever) worked - however briefly?
• Is your board's power switch - in its proper "DBG" (right-most) position?
• Was that (always) the case?
• Are you routing your USB cable from the PC to the (top) Debug USB connector
• Was that (always) the case?
• Have you made any other connections to your board?   If so - kindly describe
• Carefully measure the board's voltage - with a scope or DMM - connected between "J2-top" and (first) "J1-top" and then "J3-top."
• J1 to J2 should measure 3.3V while J3 to J2 should yield 5V.    Does your board produce these results?
• Have you a different USB Cable - with which to power your board?   If so - kindly connect, observe & report.
• It also proves useful to power your MCU board from a "different" USB Port - ideally from a different PC - as well.
• Does your board's power Led illuminate?   (just below the Debug USB connector)
• Have you a friend - or coworker - who may have a similar board?    If so - might you "test that board - as well?"

These boards are produced in volume - and are proven to be,  "Highly Robust."    (our firm has employed several hundred - and has YET to note (any) failure - that is NOT unusual!)

Your response to these questions should aid (both) - vendor agents - and my "outsider team" - to best aid you in your board's (possible) recovery...

Hi cb1,

Thanks for those questions, I think you've exhausted every initial idea for what Mohammed should test so we can figure out whats going on.

Mohammed,

Please report back your results from the list of questions cb1 provided so we can try and uncover what is occurring.

Had your board (ever) worked - however briefly?
yes it worked fine for about a month

Is your board's power switch - in its proper "DBG" (right-most) position?
yes

Was that (always) the case?
yes

Are you routing your USB cable from the PC to the (top) Debug USB connector
Was that (always) the case?
yes

Have you made any other connections to your board? If so - kindly describe
yes, we connected PF1,PF2,PB3,PC4 to L293DD to drive stepper motor

Carefully measure the board's voltage - with a scope or DMM - connected between "J2-top" and (first) "J1-top" and then "J3-top."
J1 to J2 should measure 3.3V while J3 to J2 should yield 5V. Does your board produce these results
J1 to J2--3.1V J3 to J2---4.6V

Have you a different USB Cable - with which to power your board? If so - kindly connect, observe & report.
No, we used same cable supplied with launch pad

It also proves useful to power your MCU board from a "different" USB Port - ideally from a different PC - as well.
Does your board's power Led illuminate? (just below the Debug USB connector)
yes

Have you a friend - or coworker - who may have a similar board? If so - might you "test that board - as well?"
we have worked on many number of similar boards, but we haven't faced issue but this time we faced issue in more than 10 boards

Hello Mohammed,

I presume each board has it's own USB cable, so you've overall used over 10 cables with the 10 failing boards? I ask because sometimes the USB cable is the root cause and swapping cables is a common recommendation for debug.

It sounds like the power is in good shape, 4.6V is a bit low but I think that is fine still for J3 to J2.

10 boards? That sounds like your application may have damaged the device. We ship hundreds of these, never had issues with 10+ boards failing. Given you are dealing with a motor drive application I feel it may be possible you subjected the LaunchPad to more voltage or current that it could handle.

Was the same application loaded on every failing board? What does the application do? Have you investigated possible ways for the board to have suffered from voltage or current spikes based on your hardware setup with the stepper motor+driver?

Mohammed Hussain said:

Have you a different USB Cable - with which to power your board? If so - kindly connect, observe & report.
No, we used same cable supplied with launch pad

As I was first to note this - it IS advisable to employ a "different" (ideally a KNOWN GOOD) USB cable - to (properly) perform such test.    Such appears NOT to have been done!

Mohammed Hussain said:

Have you made any other connections to your board? If so - kindly describe
yes, we connected PF1,PF2,PB3,PC4 to L293DD to drive stepper motor

This proved a,  "Very KEY QUESTION" - did it not?     Poster's initial writing gave "No clue" as to (any) past "Board Success" and  especially to (any) Board Interconnects!

Attaching & Driving a Motor - even a small "stepper" - may subject the,  "Driving MCU pins to voltage (or current) transients" - causing damage.  This appears the (most likely) cause of poster's Issue.    (now discovered to be,  Multiple Issues!)

Few more questions should (further) assist in poster's Diagnosis:

• Your Stepper Driver IC (L293DD) must have been located on a 2nd board (there's NO room for it - on the LPad).   Kindly confirm
• What was/is the distance of the "cable-run" - connecting the LPad to the (assumed) Stepper board?
• How were you "powering" the L293DD and (any other) ICs - or power requiring devices - upon your (assumed) Stepper board?   (i.e. what was the Source of the Stepper board's power?)
• My questioning revealed that,  "You've worked on MANY NUMBER of (SIMILAR) Boards - w/out ISSUE!     That's significant - is it not?    What's changed?    What's DIFFERENT between these 10+ NEW Boards - which have FAILED - and those "MANY NUMBER" of Past (Similar) Boards - which worked?
• You have noted "ONLY" the Debugger (i.e. "ICDI" MCU) as,  "Getting HOT!"   How did you first,  "Note that?"    Does that mean that the Target (or Main) MCU - does not,  (similarly) "Heat Up?"   (it is assumed an "unburned finger" - serves as the "temperature sensor" - correct if that's, "not the case."
• There has been "NO DESCRIPTION" of how your (assumed) TWO Board Assembly has been operated.     What is the Power Source - for each board - or does just one power source - power the 2 boards - together?     Please describe the powering method - in detail.   (important)
• Have you insured - at all times - that  "Board GND" - between LPad and (assumed) Stepper Board - is "IN Place, Solid & Sufficient?"   (adequately sized wire gauge)
• While (either) "Testing" - or during "Normal Operation" - is there an  "Active connection to the Debug USB Port" - on the LPad.    Is that connection  "Again Made" (ever) - during "NORMAL" (NON - Debug or Programming) operation?     ***  This is rather critical - as (something) UNEXPECTED - appears to be "attacking" your ICDI MCU.    Your "best & detailed answer - will greatly AID - my group's diagnosis!

I believe - again - that  the detail requested will  "Speed, Ease & Enhance" - even  (further),  successful MCU Board (or even Stepper Board) Diagnosis.    Thank you for your time & attention...