Hi, i got a question,when i use CSEc module in S32K146,when the program code access the CSE_PRAM space,it will be into exception interrupt in Debug mode.point it in the below:
#define REG_WRITE32(address, value) ((*(volatile uint32*)(address))= (value))
#define CRYPTO_PRAM_HDR_ADDR32 (0x14001000u)
REG_WRITE32(CRYPTO_PRAM_HDR_ADDR32, u32CommandHeader);
The highlighted code is shown in the figure above, mean that the command to write PRAM cause progarm into exception Interrupt.
Do you know that problem ?
Could you give me some advice or resolution?
Best Regards,
BigJulie.
Solved! Go to Solution.
Hello,
There are two things that you can check before entering Csec operation:
- Check if your S32K silicon has supported CSEc in it, by checking SIM_SDID[FEATURES]
- In order to enable the CSEc, the Memory need to be partitioned for EEPROM, and FTFC registers need to be programmed.
Unfortunately, MCAL CSEc code hasn't implemented these steps, and you need to implement in your application code.
Here is the link for our CSEc training program that you can refer to: https://community.nxp.com/t5/Technology-Days-Training/MCU-Technology-Topic-Hands-On-Workshop-Writing...
Best Regards,
Nam
Hello,
There are two things that you can check before entering Csec operation:
- Check if your S32K silicon has supported CSEc in it, by checking SIM_SDID[FEATURES]
- In order to enable the CSEc, the Memory need to be partitioned for EEPROM, and FTFC registers need to be programmed.
Unfortunately, MCAL CSEc code hasn't implemented these steps, and you need to implement in your application code.
Here is the link for our CSEc training program that you can refer to: https://community.nxp.com/t5/Technology-Days-Training/MCU-Technology-Topic-Hands-On-Workshop-Writing...
Best Regards,
Nam
Thank you for your reply,that's useful for me,it working.
Best Regards.