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.

CCS4 Error connecting to target with custom board (Error 0x80001240/-1052)

Other Parts Discussed in Thread: TMS320VC5407

Hello everyone

I face a few problems programming a custom board with a tms320c5407 dsp. I get the following message, when I try to program/connect to the target using CCS 4:

Error connecting to the target: Error 0x80001240/-1052 Fatal Error during: Initialization, OCS, Target,  Device driver: Emulator Controller not responding The targets should be power cycled or hard reset followed by an emureset and reconnect to each target. Then it is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.

I also ran the dbgjtag/xdsprobe tests to verify the jtag connection, the results were all successful as you can see on the following output:

C:\Users\silas\ccsv4\common\uscif>dbgjtag -rv -f "C:\Users\silas\ccsv4\DebugServ
er\bin\win32\BrdDat\ccBoard0.dat" -S pathlength

-----[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 'Jun 30 2010'.
The library build time was '22:08:44'.
The library package version is '5.0.104.0'.
The library component version is '35.34.24.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 now 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).

-----[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 succeeded.
The JTAG IR instruction path-length is 8 bits.

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


C:\Users\silas\ccsv4\common\uscif>xdsprobe -r -f 0 -g 10 -c 4

-----[Perform the Given Data scan-test on the JTAG IR]-----------------------

This test will use blocks of 512 32-bit words.
This test will be applied 4 times.
It uses the first 4 of the 10 different test-cases.

Do a test using 0x0000000A.
Scan tests: 4, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Given Data scan-test has succeeded.

-----[Perform the Given Data scan-test on the JTAG DR]-----------------------

This test will use blocks of 512 32-bit words.
This test will be applied 4 times.
It uses the first 4 of the 10 different test-cases.

Do a test using 0x0000000A.
Scan tests: 4, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Given Data scan-test has succeeded.


The target is a custom board, on which the dsp is directly connected to the jtag connector (TDI, TDO, EMU1, EMU0 ....), and there is neither external memory nor another processor.
The emulator used is an XDS100v2.

The target configuration is the following:

Other information about the system:

Version of OS: Windows 7 64-bit
CCS version 4.1.3.00034
Target: DSP TMS320VC5407
Emulator: XDS100v2
Board: custom board

(voltage levels etc. on the board have been checked and are ok).

The error message of CCS is not very helpful and I don't know anymore what to do because the jtag connection seems to work. Can someone please help me with this.


Thanks in advance!

  • Hi,

    Unfortunately the error messages changed over the years and therefore it is difficult to get many references about this specific error code. In any case, I found a forum thread below that talks about a very similar scenario that was originated from a hardware/initialization error:
    e2e.ti.com/.../114638

    The apparent disconnect between CCS and the dbgjtag messages is that dbgjtag only tests the sanity of the JTAG scan chain, which is independent on the status of the processor core itself - any problems with the core's clock and power subsystems will not be caught by the dbgjtag but will be critical for a proper connection via CCS.

    Given you already checked voltage levels, I would then check clocks to your device (which is also suggested by the forum thread above).

    I will try to find other possible root causes and report back if I find anything.

    Hope this helps,
    Rafael