• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 4632 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: XDS100v2 emulator not found on system

Chris Lightcap
Expert 1800 points


Tool/software: Code Composer Studio

I'm using an XDS100v2 emulator for debugging my Piccolo C2000 microcontroller. I've used it successfully in the past, but recently I've had trouble recognizing the emulator. Today I haven't been able to connect to it at all. I've tried other USB cables but have not had any success. My colleague tested the same board on his machine and it worked without problems. I'm concerned that I have some USB FTDI XDS100 driver problem.

I can see the XDS100 device in Device Manager and Texas Instruments Debug Probe, but I'm not able to discover the device using xds100serial.exe program in common/uscif. The xds100serial.exe program hangs and then perhaps a minute later returns the output:

C:\ti\ccsv7\ccs_base\common\uscif>xds100serial.exe
Scanning for XDS100 emulators...

No XDS100 emulators were found on the system.

The FAQ page shows that I should see TI devices listed under USB devices in my Device Manager (see image), but I don't see any on my system.

I've tried reinstalling Code Composer v7 but have not had any success. Please let me know if you have any suggestions to try.

Best regards,

Chris

  • 0
    Expert 1800 points
    I have another update. I switched USB cables and I can detect the XDS100 device using xds100serial.exe but I cannot run the debugger. Here's the output from 'Test Connection'

    [Start: Texas Instruments XDS100v2 USB Debug Probe_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\CLIGHT~1\AppData\Local\TEXASI~1\
    CCS\ti\3\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioserdesusb.dll'.
    The library build date was 'Dec 11 2017'.
    The library build time was '12:04:14'.
    The library package version is '7.0.100.1'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the FTDI FT2232 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for FTDI FT2232 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[The log-file for the JTAG TCLK output generated from the PLL]----------

    There is no hardware for programming the JTAG TCLK frequency.

    -----[Measure the source and frequency of the final JTAG TCLKR input]--------

    There is no hardware for measuring the JTAG TCLK frequency.

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 64 32-bit words.

    The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 38 bits.

    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Integrity scan-test has succeeded.

    [End: Texas Instruments XDS100v2 USB Debug Probe_0]

    Here's the output from xds100serial.exe

    [Start: Texas Instruments XDS100v2 USB Debug Probe_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\CLIGHT~1\AppData\Local\TEXASI~1\
    CCS\ti\3\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioserdesusb.dll'.
    The library build date was 'Dec 11 2017'.
    The library build time was '12:04:14'.
    The library package version is '7.0.100.1'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the FTDI FT2232 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for FTDI FT2232 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[The log-file for the JTAG TCLK output generated from the PLL]----------

    There is no hardware for programming the JTAG TCLK frequency.

    -----[Measure the source and frequency of the final JTAG TCLKR input]--------

    There is no hardware for measuring the JTAG TCLK frequency.

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 64 32-bit words.

    The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 38 bits.

    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Integrity scan-test has succeeded.

    [End: Texas Instruments XDS100v2 USB Debug Probe_0]

    Here's the output from xds100serial.exe:

    C:\ti\ccsv7\ccs_base\common\uscif>xds100serial.exe
    Scanning for XDS100 emulators...

    VID/PID Type Serial # Description
    0403/a6d0 XDS100v1/v2 TIXTLZPV Texas Instruments Inc.XDS100 Ver 2.0

    Here's the error from Code Composer:

    C28xx: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may be one or more of: no XDS100 is plugged in, invalid XDS100 serial number, blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the XDS100 can be located. (Emulation package 7.0.100.1)
  • 0 in reply to Chris Lightcap
    TI__Guru**** 473751 points

    Hello,

    Based on the results of your scan test, the low level JTAG connectivity looks good.

    Chris Lightcap said:
    VID/PID Type Serial # Description
    0403/a6d0 XDS100v1/v2 TIXTLZPV Texas Instruments Inc.XDS100 Ver 2.0

    The VID/PID values look good. Hence I would guess that the EEPROM was programmed correctly.

    Not sure what the root cause of your issue is. I suppsoe you could try reprogramming the EEPROM to see if that helps.

    What exact CCSv7 version are you using? And are you using an external XDS100v2 probe with a custom piccolo target? If so, what is the vendor of the probe? And what exact target are you using?

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1800 points

    Hi Ki,

    Thanks for the quick reply. I'm using an FTDI 2232H chipset and the latest code composer release (v7.4.0). I set up another machine with Code Composer and my project and I was able to immediately connect and debug without any errors. The primary difference between the two machines is that one uses Windows 7 while the other using Windows 10. Are there any known compatibility issues with XDS100 and Windows 7?

    Thanks,

    Chris

  • 0 in reply to Chris Lightcap
    TI__Guru**** 473751 points
    No, there are no known issues regarding Windows 7, it should work fine.

    It could be an issue with a corrupted installation. If it is not too much trouble, can you uninstall the existing install and then reinstall CCS 7.4? Make sure that when you reinstall, you can installing in an empty clean folder

    Thanks
    ki
  • 0 in reply to Ki
    TI__Guru**** 473751 points
    Hello,
    I haven’t heard back from you, I’m assuming you were able to resolve your issue. If not, please post a reply with an update below (or create a new thread).

    thanks,
    ki
  • 0 in reply to Ki
    Expert 1800 points

    Hi Ki,

    No, this hasn't resolved the problem on my Windows 7 machine. I tried re-installing Code Composer 7.1 but the same issue arises. I've since switched to using my Windows 10 machine. I suspect it is some type of driver issue but I can't seem to clear up the issue by re-installing Code Composer. Let me know if you have any other ideas.

    Thanks,

    Chris