Hello, I have a few questions while using the standby mode of S32K312:
1.What is the relationship between enabling the clock for MCU peripherals within the power management module and enabling the clock within the clock group? If I enable the clock within the clock group, do I still need to enable it in run mode?
2.For standby mode, if I use CAN to wake up the MCU, I noticed in the example routine that the flexcan0 clock within the MCU peripheral of the power management module is not enabled in standby mode. Is this configuration unnecessary?
3.If I want to use a specific CAN ID to wake up the MCU, do I only need to implement the relevant logic for judgment in the CAN 0 callback function?
Thank you for your help.
Hi @fengba_360,
1. Even if you are not using the POWER component, you can still enable and disable application cores and peripherals as needed, based on functional and power requirements.
For example, in the S32K3 Low Power Management AN and demos, a second functional group is used to enter the VLSR mode by simply switching the clock from PLL to FIRC:
The clock tool enables the clocks, and the power component enable the fields that gate the application core clocks, which can also be clock gated by executing Waiting for Interrupt (WFI). You can look at Chapter 46 from the S32K3XX's reference manual for more information.
If you use the power driver and set a power mode, you need to configure the peripherals used in that specific mode, using that same low power demos, you can see that the power driver is initialized, and the RUN mode is set:
This driver then configures the peripheral clock gating with the configuration set in "McuPeripheral".
2. Since FlexCAN itself is not a power domain, the module is not used for wakeup and does not need to be enabled for standby, only the external pin is used as interrupt which shares the FlexCAN functionality. Please refer to this post: Solved: Re: S32K3 Wake up method - NXP Community.
3. Since FlexCAN module does not provide wakeup, yes, functionality must be implemented in the callback.
Best regards,
Julián
I have been able to use the standby mode, but I encountered a problem. I selected two GPIOs (PTB28, PTC18) as wake-up sources, with PTC18 as the sleep control pin. When PTC18 is low, the S32K312 enters standby mode. At this point, if I provide a high level to PTC18, the S32K312 can be woken up, but a high level on PTB28 does not wake it up. When PTC18 is high, the S32K312 also enters standby mode. However, at this point, a low level on PTC18 cannot wake up the S32K312, but a low level on PTB28 can normally wake it up. Can you tell me the reason for this?
Additionally, does it support wake-up triggered by a specific CAN ID?
