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.

have errors when using XDS100V3 to debug CC1310F128

Other Parts Discussed in Thread: CC1310

In this link, http://www.ti.com/tool/cc13xx-sw, 

Code Composer Studio (CCS)

  1. Download and install TI-RTOS SimpleLink bundle from the link above.
  2. Download and install CCS here.
  3. Once you open CCS, click on “Browse Examples”. This will open up the Resource Explorer, from where you can import example projects directly into your CCS workspace.
  4. Select one of the examples, e.g. RF Packet TX, and click the "Import" button.
  5. Build the project; the first time it will take some time, due to the TI-RTOS kernel is also built.
  6. Connect your CC1310DK to your PC and download to your CC130DK via the Debug button.
  7. Start the program by clicking "Run".
  8. The RF Packet TX example will transmit packets every 100ms, indicated by LED3 blinking.
  9. Follow the same procedure to import the RF Packet RX example in order to receive the packets. You can also use SmartRF Studio to capture packets.

When I carry out step 6, I can successfully compile the code but when I try to debug it, I have the following errors:

IcePick_C: Error connecting to the target: (Error -620 @ 0x0) An attempt to read register values from the DTS have failed badly. (Emulation package 6.0.14.5) 

The following facts have to be told for better solving my problem.

(1)The CC1310 board is designed by myself. 

(2)I use XDS100V3 for debug CC1310F128

(3)The CCS version is Version: 6.1.2.00015 

(4) I use 5 pins for connection between CC1310 and XDS100V3. That is, TMS,TCK,TRST,VCC,GND

(5) The screenshots of target configuration are put below

(6) When I click the button "Test Connection", I got the following results,

[Start: Texas Instruments XDS100v3 USB Debug Probe]

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\way\AppData\Local\TEXASI~1\CCS\
ti\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 'jioserdesusbv3.dll'.
The library build date was 'Sep 4 2015'.
The library build time was '21:59:23'.
The library package version is '6.0.14.5'.
The library component version is '35.35.0.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).

An error occurred while hard opening the controller.

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

This error is generated by TI's USCIF driver or utilities.

The value is '-154' (0xffffff66).
The title is 'SC_ERR_FTDI_WRITE'.

The explanation is:
One of the FTDI driver functions used to
write data returned bad status or an error.

[End: Texas Instruments XDS100v3 USB Debug Probe]

How to solve my probem? Thank you.

  • Hello,

    Yunlong Wang85 said:

    (1)The CC1310 board is designed by myself. 

    (2)I use XDS100V3 for debug CC1310F128

    (3)The CCS version is Version: 6.1.2.00015 

    (4) I use 5 pins for connection between CC1310 and XDS100V3. That is, TMS,TCK,TRST,VCC,GND

    A common cause of the -154 error is some error in the JTAG connection (some signals not properly connected). This is more common with custom boards so carefully check the integrity of all the signals.

    Are you using an external XDS100v3 debug probe with your custom CC1310 board?


    Thanks

    ki

  • Hi, I found that the reason of my problem is that the input the wrong voltage into CC1310, that is, I input 4.3v to CC1310. After using 3.3v, everything works well.