• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 3865 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/TM4C1294NCPDT: Can't connect to my device in code composer studio or update the device drivers in Windows 10

kayla kloster
Prodigy 30 points
Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL

Tool/software: Code Composer Studio

I am trying to program my TM4C Microcontroller, however when I try to connect to my device and use the debugger in Code Composer Studio, I get the error, "Error connecting to the target:
Unable to communicate with the device. Please check your connection." I have also tried to program using the LM Flash Programmer, but it says it's unable to find the target. I have a Windows Computer and have tried updating the drivers to the Stellaris ICDI Drivers, but whenever I try to update the drivers it says that "The best drivers for your device are already installed". I've tried changing the permissions on my computer as well as disabling any anti-malware settings, but still am not able to connect to my board. I am not sure what the issue might be? 

  • 0
    Expert 2735 points
    respected sir/madam,
    Can you check jumpers on yours EK-TM4C1294XL launch pad kit?? JP1 should be in ICDI position and remaining should be in horizontal position.
    regards,
    digvijay
  • 0
    TI__Guru 72500 points

    Hello Kayla,

    Welcome to this forum.

    In addition to  Digvijay's suggestions I add some other things to check.

    (1) In the picture below I drew a blue arrow pointing to the jumper Digvijay suggested that you check.

    (2) Verify that this LED is on indicating that the board is getting power.

    (3) Verify that you are plugging the USB cable into the Debug port indicated by arrow (3)

    (4) If all three conditions above are met, check your computer's device manager to see if "Stellaris In-Circuit Debug Interface" is listed.

  • 0 in reply to Bob Crosby
    Prodigy 30 points

    Hello Bob, 

    Thanks for the help and information! I believe I have the jumpers in the correct location, and the LED on my board is indeed lighting up, indicating my board is getting power. However, in the device manager panel, my TIVA board is listed as an unrecognized device, as you can see in the snapshot below. 

  • 0 in reply to kayla kloster
    Expert 2735 points

    Respected sir/madam,

                          The driver installation instruction are given in .  

    I have attached snap of device manager after successful driver installation. And i think your board should be connected to the PC while driver installation.

    Regards,

    digvijay

  • 0
    Guru 117855 points

    Feel your pain (such IS a very "helpless" feeling).         Arrives now - 5 "new" suggestions/questions:

    • might you try a fresh install of the Stellaris ICDI Drivers - but w/in (another) computer.     (this to eliminate a "particular computer" issue - known to (sometimes) occur.
    • silent is the earlier use of this board.    Had it (ever) worked?       If so - might improper handling (ESD) - and/or errant program (one which modified the JTAG pins or System Clock) have occurred?
    • as always - "test & re-test" of,  "One MCU board only" proves highly limiting - not too insightful.     If  "at school" - or "on the job" cannot you borrow (or steal) [kidding] a 2nd board - and test that?    Such reveals if the issue resides w/in your PC - or your board - and is "difficult to reveal" via the earlier methods - other helpers advanced.
    • change to a "known good" USB cable - multiple reports here indicate that, "Power may pass - yet "signal" is distorted or AWOL - due to an inferior cable
    • carefully inspect the surface mount USB connector.    "Thru-hole" connectors prove far more robust - through repeated use - the "signal connection" may have been distressed.

    BTW - excellent description of your issue - know that you are, "Far (very far) from alone in suffering this  misfortune!"     Bon chance...

  • 0 in reply to cb1_mobile
    Prodigy 30 points

    Thanks so much for your response! I ended up figure out the issue and it was my USB Cable! I switched the USB Cable for a spare one that I had and everything works fine now. 

  • 0 in reply to kayla kloster
    Guru 117855 points

    Good that - glad that you persisted & succeeded!    It's to be noted that there exist wide variance in USB cable quality & longevity.     Most always the "power connections survive" - not so much - the (distorted or lost) signal.

    You've verified your post - yet was not mine - the (only) one which  "Identified your issue" - thus led directly  to your success?     A second  "Verify" seems appropriate - does it not?

    One last point - I'd suggest that you MINIMIZE any/all  USB cable insertions - w/in your MCU board!       As earlier noted - surface mount USB connectors are  "Not famed" for robustness.      (thus - best to "Yank the cable from the PC" - leave it (safe) & attached to your MCU board!       I'd cut the faulted USB cable in half - to prevent others from,  "suffering your earlier fate"...      (and by "cutting in half" - it proves possible to determine "which end" went (or was) bad - and to "re-purpose" the good end - for (future) signal probing/observation...)