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/TMDXIDDK377D: TMDXIDDK377D

Part Number: TMDXIDDK377D

Tool/software: Code Composer Studio

Error connecting to the target

When I am trying to connect to C2000 Delfino controlCARD TMDXCNCD28377D I got the follow error:

"IcePick_C_0: Error connecting to the target: (Error -1265 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 8.0.27.9)" 

CCS Version: 8.1.0.00011

Connection: XDS100v2 USB Debug Probe

Board or device: TMS320F28377D

Test connection results attached in txt file.

Any idea what could be the problem?

Regards,

test_connection.txt
[Start: Texas Instruments XDS100v2 USB Emulator_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\EVGENI~1.BOR\AppData\Local\TEXASI~1\
    CCS\ti\2\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 'May 30 2018'.
The library build time was '23:03:35'.
The library package version is '8.0.27.9'.
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 6 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 Emulator_0]

  • Yevgeny,
    Thanks for sending the test logs, those look good, meaning that CCS has detected and connected to the XDS100v2 correctly. On newer devices like the TMS320F28377D there is additional check that the MCU part number matches the PN used in your target config file. This is done so that the built in flash tools know the number of cores/flash size/etc. In your target config CCXML can you confirm that you have selected the F28377D as the target? Note that on later control cards(TMS) we have switched to the F28379D for the MCU, so if you are switching back and forth between control card revs, you will need a different CCXML.

    Matt
  • Hi Matt,

    Thank you for the answer. I checked the CCXML file, I see that F28377D selected as the target. Are there any other ideas?

    Thanks

  • Yevgeny,
    This control card has high power isolation, and as such requires both the emulator to be powered as well as the card itself.

    I don't expect this error message for this issue; but want to make sure; are you also plugged into the docking station and have it powered(either with another USB or 5V barrel connector)?

    If this doesn't work can you force CCS to perform an update through "Help->Check For Updates".

    Let me know what you see and we can go from there.

    Matthew