(Error -1135 @ 0x0) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.

Hello,
Note that your version of CCS is quite old. Would it be possible to update it to a later version? CCSv6.1.0 is the latest version.

If you have tried updating and still have an issue, please provide which target you are using and which emulator.

Thanks
ki

Hi,

Can you double check the details shown in the page below? Those will help you narrow the issue even further.

processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

Hope this helps,
Rafael

Hello Ki,

I know is old, but is the version the colleagues that I took over from were working on, therefore I know it should work and it worked last week. I need to say that last week I was able to start the debug session and flash the chip.

Target CPU is a 320F280200 and Emulator is XDS100v2 USB Emulator_0/C28xx .

Although I have 20 years development experience, I have not used Code Composer before last week, therefore I think is some misconfiguration as I use the same CCS also for a TI multiplexer. With the multiplexer it seem to work.

Thank you,
Raz

After checking Mr. desouza suggestion I installed the Debug JTAG GUI and for an integrity test I had the following outcome:

-----[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 14 2011'.
The library build time was '22:23:33'.
The library package version is '5.0.429.0'.
The library component version is '35.34.29.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).

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver.

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

Razvan Radulescu said:

The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.

This error is usually a very serious error, sometimes indicating a HW failure of the JTAG scan chain. You can try hooking up a scope to the pins and see where the breaks may be.

Do you have another emulator or target to try?

Hello Ki,

With the same Spectrum Digital XDS100v2 JTAG I am able to connect to a different board, using a different cable. In this case I assume the cable for this configuration is faulty, do you agree ?

Thank you,

Raz