Tool/software:
Hello everyone, I've been encountering some issues with the C5502 DSP board. Although I've managed to temporarily resolve them, they reappear after some time. I wonder if there’s a permanent solution to these problems.
-
Error connecting to the target:
- Error -1063: Device ID is not recognized and is not supported by the driver. Confirm that the device and debug probe configurations are correct, or update the device driver (Emulation package 9.12.0.00150).
- Solution:
- Remove the power supply from the DSP board.
- Replug the USB cable connected to the debug probe.
- Reconnect the DSP power supply.
-
Error initializing emulator / error connecting to the target:
- Error -2083 / Error -2172: Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation (Emulation package 9.12.0.00150).
- Solution:
- Remove the DSP power supply.
- After waiting more than 10 seconds, reconnect the power.
Additionally, here is the test connection result log:
[Start: Texas Instruments XDS2xx USB Debug Probe]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\user\AppData\Local\TEXASI~1\CCS\
ccs1240\0\0\BrdDat\testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Jun 2 2023'.
The library build time was '17:37:16'.
The library package version is '9.12.0.00150'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
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]-----------------------------
This emulator does not create a reset log-file.
-----[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 XDS2xx USB Debug Probe]
Thank you in advance for any advice or insights from the experts and seniors here!
