• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 1693 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.

EK-TM4C1294XL: Stellaris in circuit debug interface erratic with windows 10 computer

Priya Nadathur70
Expert 2795 points
Part Number: EK-TM4C1294XL
Other Parts Discussed in Thread: SEGGER

Hi,

I have the drivers installed for the Stellaris debug interface. I am finding that my windows 10 PC

sometimes does not recognize this COM port at all and labels the USB device as unknown.

I have tried uninstalling and re-installing the Stellaris drivers, disabling the windows 10 signature,

restarting the computer, re-setting the USB hub etc. Nothing seems to fix the problem. The JTAG

programmer I was using worked fine with a windows 7 machine. I plugged a different JTAG programmer

into my windows 10 machine. Did not work. Then I plugged the usual JTAG programmer back in and

then the Stellaris VSP shows up in the device manager.

The last time this problem happened, I changed the EK. This seemed to fix it. Something about bringing

in a new EK seems to help. What is it? I need to have the JTAG programmer ALWAYS available. I am losing

a lot of time at work dealing with this problem.

Thanks,

Priya

  • 0
    Expert 2795 points
    I wanted to add, this problem shows up when I am using the USB interface in the application. I don't see it if I use a different interface.
    Is there a release for the tiva drivers with the USB patch built in? If not, what do I apply the USB driver patch to?

    Thanks,
    Priya
  • 0 in reply to Priya Nadathur70
    Guru 117850 points

    Feel your pain - know that "Win10" has proved challenging (when used in conjunction w/Devices/Drivers here) to many.

    It is unclear if you have employed the "Forum Search Box" - located atop this forum page - and  employed, keyword "Windows 10."    Some - yet not all posters - "Have reported success."

    Have you considered the "PRO" JTAG/SWD Probes - specifically those from IAR and Keil?     While more costly - these have "far superior" history  - and as Segger's "J-Link" is available at substantial, "Educational Discount" (even to those - "outside" that description) such seems a "reasonable" alternative.     

    Note too - these "Pro JTAG/SWD Probes" accommodate (most) ALL ARM-based MCUs - from MANY Vendors - thus the incentive to, "Solve such issues as you report" is likely greater.     I must advise that firm/I (still) "Only purchase PCs loaded w/Win7" (Dell is one such "accommodating" vendor) - as several of our legal/financial/engineering programs perform only - or more robustly - under MS's "past regime."

    Note that "No Benefit/Reward" results from firm's/my endorsement.     In multiple, side by side comparisons - we find the "PRO JTAG/SWD Probes" much superior...    

    Note that there exist MANY "illegal copies" of the J-Link - firm/I are, "Unaware of ANY copies" - of the probes offered for sale - here...    Such is "telling" - is it not?

  • 0 in reply to Priya Nadathur70
    TI__Guru*** 128255 points

    Hello Priya,

    There are two sets of drivers you can try and apply. The first set is for the USB examples which use aspects like CDC to enumerate correctly (aside from our Composite example which has an issue in the current TivaWare release), and that can be downloaded from: http://software-dl.ti.com/tiva-c/SW-TM4C/latest/exports/SW-TM4C-2.1.4.178.PATCH-1.0.zip

    The other set of drivers which may be useful for you as well are our ICDI drivers specifically for the ICDI port which enumerates, and those can be downloaded from: http://www.ti.com/tool/stellaris_icdi_drivers

    Please try installing these and see if that resolves your issue. You will have to manually install them in the sense of searching for them yourself rather than letting Windows try to find them.

  • 0 in reply to Ralph Jacobi
    Expert 2795 points
    Ralph,
    I have the current stellaris icidi drivers installed.

    What do I apply the tiva USB driver patch to? Please explain.

    cb1_mobile-- I have a standard 10 pin ARM JTAG connector bought from digikey,
    it is a Samtec part FFSD-05-S-06.00-01-N. I couldn't find a 10 pin - 10 pin adapter
    connector, so one end of the JTAG cable is soldered on a breadboard. Is this part good
    enough?

    Thanks,
    Priya
  • 0 in reply to Priya Nadathur70
    Guru 117850 points

    Greetings,

    Pardon - I'm at a loss, you wrote that you have a "standard 10 pin ARM JTAG connector - yet, "Could not find a 10 pin - 10 pin adapter."    What  then is the intent of such 10 pin to 10 pin adapter - (escapes staff & myself.)

    I have suggested your investigation of the Segger "J-Link" JTAG/SWD Probe - in place of vendor offerings - which appear (beyond somewhat (pardon) "Snakebit" - especially when Win10 is "in play."

    My firm uses a (real) standard, "ARM 20 pin (0.100" pitch) to 10 pin (0.05" pitch) Adapter" - which works very well while saving copious amounts of board space.

    I referred you to the forum's Search Box - as there are (many) instances of, "Client-Users challenged under Win 10" - AND yet there are several  reports of  "Client Success!"     Perhaps such success can flow onto you - but  you must make that effort.

    No such (long standing) Win 10 issue appears to (similarly) plague the Segger "J-Link!"    Earlier here - I listed multiple (other) advantages - such PRO JTAG/SWD Probes provide...   (or - you can "soldier on...")

  • 0 in reply to cb1_mobile
    Expert 2795 points
    cb1--
    The PCB has a different 10 pin connector than a standard ARM JTAG. I had the part number checked
    on the forum before I bought it. The Keil website listed samtec parts too. I will search the windows 10
    on this forum and the segger probes also.

    Thank you,
    Priya
  • 0 in reply to Priya Nadathur70
    Guru 117850 points

    Deviating from ANY Standard - minus "GREAT & GOOD Reason" - may not make ANY Sense!

    Do give the vendor's suggestion "FIRST and SERIOUS Consideration" - should that FAIL - only then would I investigate an (enhanced - yet outside) alternative.  

    Although - vendor's desire to capture  "ALL Biz" - when the basics (JTAG success) remain unmet - surely justifies (other - especially  other succeeding) methods!      (i.e. even fellow sailor "Bob" would agree ... Any Port (even a foreign one) during a STORM!)      (where storm registers as the, "simple INABILITY to manage JTAG...")

  • 0 in reply to Priya Nadathur70
    TI__Guru*** 128255 points

    Hello Priya,

    Priya Nadathur70 said:
    What do I apply the tiva USB driver patch to? Please explain.

    Those are applied to non-ICDI USB ports which show up in device manager, so anything such as Virtual Com Port (i.e. CDC), Bulk device, etc. Another way to look at it is that they would apply to any USB port that enumerates from the TM4C due to application code running on the device.

  • 0 in reply to Ralph Jacobi
    Expert 2795 points
    Currently the problem came back one time today. Since the last time the problem happened, I installed windows updates on my laptop. I am going to check for updates, shut down and start everyday. Looking at the laptop settings, I can't seem to schedule automatic re-starts daily. Following this update, the problem seems to go away if USB ports are changed. I will run the TI example and apply the patch if it happens again. As far as other solutions, nothing is being considered seriously now.

    Thanks,
    Priya