Hi NXP,
I am testing the Advanced Secure Boot's checkPeriod function on the S32K312. I want to use it to monitor whether the app code on the plash if tampered with runtime. I have the following questions:
1. The checkPeriod in the SMR structure requires the configuration of the pSmrDest address. Does this mean that the background check can only target SRAM? Also, does it require the user to manually copy data to pSmrDest after the CR (Configuration Register) is set, in order for the HSE to function? However, the SRAM on the S32K312 is too small to fit the entire app code.
2. If the checkPeriod can only monitor data in SRAM, what is its main application scenario?
3. Can the checkPeriod background monitoring be defined within the CR?
4. If an error occurs during the monitoring, does it only set a status flag, or it can't stop the CPU from running?
我正在测试S32K312 HSE的advanced secure boot 的 checkPeriod 功能,
想使用他运行时监测plash 上的app代码是否被篡改. 有如下疑问,
1. SMR结构中的 checkPeriod 需要配置 pSmrDest地址,是否说明这个后台检查只能针对sram.
并且需要用户在过了CR后,手动复制数据到pSMRDest上, hse 才能工作? 但S32K312的sram太小了,app代码无法全部放到sram上
2. 如果checkPeriod只能监测SRAM上数据,它的主要应用场景是啥?
3. 这个checkPeriod 后台监测是否SMR 不能定义到CR中?
4. 这个checkPeriod 后台监测发生错误, 是否只是设置status 标志位,不会停止cpu运行?
