• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 1856 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/CC1310: The XDS110 stopped working with CCS

Igor Evdokimov
Intellectual 775 points
Part Number: CC1310


Tool/software: Code Composer Studio

The TI Emulators module was updating and stopped working with CCS v.9.0.1.00004

In debug mode, began to issue a message:

Verify connection result:

[Start]

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\
ccs901\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 'jioxds110.dll'.
The library build date was 'Jun 3 2019'.
The library build time was '15:24:38'.
The library package version is '8.2.0.00004'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
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 XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 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 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]

Before this, the formware was updated:

Cortex_M3_0: GEL Output: Memory Map Initialization Complete.

Cortex_M3_0: Warning: A firmware update is required for the debug probe. Click the "Update" button to update the firmware and connect to the debug target. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 8.2.0.00004)


IcePick_C: Warning: A firmware update is required for the debug probe. Click the "Update" button to update the firmware and connect to the debug target. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 8.2.0.00004)


IcePick_C: Warning: The firmware update completed successfully. (Emulation package 8.2.0.00004) 
Cortex_M3_0: Warning: The firmware update completed successfully. (Emulation package 8.2.0.00004)


CS_DAP_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.2.0.00004)

PS: The SCS works correctly with my XDS110 and if I connect my custome board through CC1310 LaunchPad(XDS110debugger), then my board is correctly programmed and debugging starts. The problem only appears with the original debugger XDS110 DEBUG PROBE.
  • 0
    Intellectual 775 points

    I tried to completely remove the CCS v.9.0.1.00004, and reinstall the new version of the CCS Version: 9.1.0.00010.

    The result is the same - XDS110 DEBUG PROBE it does not work.

    But using CC1310 LaunchPad debugging works.
    Tell me what could be the problem and how to solve it?

  • 0 in reply to Igor Evdokimov
    TI__Guru**** 171309 points

    Hi,

    Taking into consideration this worked before the update, I can think of one important change made to the newest TI Emulators package and XDS110 Debug Probes: the default TCLK speed.

    With this new emupack, some performance improvements enabled higher speeds up to 14MHz and the default was set to 8MHz, which was tested to be compatible with the Launchpads and development kits. However, this may be too high depending on the length of the connections and other physical factors.

    In this case, the first thing I would try is to reduce the TCLK to the previous default of 2.5MHz and see if you can get a stable connection. 

    Details can be seen in the clip below, where I explore various scenarios to test the TCLK.

    https://www.youtube.com/watch?v=mKxaztkCsYw&t=27s 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 775 points
    Thanks for your reply. I will try a later, but for now I have rolled back to the previous version, which works correctly for me.