Hi,
Micro: S32K312
We are using ICU Channel as a Wakeup unit for CAN. Attaching the ICU Channel configuration.
As per our understanding, ICU Channel will invoke the interrupt when there is a CAN Message (voltage change detected on ICU Channel) and below sequence of Functions will get executed.
Icu_ReportWakeupAndOverflow()
EcuM_CheckWakeup(WkpSource);
Icu_CheckWakeup(WkpSource);
Ecum_SetWakeupEvent();
etc.....
Problem: We are able to generate the interrupt on ICU Wakeup channel configured as a Wakeup Capable once we send NM Message. We could execute the Icu_ReportWakeupAndOverflow(); also, but we are not able to Execute Ecum_CheckWakeup(); because the channel state is always ICU_CHANNEL_STATE_IDLE (we are making ICU Mode to sleep while triggering sleep for ECU). As the channel state is Idle, and the ICU Mode is Sleep, the condition is getting invalid to execute EcuM_CheckWakeup();
Please go through the below Executing sequence once we receive the interrupt for ICU:
Please find the below screen shot for ICU Channel configuration:
Hi @harsh_95,
Are you able to share your main.c to see if all of the configurations shown in the picture are done correctly?
Just keep in mind that the EcuM_CheckWakeup function is a function stub only. You need to have enabled the respective module (in this case ICU) for the function to work correctly (or call Icu_CheckWakeup directly)
I have also sent you a private message through the community.
Best regards,
Julián
Hi @harsh_95,
Point-2 I believe this comes from the AUTOSAR specification since it is established that the function can be called from a wakeup ISR, but the K3 family shares the same ISR for all of the wakeup sources:
You can call the EcuM_CheckWakeup in the fast standby user defined boot address, so it is the first thing after exiting standby:
Let me check the functionality with EcuM module for checking wakeup sources with the internal application team, I will get back with you as soon as I get an answer.
Point-3 You can refer to the previous picture. After normal standby exit, a functional reset will be asserted and the MCU will run the reset handler back into the main code. When using fast standby exit will skip sBAF and HSE initialization and will run a user defined boot address so you can handle higher priority wakeup sources.
You can find some examples for this in these community posts:
- S32K3 Low Power Management AN and demos - NXP Community
- S32K3 Low Power Management AN and demos RTD 4.0.0 & 5.0.0 - NXP Community
Best regards,
Julián
Hi @harsh_95,
After normal standby exit, the MCU performs a reset. If using fast standby exit, you can implement a reset handler after your user defined boot address, as shown in the bottom of the following image:
Best regards,
Julián
HI Julian,
Thanks for the quick support.
As of now, the Microcontroller is not doing any Rest while waking up. Even the control is not going to bootloader also. Instead, the control is in application and it starts the normal communication.
But, We have observed that while waking up, sometimes we go into OS_Endlessloop() because of OS_CORTEXM_EX_SYS_TICK exception. The behavior is sporadic.
Tricks we tried:
1) Changed the OS timer from STM0 to PIT2.
2) Validated the OS priorities.
If you can help us on what can be the reason for this exception. Below is the screen shots of the function where exception is occurred.
Hi Julian,
Yes, we are using Fast standby exit. Below are the configuration screen shot. The problem we are facing is we are not able to jump to the configured Boot base address.
As per the configured Boot base address, we were trying to jump to application after wakeup, but we are not able to. (Just for understanding as of now, we are trying to jump to main(), but we want to jump to reset handler)
We are using bootloader and Application.
Let me know incase the configuration parameter needs to be corrected.
