When debugging the CSEc module of the S32K1xx chip, the chip is locked

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

When debugging the CSEc module of the S32K1xx chip, the chip is locked

跳至解决方案
678 次查看
ZEROOO
Contributor IV

Hi

    When debugging the CSEc module of the S32K1xx chip, the chip is locked, the debugger cannot be connected, and cannot be unlocked.

    CPU:S32K118

    Debugger:IC5000

   Fault phenomenon:1. The CSEc partition fails to be destroyed. 2. The CPU locks, all registers are inaccessible, and the winidea debugger is displayed offline.

    Method of fault recurrence:

    1.First execute the partition code, allocate space for the CSEc module, and then change another program to brush into the same CPU, and then use the command to erase the csec partition can not be executed correctly, this process has not changed MASTER_Key, but can not clear the partition of FlexNvm.

    2.Since it could not be erased, I tried to directly insert 0xFF to the flexnvm address to erase, and then execute mass erase, resulting in MCU lock, how to unlock, using the debugger can not unlock, winidea using unsecure return failure.

 

    I have asked for help many times on the forums and ticket post, hoping for technical support to help solve this problem, especially phenomenon 1, which is the primary reason why I locked the MCU. Thank you!

 

 

0 项奖励
回复
1 解答
559 次查看
VaneB
NXP TechSupport
NXP TechSupport

Hi @ZEROOO 

Unfortunately, there is a high probability that the MCU can not be unlocked.

Please take a look at the below application notes that could help you.

Using the Kinetis Security and Flash Protection Features.

Production Flash Programming Best Practices for S32K1xx MCUs.

 

B.R.

VaneB

在原帖中查看解决方案

1 回复
560 次查看
VaneB
NXP TechSupport
NXP TechSupport

Hi @ZEROOO 

Unfortunately, there is a high probability that the MCU can not be unlocked.

Please take a look at the below application notes that could help you.

Using the Kinetis Security and Flash Protection Features.

Production Flash Programming Best Practices for S32K1xx MCUs.

 

B.R.

VaneB