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

ソリューションへジャンプ
534件の閲覧回数
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 解決策
415件の閲覧回数
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 返信
416件の閲覧回数
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