S32K146: Failure to wake up due to an interrupt occurring during VLPS mode entry

[ShaoTianzhi]

Hello: Recently, while debugging the code, I encountered an issue. My chip operates at 64MHz, and when calling the SDK function POWER_SYS_SetMode to enter VLPS mode, it takes about 16ms to execute until STANDBY();. Before reaching the line STANDBY();, an ACC ON interrupt cannot interrupt the process of entering VLPS. However, once VLPS is entered, the ACC ON interrupt has already been triggered, so there is no other interrupt available to wake up VLPS. Are there any methods to improve this problem?

[Senlent]

Hi@ShaoTianzhi

Does the "ACC ON" you're referring to a GPIO interrupt waking up the MCU?
If it's waking up via a GPIO, you can try changing the interrupt priority of that GPIO port and testing again.

[ShaoTianzhi]

The issue is that when calling POWER_SYS_SetMode to enter VLPS mode, it takes about 16ms from the start of the function until it reaches STANDBY();.

During this 16ms period, if a GPIO interrupt (ACC ON) triggers, it does not prevent VLPS entry—the function continues executing until STANDBY();. Only after STANDBY(); is executed does an interrupt become necessary to wake up the MCU from VLPS.

Is there a way to ensure the GPIO interrupt can abort the VLPS entry process if triggered during this 16ms window?

[Senlent]

Hi@ShaoTianzhi

You can check whether there is an interrupt nesting issue. If so, you can resolve this issue by adjusting the interrupt priority.

If there is no interrupt nesting issue, then I don't think this problem exists.

Also, check whether your GPIO interrupt service function clears the interrupt flag, i.e., "PINS_DRV_ClearPortIntFlagCmd(PORTn)".