-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Labels
bugThe issue is a bug, or the PR is fixing a bugThe issue is a bug, or the PR is fixing a bugplatform: NXP S32NXP Semiconductors, S32NXP Semiconductors, S32priority: lowLow impact/importance bugLow impact/importance bug
Description
Describe the bug
S32K3 devices allow to retain SRAM contents through a hw mechanism but currently the SRAM contents are always being zero-initialized at boot time to prevent ECC errors for occurring: https://github.com/zephyrproject-rtos/zephyr/blob/main/soc/nxp/s32/s32k3/s32k3xx_startup.S
To Reproduce
- write data in SRAM after booting the device
- issue a functional reset (e.g. watchdog expires - not currently supported in
main
branch) - read previous data from SRAM after booting the device - contents are cleared.
Expected behavior
SRAM contents are retained across functional resets and ECC initialization is only performed if coming from a destructive reset (e.g. PoR).
Impact
defective functionality
Environment (please complete the following information):
- OS: Linux
- Toolchain Zephyr SDK
- d2a4522
Additional context
NA
Metadata
Metadata
Assignees
Labels
bugThe issue is a bug, or the PR is fixing a bugThe issue is a bug, or the PR is fixing a bugplatform: NXP S32NXP Semiconductors, S32NXP Semiconductors, S32priority: lowLow impact/importance bugLow impact/importance bug