CCS/CC1352P: Regarding Unlocking of CC1352P device

Haricharan sarpatwar

Part Number: CC1352P
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hi,

I am working on CC1352P device and using SMART RF06 Evaluation board for programming custom board. I can able to debug and program my Board (i have tried with 10 devices, all are working fine). Suddenly one of my device could not able to debug or program. I am getting the following error when i program using uniflash tool.

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 8.0.27.9).

I searched in net for the error. In debug error issues i found this is occured due to following reasons

Security Error

This error is caused by the inability of the debug probe to communicate with the device or core, despite the physical connection is fine. This can be caused by a large number of sources, but the most common are:

The device being used is in secure mode and requires a specific procedure to unlock it. Certain devices have a security module that prevents any intrusive access to its core (including JTAG) and require a specific unlocking mechanism on the running code on the board (MLO, u-boot, etc.). A solution to this forcefully demands having this specific code. Contact your TI representative for details.
The device or core is either powered down, incorrectly or does not have a valid clock. In these cases the JTAG debug probe can be fooled into thinking the device or core are secure but they are simply inaccessible. The solution to this is not unique but it requires thoroughly checking all clock and power signals on the target board. Some reported issues are:
The device is flashed with code that prevents JTAG access to the core. This is mostly common on microcontrollers (due to the presence of Flash memory) and usually require a mass erase to clear its memory from the faulty code.
- https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/518464
- https://e2e.ti.com/support/wireless_connectivity/low_power_rf_tools/f/155/t/262357
  
  Note: for Launchpads, check if the TMS and TCK jumpers are in place.

How to unlock my device if it locked?

I could not even erase my code. I checked all the clocks are working fine

Thanks 
Haricharan

over 6 years ago

0 Haricharan sarpatwar over 6 years ago

Expert 1750 points

Hi,

Can anyone give a solution for my post.

I had checked following

2. The device or core is either powered down, incorrectly or does not have a valid clock. In these cases the JTAG debug probe can be fooled into thinking the device or core are secure but they are simply inaccessible.

I checked all the power and clocks

3. The device is flashed with code that prevents JTAG access to the core. This is mostly common on microcontrollers (due to the presence of Flash memory) and usually require a mass erase to clear its memory from the faulty code.

The code is working fine i checked with other hardware, it is not faulty code. I flashed my code several times on working Hardware and it working normally.

The device being used is in secure mode and requires a specific procedure to unlock it. Certain devices have a security module that prevents any intrusive access to its core (including JTAG) and require a specific unlocking mechanism on the running code on the board (MLO, u-boot, etc.). A solution to this forcefully demands having this specific code. Contact your TI representative for details.
I suspect this may happen so i require TI Help in unlocking my Device.

Thanks & Regards

Haricharan

0 desouza over 6 years ago in reply to Haricharan sarpatwar

TI__Guru**** 171044 points

Haricharan,

Please apologize for the delay. The CC13xx devices usually do not have devices with security, which require specific unlocking or access procedures, therefore this is not the issue at hand.

As mentioned in the reference, the security error is certainly something that may be caused by the software or the hardware itself. Given that only one device out of ten is giving problems, as you mentioned, chances are very high the hardware surrounding this particular device is faulty.

Therefore, there is very little that can be done from a software tools perspective, but two details may help you dig further into this:

- Step 8 of the section "troubleshooting the connect phase" of the Debugging JTAG reference you mentioned contains a procedure that allows you to inspect the status of the core from the JTAG perspective.

- You can try and mass erase the core by using the script mentioned in section "A router subpath cannot be accessed" of the same Debugging JTAG reference you mentioned.

Hope this helps,
Rafael

0 Haricharan sarpatwar over 6 years ago in reply to desouza

Expert 1750 points

Thank you for the reply i will try to check with my hardware team

Thanks & Regards
Haricharan

Code Composer Studio™︎

Code Composer Studio forum

CCS/CC1352P: Regarding Unlocking of CC1352P device

Security Error