EcuM Alarm Function

[ydygcvjhbjkjnkn]

Hello,

Regarding the EcuM alarm clock issue, I have consulted some materials and the manual, but there are a few points I do not quite understand, so I would like to ask for your help. Thank you.

1. In the EcuM manual, in the section introducing configuration items, how is the configuration item EcuMAlarmClockTimeOut used? It seems that I have not used it in my design.

2. How is the EcuM alarm clock updated? Currently, during the UP phase, I update it in the main function using the main function scheduling cycle. However, the documentation says that it should be implemented by a hardware timer. I am concerned that task blocking or preemption may cause the main function scheduling cycle to be incorrect. How should it be implemented using a hardware timer?

3. How should it be implemented during the SLEEP phase? The documentation mentions the POLL phase, where EcuM_SetClock is used in EcuM_SleepActivity for updating. After updating, where is the timeout checked? Is it in EcuM_CheckWakeup? And what about the HALT phase? Where is the clock updated and the timeout checked?

4. If the configured alarm has already expired before entering sleep, what should I do? Should I directly skip entering sleep, or should I set the alarm wake‑up source to suspend and notify BswM of the alarm wake‑up source status?

I look forward to your reply. Thank you. In addition, please provide the basis and supporting points, indicating which parts of the manual can be referred to for confirming the implementation approach. Thanks again in advance.

[danielmartynek]

Hello @ydygcvjhbjkjnkn,

Can you please specify the drivers/revision, and the MCU part number?

Thank you,

BR, Daniel

[ydygcvjhbjkjnkn]

I am referring to the AUTOSAR EcuM specification manual, version 4.2.2. The MCU part number may not be fixed.

[danielmartynek]

AUTOSAR 4.2.2 is an outdated specification, and no currently supported NXP Real-Time Drivers (RTD) package is based on it. The only NXP software that was aligned with AUTOSAR 4.2.2 was the legacy MCAL for S32K1xx, which is no longer supported.

Also, please note that NXP support covers only NXP's own RTD/MCAL driver implementations. If you are using a BSW stack from a third-party vendor, their EcuM implementation is outside the scope of what we can support here, and you would need to contact that vendor directly.

Regards,

Daniel