New problem :The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.

Hi,

You must have forgotten to tick on spectrum digital drivers while installing CCS. Please install it again and tick on SD drivers while on Tool Support window.

Regards,
Gautam

Hi, I reinstall ccs. I could find the XDS100v2 USB Emulator option. Thanks.

But I met a new problem, in step 4 "Debug the imported project", the error message is
C28xx: Error connecting to the target: (Error -600 @ 0x0) A required dynamic library could not be located. The library isn't on the search path. (Emulation package 5.1.232.0) .

Because it is the first time when I connected it with my computer. I think it may be the windows can not detect the hardware and install the drives. When I connected it with my computer, the computer did not respond to the hardware and I just saw leds flashing.

Could you help me? Thanks.

Check the device manager for the debugger part under USB connections. Let me know whether it displays or not.

Just for the sake that there's no confusion, this is what I wanted you to check:

Check with the troubleshooting steps and let us know whether that helps you or not.

Regards,

Gautam

Hi Gautam,

Sorry for a late reply. I changed a computer and the XDS100 worked. But I still can not connect my launchpad. This is the new error message:

C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 5.1.641.0)

Sorry for so many problems.

Thanks again

This is my LP and I am not sure whether it is correctly set. Thanks.

I think I chose the wrong connection in ccsv6. I still can not find XDS100v2 USB Emulator option in ccsv6. But I can find this option in ccsv5. It seemed that I did not see Emulator install option when I install ccsv6.

But even I select XDS100v2 USB Emulator  in ccsv5. It also can not be  connected.

This is the test result.

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\kou\AppData\Local\.TI\693494126\
0\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 'Aug 20 2013'.
The library build time was '22:56:19'.
The library package version is '5.1.232.0'.
The library component version is '35.34.40.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 512 32-bit words.

The test for the JTAG IR instruction path-length failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

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

This test will use blocks of 512 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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG IR Integrity scan-test has failed.

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

This test will use blocks of 512 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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.

The JTAG DR Integrity scan-test has failed.

[End]

Hi Gautam,

You can see when I try to install ccsv6. It only has option to select debug probes but it has no options to select emulators. So my ccsv6 has no emulators options but ccsv5 has.

Thanks

XDS100v2 debugger comes under Spectrum Digital Debug Probes and Parts. Simply click on it and install the same.

Hi Gautam,

I can find the XDS100v2 debugger but the F28027 board needs XDS100v2 USB Emulator, am I right?

Thanks for your reply

Hi Gautam,

I reinstall the CCS and I select Spectrum Digital Debug Probes and Parts. 

The picture is the connections I have. Could you give me any suggestion?

Thanks

Hello, 

I was curious how this was solved. I am also having the same code error. 

"The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation."

I have a TMS320F28035PN.

Thank you.

Hello Luis,

This thread seems to have gone stale. Please create a new thread explaining your issue so you have a better chance of it being answered in a timely fashion.

Best Regards,
Adam Dunhoft