Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NXP: MCXN947: HWINFO: Add implementation of hwinfo_get_reset_cause API in HWINFO module for MCXN947 MCU #84114

Open
theadib opened this issue Jan 16, 2025 · 0 comments
Assignees
Labels
area: HWINFO Hardware Information Driver Enhancement Changes/Updates/Additions to existing features platform: NXP NXP

Comments

@theadib
Copy link
Contributor

theadib commented Jan 16, 2025

Is your enhancement proposal related to a problem? Please describe.
I am working with frdm_mcxn947 board.
Currently the HWINFO module only implements uuid api.
The API for Reset reason is not implemented.

Describe the solution you'd like
please implement the hwinfo_get_reset_cause API

Describe alternatives you've considered
the gathering of reset cause can also be done using manufacturers hardware libraries and register definitions.
But the resulting information must be converted to the zephyr information enums manually.

Additional context
hwinfo_get_device_id() for this MCU is implemented in hwinfo_mcux_syscon.c

For this MCU theregister containing the relevant information is the System Reset Status SRS or Sticky SystemReset Status SSRS that can be found in the Core Mode Controller CMC module.
See MCXN947 reference manual page 1447ff.: 38.7.1.8 System Reset Status (SRS)

@theadib theadib added the Enhancement Changes/Updates/Additions to existing features label Jan 16, 2025
@DerekSnell DerekSnell added the area: HWINFO Hardware Information Driver label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: HWINFO Hardware Information Driver Enhancement Changes/Updates/Additions to existing features platform: NXP NXP
Projects
None yet
Development

No branches or pull requests

5 participants