Dear S32K3 Team,
I am currently working with the S32K358 MCU, where I am attempting to transition the MCU into standby mode and then wake it up into run mode via a WAKEUP input. On the S32K344 reference board, simply configuring the WAKEUP signal and switching the MCU mode correctly outputs the reset reason. However, I am encountering issues with the same process on my board using the S32K358.
Current Status:
- I have enabled the low-power mode on the MCU.
- All peripheral clocks have been disabled.
- The mode change is being handled through the Mcu_SetMode function.
- I have confirmed that the MCU enters standby mode, with power consumption dropping by over 25%.
Reset behavior on the S32K344:
- On WAKEUP input:
- GetResetRawValue = 0
- GetResetReason = 28
- On Power-On Reset (POR):
- GetResetRawValue = 0
- GetResetReason = 0
Reset behavior on the S32K358:
- On WAKEUP input:
- GetResetRawValue = 0x8000
- GetResetReason = 0
- On POR:
- GetResetRawValue = 0x8000
- GetResetReason = 0
- On Functional Reset:
- GetResetRawValue = 0x800
- GetResetReason = 26
Questions:
During the wakeup on the S32K358, the GetResetRawValue = 0x8000 is observed from the DES register, which corresponds to a System clock dividers alignment failure. Could you please provide guidance on the possible cause of this issue and what I should check further?
During the Functional Reset, the GetResetRawValue = 0x800 was found in the FES register, but I am unclear about the meaning of this value. Could you please clarify its significance?
I am curious if the fact that the reset reason is not showing 28 during the wakeup on the S32K358 is related to the DES register value of 0x8000. Any insights on this would be greatly appreciated.
I would greatly appreciate your support and guidance on resolving these issues.
Thank you.
Best regards,
