CC1352R: OOPS....i locked my MCU

Part Number: CC1352R
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi

I have a custom board that uses a CC1352R.

In trying to resolve 1 issue i seem to have bricked my CC1352...when i try & download my program to the chip via a XDS110 i get the following error message...
"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 9.10.0.00080)"

i have tried 'Mass Erase' in uniflash but get the same error.
i tried testing the connection in CCS via the .CCXML file but also get the same message.

How can i unbrick the CC1352R??

thanks in advance

  • If you actually have bricked your device it's not possible to unbrick it. This is a safety feature, if you set set given bits in the CCFG that locks the access to the chip it should not be possible to get access to the chip again.  

  • so is the message indicating that the chip is really 'bricked' or in a state thats possible to get it 'unlocked'?

    (i never set any bits in the CCFG...i was setting the various pins of the jtag hi/lo individually)

  • Hi Moshe,

    Can you try power cycling the device, then connecting all the JTAG wires correctly and retry?

    Not sure how flipping JTAG lines individually can rick your device permanently.

    Cheers,

    Marie H

  • Hi Marie

    Thanks for the suggestion..sadly it didn't help.

    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 9.4.0.00129)

    but am willing to try anything before a replacement chip arrives

    cheers

    moshe

  • My experience is that if you have tested mass erase and you still got an issue your chip is dead...

    Since you get different results on the I2C issue with two different debuggers, I see two possibilities:

    - You have not fully control of the tool chain and you have managed to write to the CCFG without knowing. To check this, if you have the last hex file you flashed the chip with you can see if you have something on the last flash page that shouldn't be there.

    - The debugger gives sometimes slightly misleading error messages. Could it be something with the connections etc also considering the strange debugger difference you are seeing? 

  • i'm now not sure if i ever did a 'mass erase' as i am no longer sure where one does that. What i did do was, i went to uniflash, settings & utilities, & selected 'erase entire flash'. and still got the locked error when it tried to perform that operation.

    i suspect my I2C issues are due to timing issues (between querying the I2C device when it isn't actually being ready after power up) rather than the debuggers themselves....

    so i suppose with all my fiddling with the JTAG pins (bringing them to GND) while everything was all connected i somehow set the cc1352 into lock state.
    (fortunately the debugger was not affected). 

  • Hi Moshe,

    You could try downloading Flash Programmer 2 and see if it makes a difference, but I believe it uses the same mechanism for flash erase as Uniflash.

    https://www.ti.com/tool/download/FLASH-PROGRAMMER-2/1.8.2 

    I don't suppose you have a bootloader or enabled ROM bootloader in your sw project?

    Cheers,

    Marie H

  • Marie...you are a star!!

    board unlocked & prgram downloaded!!

    thank you!