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.

Connection error SC_ERR_ROUTER_SECURE_SUBPATH with JTAG CC1310

Other Parts Discussed in Thread: CC1310

Can't connect to my hardware anymore:

IcePick_C: Error connecting to the target: (Error -241 @ 0x0) A router subpath could not be accessed. A security error has probably occurred. (Emulation package 6.0.228.0)

Test Connection shows:

[Start: Texas Instruments XDS2xx 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\ARMINI~1\AppData\Local\TEXASI~1\
    CCS\ti\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Apr 28 2016'.
The library build time was '02:18:13'.
The library package version is '6.0.228.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 '13' (0x0000000d).
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]-----------------------------

This emulator does not create a reset log-file.

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 '-241' (0xffffff0f).
The title is 'SC_ERR_ROUTER_SECURE_SUBPATH'.

The explanation is:
A router subpath could not be accessed.
A security error has probably occurred.

[End: Texas Instruments XDS2xx USB Debug Probe_0]

Before this happend, I cleared and programmed the internal flash within my application.

Is it possible to destroy the CC1310 that way?

Regards

Armin

  • Armin,

    Sorry for the delay; are you still having this issue? This is a very uncommon error that seems to be tied to the hardware and yes, depending on the firmware loaded the device may appear to be bricked due to constant resets, etc.

    In these cases you may be able to still see if your device is still alive by following the short procedure shown in section 3 of the page below:
    processors.wiki.ti.com/.../GSG:Connecting_to_slave_cores_in_SoC_devices_v5

    In case you are able to verify the core is still alive but being constantly reset, you may try to recover this core by selecting the Cortex_M3_0 core in the Debug view and issuing a MassErase from the menu Script.

    If you are unable to follow the procedure above, perhaps the device is not working anymore. In this case, I would try to ask a question in the device forum as the experts there would be able to better assist you with HW tips.

    Hope this helps,
    Rafael
  • Hi Rafael,

    thanks for the reply. I tried it, but I can't connect to the device:

    IcePick_C: Error connecting to the target: (Error -241 @ 0x0) A router subpath could not be accessed. A security error has probably occurred. (Emulation package 6.0.228.0) 
    MassErase() cannot be evaluated.
    Connect failed
    	at GEL_Connect() [connect_util.gel:41]
    	at ConnectIfDisconnected()
    	at GEL_EvalOnTarget("<parent>", "ConnectIfDisconnected()", 1)
    	at GEL_EvalOnTarget("<parent>", "GEL_EvalOnTarget("<parent>","ConnectIfDisconnected()", 1)", 1) [cc13xx_xds.gel:70]
    	at MassErase()

    Regards
    Armin

  • And the decive is still working with the old firmware.
    Any other idea?
  • Armin,

    I am afraid I have not many other ideas, short of checking the device forum.

    If the hardware is still working, I suspect that somehow the JTAG was disabled. I found the thread below where it is reported the CC1310 is showing a similar behaviour as your setup after writing to a CCFG register area.
    e2e.ti.com/.../519860

    Also, the other thread below discusses the impact of writing to this CCFG area:
    e2e.ti.com/.../474719

    In this case, perhaps you could try to use the SmartRF Flash programmer utility and see if you can gain access to the device via serial port and have some additional insights on what may be happening.

    www.ti.com/.../flash-programmer

    In this case, I suspect the experts at the device forum will be better equipped to help you in trying to get through to your device.

    Hope this helps,
    Rafael
  • Was this ever resolved?

    I am seeing this issue with a CC1310 Launchpad when attempting to do a code load from CCS Version: 7.1.0.00016 but the Debug Device that is selected is the XDS110 USB Probe. I am using the TI-RTOS 'display' project from the SimpleLink CC1310 SDK which builds fine but I am unable to load the code from CCS.

    This was seen after being prompted to update the firmware on the CC1310 from CCS.

    However, I can load the same .out. file from Flash Programmer 2 and view the device from Smartrf Studio 7 so I know the board is not bricked.


    This is the error that I see:

    "Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
    IcePick_C: Error connecting to the target: (Error -241 @ 0x0) A router subpath could not be accessed. A security error has probably occurred. Make sure your device is unlocked. (Emulation package 6.0.579.0)"

    From the Pop up window:
    "Error connecting to the target:
    (Error -260 @ 0x0)
    An attempt to connect to the XDS110 failed.
    The cause may be one or more of: no XDS110 is connected, invalid
    firmware update, invalid XDS110 serial number, or faulty USB
    cable. 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.
    (Emulation package 6.0.579.0)
    "

    Note: JTag is not selected in this case.