S32K144 CSEc Error

[Jason88619]

Hello, I am using the CSEc of the S32K144 chip. I use the S32K1xx CSEC Tool to generate an initialization binary file for the CSEc module, and download the initialization file into the S32K144 chip via J-link. Then I run my own program, and a Reset_Handler occurs at CSEC_DRV_InitRNG. Why is this happening? Did I set something wrong? The pictures below show some of my code and configurations.

[Jason88619]

As you mentioned, I checked my FCFG1 register and FCSESTAT register, but their values showed no changes before the program entered the Reset_Handle 。According to the FCFG1 register, the EEPROM memory has been allocated. However, I executed the Reset program generated by the S32K1xx CSEc Tool (though it may not have executed successfully). From the FCSESTAT register, the status of CSEc remains "Busy", even though no operations are currently being performed on CSEc. What should I do to restore CSEc to normal?

Best regard,

Jason

[lukaszadrapa · Accepted solution]

I did quick test on my board and it works as expected - I can enable CSEc by "Initial Firmware", then the CSEc works as expected and then I can reset the device by "Reset Firmware". But I noticed one difference: using the same configuration, DEPART is set 0x04 by the firmware. If I click on "Create Partition Code" in the tool, it is also showing 0x04:

But your screenshot shows that the DEPART is 0x08. It looks like the device is already partitioned but CSEc is not enabled. 

I can see it's not explicitly mentioned in the user manual of the tool, but I supposed that it expects that the partition is not set when running "Initial Firmware".

I would try to create RAM project and just run FLASH_DRV_EraseAllBlockUnsecure command. Not just FLASH_DRV_EraseAllBlock command because then it would be necessary to program flash configuration field to unsecured state. 

I believe that it will work as expected after such mass erase. 

Regards,

Lukas

[Jason88619]

Hi @lukaszadrapa 

As you suspected, the CSEC_DRV_InitRNG function executed successfully after FLASH_DRV_EraseAllBlockUnsecure. Although for some unknown reason a HardFault occurred during the execution of FLASH_DRV_EraseAllBlockUnsecure, the function subsequently completed successfully. After that, the CSEc was able to initialize normally.

Thank you very much for your explanations and help.Wishing you happiness every single day!

Best Regards,

Jason

[lukaszadrapa]

Hi @Jason88619 

CSE PRAM is not writeable if the device is not partitioned and if CSEc is not enabled. This was discussed here, for example:

https://community.nxp.com/t5/S32K/CSE-PRAM-is-not-writable-S32K146/td-p/1282095

Was the InitFW loaded and executed successfully? What can you see in FCFG1 register in SIM module?

Regards,

Lukas

[Jason88619]

Inside the CSEC_DRV_InitRNG function, immediately after executing the line

/* Write the command header. This will trigger the command execution. */
CSEC_WriteCommandHeader(CSEC_CMD_INIT_RNG, CSEC_FUNC_FORMAT_COPY

/* Write the command header. This will trigger the command execution. */ CSEC_WriteCommandHeader(CSEC_CMD_INIT_RNG, CSEC_FUNC_FORMAT_COPY CSEC_CALL_SEQ_FIRST, CSEC_SECRET_KEY); the program enters DefaultISR.

[lukaszadrapa]

... and also please check FCSESTAT register in FTFC module.