topic Re: [Security] CSEC component invoke the eraseKeys interface problem in S32K

[Security] CSEC component invoke the eraseKeys interface problem

Gideon — Thu, 04 Jul 2024 02:12:10 GMT

Dear NXPs:

S32K146;

S32DS sample 《csec_keyconfig_s32k146》

NXP NVM has written the key. First burn the Clear Key project. After calling the bool eraseKeys(void) interface in csec_utils.c, the key is successfully erased. Burn the KeyLoad project again. Under IAR Debug, hardFault occurs in the first run. Reset (the greenbox is the IAR Debug reset button) and execute again. Key is written successfully. (Two projects are designed, one Clear key and one load key. When using them, it is found that after the Clear key project is running, the loadkey project is burned again. It is found that the loadkey project is not executed. IAR Debug finds that it has entered hardFault. The participation of IAR Debug is only a temporary solution). I need your help, please

Re: [Security] CSEC component invoke the eraseKeys interface problem

lukaszadrapa — Wed, 10 Jul 2024 08:52:16 GMT

Hi @Gideon

Isn't just an additional reset needed? That's the only probable root cause I can see.

Regards,

Lukas

Re: [Security] CSEC component invoke the eraseKeys interface problem

Gideon — Sat, 13 Jul 2024 04:10:42 GMT

@lukaszadrapa
Thank you for your strong support.I called the following function and found that it still didn't work.
void SystemSoftwareReset(void)
{
uint32_t regValue;

/* Read Application Interrupt and Reset Control Register */
regValue = S32_SCB->AIRCR;

/* Clear register key */
regValue &= ~( S32_SCB_AIRCR_VECTKEY_MASK);

/* Configure System reset request bit and Register Key */
regValue |= S32_SCB_AIRCR_VECTKEY(FEATURE_SCB_VECTKEY);
regValue |= S32_SCB_AIRCR_SYSRESETREQ(0x1u);

/* Write computed register value */
S32_SCB->AIRCR = regValue;
}