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.

CC2652R: Device is Locked

Part Number: CC2652R
Other Parts Discussed in Thread: LAUNCHXL-CC26X2R1, , UNIFLASH

Hi,

When I was working on my CC26X2R1 Launchpad, the board reported "security error" with "make sure device is unlocked". I searched the forum, and tried to use Flash Programmer 2 to perform "Mass Erase" to unlock it following link https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/918427/ccs-cc2652r-error-code--241-a-router-subpath-could-not-be-accessed-a-security-error-has-probably-occurred-make-sure-your-device-is-unlocked, but the device couldn't be recovered although it shows Mass Erase succeeded:

And I tried to use CCS to debug on board after mass erase, it shows different error now:

"Error initializing emulator:
(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 XDS110SupportReadMe.pdf
file there for instructions.
(Emulation package 9.5.0.00143)"

I also tried to perform "Test Connection" from "Target Configuration" Review, it reports below logs:

[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\xiaofeng.lei\AppData\Local\TEXASI~1\
CCS\ccs1100\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 'Oct 8 2021'.
The library build time was '13:26:36'.
The library package version is '9.5.0.00143'.
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 '-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.
Make sure your device is unlocked.

[End: Texas Instruments XDS110 USB Debug Probe]

Is there any other way to save my board?

Any help will be appreciated!

Thanks,

Xiaofeng

  • Hi Xiaofeng,

    These errors are typically due to an unstable XDS110 debugger connection.  Are you programming the CC2652R device on the LAUNCHXL-CC26X2R1 board or using the LaunchPad's XDS110 to program a separate PCB?  Are you using the USB cable which came with the EVM?  Do you have multiple LaunchPads to test with?

    Regards,
    Ryan

  • Hi Ryan,

    Thanks for your reply!.

    Yes, I'm working on the LAUNCHXL-CC26X2R1 board now, and have been already working on this board for 2 months, the XDS110 is directly with USB cable. When this issue happened, there was only on Board connected. I also tested another board with same USB cable, it's working fine.

    Best,

    Xiaofeng

  • Thanks for the update.  The XDS110 debugger appears to be unresponsive, perhaps you could find more from the User Guide or Documents page.  Is the LED indicator green on the XDS110 side of the board when plugged in?  Are there any noticeable differences between the LaunchPads being tested (jumpers, hardware version, etc)?  Could the board have been exposed to ESD or excessive voltages?

    Regards,
    Ryan

  • The LED is always showing green, and 3.3V voltage is connected as external power supply. It was working fine before the issue occurred. I also tried to restore the default jumper connections with USB only, but no lucks. Looks like something is wrong on the board.

  • Have you tried programming with Uniflash or Flash Programmer 2, or reducing the JTAG clock speed in CCS from the target configuration file?

    Regards,
    Ryan

  • Hi Ryan,

    Yes, I tried both UniFlash and Flash Programmer 2, none of them is working.

    I also tried the different Clock from 100K to 5M for JTAG, no lucks for me.

    Thanks,

    Xiaofeng

  • Here is the output of "Test Connection" of target Configuration 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 '-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.
    Make sure your device is unlocked.

    [End: Texas Instruments XDS110 USB Debug Probe]

  • The tests show that the XDS110 appears to be inaccessible.  You can attempt to contact TI Customer Support for a replacement, be sure to provide this E2E thread and your invoice/order number in the request.  It is still possible to program the on-board CC2652R1 using an external debugger connection.

    Regards,
    Ryan