• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 91 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

MSPM0G3507: the chip is often get locked

steve henry
Prodigy 10 points
Part Number: MSPM0G3507

Tool/software:

Hi there!

My ccs version is 12.6. I am trying to develop some functions in MSPM0g3507(LQFP 48Pins). Every time when i try to debug the program then power down, if i try to debug again it shows that the chip is unable to be connected. with some reserach i figure out how to unlock the chip but why the chip can be locked so often? what kind of reasons will make the chip get locked? will you give me some advice, thank u!

  • 0
    TI__Genius 13335 points

    Hi Henry,

    From my perspective, the reason device why device get locked might be belows:

    1. The device enter fault status, and can not response to the swd connection signal.

    2. unstable swd connection and makes the error 

    3. user configure the NONMAIN region which is used for security function and lock the device

    4. some debugger do not support deep low power mode, like standby mode. (TI XDS110 debugger should support it, except shut down mode)

    5.The code will trigger BOOTRST reset within its code, and it might break the swd connection.

    Except using scripts to unlock the device, usually user can conncect PA18 to VCC, then it could avoid software issued which cuases the device locked. -> this will trigger rom bsl and force it pending in bsl mode, then application code will not run and user could connect it with debugger.

    Hope these information could help you.

    B.R.

    Sal

  • 0
    Guru 39060 points

    I find that fiddling with the non-volatile memory leads to lock-ups that require resetting. If I use the standard .cmd file, it rarely locks up.

  • 0 in reply to Keith Barkley
    TI__Genius 13335 points

    Hi Keith,

    Yes. I suppose you mean NONMAIN Flash memory in MSPM0 device. It supports MSPM0 security function including SWD interface. It has separately memory address compared with MAIN flash address with default cmd file.

    Unproper operation on NONMAIN will lock the device and requires unlock, Incorrect opearion will even permanently lock device.

    B.R.

    Sal

  • 0 in reply to Sal Ye
    Prodigy 10 points

    Thank you for you replying!

    As mentioned above, I use J-Link to debug the chip(MSPM0G3507). the version of J-Link is V7.98b. The first time when I debug my program, the board and the chip works well by the way I make the board by myself. Later I power it down and power it up, I try to debug my program again but CCS ocuurs an error:CORTEX_MOP: Trouble Writing Register PC: Error occured in writeRegister ()!  After I follow the tips cancelled this debug , I debug my program again.CCS occurs an another error which shows that unable to connect the target. 

    In the whole time I have not changed my debug settings. When I try more times always get the same error. If I just power on the chip and board without debugging, the chip and board still work well. It seems to be unlocked.

    Then I try to download the program with J-Flash ,J-flash shows an error which is " Timeout while programming sector, RAMCode did not respond in time (PC = 0x00000026, XPSR = 0xF1000002, SP = 0x20207FE0)!" I am not sure where I did wrong to trigger this error. Looking forward to your help!

  • 0 in reply to steve henry
    TI__Genius 13335 points

    Hi Steve,

    Actually, I met this error sometimes before. It looks like the CCS debug is not compatible to J-Link well.

    Maybe you can upgrate your CCS version to latest, it will update integrated j-link version. (The default version is quite old in previous CCS version)

    J-link manually installed by the user will not be updated to CCS.

    B.R.

    Sal