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.

CC1310 Launchpad target board issue

Expert 2065 points
Other Parts Discussed in Thread: CC1310

I have two launchpad cc1310. and I have also two prototypes custom made (based on TIDA 00484 we have just added one wire tamper on GPIO) which I try to test with the XDS probe of the launchpad as programmer. I don't success to connect any custom board to SMARTRFSTUDIO . It display "Unknown" constantly.  I have the LED D4 and D5 which are lighting on the the custom board when I plug the IDC cable from XDS 110 Pin out to our JTAG plug J3. I am wondering if the Unkonwn is related to the fact that our custom board still doesn't have any firmware in it and hence wouldbe in ADFU mode  or if the problem comes from something else ?

When launchpad 1 is connected to launchpad2 via XDS pint out on 1 and pin in on launchpad 2,, smartrfstudio recoginzed well the chip from launchpad 2, hence cable issue is excluded.

I have attempted to test voltage on the custom board based on test point. Here are the values I am currently getting: 

TP4 = 0V

TP3 = -0.14V  (I have no battery in the battery slot)

TP7 = 3.3V

TP8 = 3.3V

TP1 = 3.3V

TP2 = 0V

I noticed JTAG TCK is 3.3V and JTAG TMS = 0V, but if I click on refresh in stmart rf studio JTAG TMS will move to 0.7V

NRESET is 0V and doesn't move at all even when I refresh in smart rf studio or even if I press the RESET button on the launchpad with the XDS. I suppose this is not normal right ? It should be at 3.3V ? (This is what I measure on the launchpad board)

In CCS I have tried to test the connection (picture in attachment). 

Here is the answer after I press the test button

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\2015\AppData\Local\Texas Instruments\
    CCS\Code Composer Studio\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 '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.

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 '-260' (0xfffffefc).
The title is 'SC_ERR_XDS110_OPEN'.

The explanation is:
An attempt to connect to the XDS110 failed.
The cause may be one or more of: invalid firmware update, invalid
XDS110 serial number, or faulty USB connection. The firmware and
serial number may be updated using the xdsdfu utility found in
the .../ccs_base/common/uscif/xds110 directory of your
installation. View the ReadMe.txt file there for instructions.

[End: Texas Instruments XDS110 USB Debug Probe_0]

PROJECt_V2.pdf 

When I double click on the smartrfsutdio "Unknown" I get the followig windows which open but it doesn't allow me to click on a target like if radio button is inactive.

I have tried to upload the firmware of the XDS using the tool as mentionned in the error generated by CCS . After the firmware being loaded, I tested again the connection and CCS reply me this : 

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\2015\AppData\Local\Texas Instruments\
    CCS\Code Composer Studio\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 '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 '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).

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 '-242' (0xffffff0e).
The title is 'SC_ERR_ROUTER_ACCESS_SUBPATH'.

The explanation is:
A router subpath could not be accessed.
The board configuration file is probably incorrect.

[End: Texas Instruments XDS110 USB Debug Probe_0]

After this, when I go to SmartRRFtudio it says the Firmware update required. I do the update then it propose me to open control panel, I say yes then it propose me to open a target , and here again the radio button can not be selected.
I come back to the main windows and get a Unknown device again....

I think I have a software issue and a hardware issue. 

Software issue because when I usre the launchpad chip with jumper connected on the board as target, SMARTRFSUTDIO 7 make it no problem but CCS Connection test still generate an errror as below: 

-----[Print the board config pathname(s)]------------------------------------

C:\Users\2015\AppData\Local\Texas Instruments\
    CCS\Code Composer Studio\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 '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.
Updating the XDS110 firmware ... complete.
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).

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 '-242' (0xffffff0e).
The title is 'SC_ERR_ROUTER_ACCESS_SUBPATH'.

The explanation is:
A router subpath could not be accessed.
The board configuration file is probably incorrect.

[End: Texas Instruments XDS110 USB Debug Probe_0]

Hardware issue because when I connect the XDS probe to my custom board it still give Unknown as target in SMARTRFSTUDIO.

  • Hi, yes this is in the PROJECT_V2.pdf which is posted.
  • XDS110c2.datcJTAG is not supported out of the box for SmartRF Studio and SmartRF Flash Programmer 2.

    There's a way to make it work, but that involves manually replacing a file in the installation directory of the programming tool.

    You need to replace the xds110.dat file in C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Flash Programmer 2\config\xds\board_config with the attached file, and it should work. Rename the old file first, and the new file should be called xds110.dat.

  • Thank you. I will try this.

    Another question, when I try to access CC1310 register via launchpad using CCS6, I get a "Error: Unable to read" in the register area

  • How do you try to read the registers?

    Note that on CC1310 most of the registers should be accessed through macros etc to ensure safe read/ write, see the examples in TI-RTOS for more information.
  • Well, I have downloaded an example project from Ti REssources Explorer and try to build and load it in the launchpad trought the XDS110, but when I try to build adn debug, it gives me this error in the console: 

    Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
    Cortex_M3_0: GEL Output: Board Reset Complete.
    Cortex_M3_0: GEL: Encountered a problem loading file: C:\Users\2015\workspace_v6_1_3\ccccc\Debug\ccccc.out Could not open file

    And below it is what it give me when I build it. I checked inside the workspace project folder and it seems the .out file is not generated. I am going to try reinstall XDC tools

  • Form the screenshot it could look like you haven't installed the XDC tools package. Either try reinstalling CCS or do a search on the forum on how to install thre XDC tools, I believe it's been answered a few times.

  • Thank you for your answer. What i am going to do is to unisntall everything, clean the folder and directory, clean the windows register and try to reinstall everything
  • Hello,

    I have made the resinstall completely of CCS. I success to work it out well with the launchpad, however when I try to get my own board to work, it doesn't success to connect. 

    I get the following feedback when Testing Connection: 

    [Start: Texas Instruments XDS110 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\2015\AppData\Local\Texas Instruments\
    CCS\ccs6\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 'Apr 8 2016'.
    The library build time was '02:44:08'.
    The library package version is '6.0.222.0'.
    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).

    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 '-242' (0xffffff0e).
    The title is 'SC_ERR_ROUTER_ACCESS_SUBPATH'.

    The explanation is:
    A router subpath could not be accessed.
    The board configuration file is probably incorrect.

    [End: Texas Instruments XDS110 USB Debug Probe]

    Here is how my settings are in the target configuration file: 

    Can you please indicate a hardware debut method for me to verify physically that hardware is fine already. Once the hardware has been verified we can valdiate it and work on the hardware issue.

  • I have replaced the file too and still Smart Rf Studio find the target as unknown

  • Yes, we received support from someone having looked at our board and bringing a CC1310 SmartRF06 Evaluation board which use XDS 100 V3 on it.

    First it has been spoted some issue with ESD on JTAG port. For recall our design is based on TIDA 00484. By removing one of the ESD, then our custom board was finally detected by the SMARTRF06 as being CC1310 chip.  So we have solved one problem. 

    However please note, we have also tested the same custom board with the XDS 110 of our own CC1310 launchpad and then we got the unknown again. So, the XDS 110 from launchpad was unable to detect properly an IC which is detected properly by SmartRF06. Why ?

  • The XDS100V3 have had support for cJTAG for some time but for the Launchpads you need the "fix" I described. We tested the fix by removing two jumpers on the LP and we could still program a target. This indicate that you haven't succeeded to do the fix correctly.
  • Hello, 

    Can you please indicate the jumper configuration you are using for this ? 

  • When we tested we removed TDO/ TDI if I remember correctly.