Dear NXPs：
Bootloader- D-Flash-32K
Are there any restrictions if I call CSEC_DRV_EncryptCBC/CSEC_DRV_DecryptCBC interfaces of the CSEc driver on D-Flash?
I haven't met this use-case yet but I can see in the manual that you are right. It explicitly says:
If your code is running from data flash, solution is to put the function to RAM memory.
Dear lukaszadrapa：
@lukaszadrapa
A1:Disabling interrupts has no effect.The interface I use is
By the way Viewed the manual S32K-RM.pdf Table 37-7. Allowed simultaneous memory operations,
There are limitations in operating CSE PRAM on D-Flash，Could IBUSSERR be related to this?
Hi @Gideon
not sure what's going on.
First step - did you try to disable interrupts? Second step - you can try to find out what is the reason of the fault exactly:
https://community.nxp.com/t5/S32K-Knowledge-Base/Fault-handling-on-S32K14x/ta-p/1114447
https://www.nxp.com/docs/en/application-note/AN12201.pdf
Regards,
Lukas
Hi @Gideon
If we are talking about CSEc commands CMD_ENC_CBC and CMD_DEC_CBC, there are no limitations because it is up to software to load plain/encrypted data to CSEc via PRAM interface and then read encrypted/plain data from PRAM. So, software can read the data from anywhere. Mentioned SDK function do not check the addresses, so it can read the data from whole memory map. Just the output buffer needs to be in RAM, of course, so the driver can write the result to the buffer.
Regards,
Lukas