Hello,
When I debug S32K344 with PE Micro, I found that an array(__attribute__ ((section(".standby_data"))) volatile uint32_t WkupSourcestatus1[64];) located in the standby RAM section is unexpectedly modified when entering main(). Then, as shown in the attached video, I manually modified the registers to reinitialize the standby RAM area. The data was correctly initialized to 0, and after entering main(), everything ran fine. However, after a reset, when I enter the Reset_Handler, the data in the WkupSourcestatus1 array is modified again. Why is this happening? I noticed that a large number of 0x5AA55AA5 values appear in the array. Is this related to the SBAF_BOOT_MARKER? I tested this on another board and the phenomenon is the same.
Then I switched to using J-Link for debugging and found that no abnormality occurs during a reset while debugging. However, after a debug session is restarted, all data in the standby RAM area becomes 0xDEADBEEF. Is this expected behavior?
S32K344
S32DS3.6.4
RTD700
PE v.6.0.8
BR,
Jason
