S32K中的主题 Re: How to save data during reset

How to save data during reset

Pusoy — Mon, 08 Jan 2024 03:34:10 GMT

Hello,

I am currently using BIST in the project, but before executing BIST, I need to disable the communication peripherals, and a reset occurs after completing the BIST. Therefore, I have not yet found a way to identify the cause of the system reset that occurs before executing BIST.

1. Is there a method to preserve data even after a destructive reset or functional reset occurs?

Re: How to save data during reset

petervlna — Mon, 08 Jan 2024 09:05:34 GMT

Hello,

You simply look after reset to RGM [DES/FES] registers after the BIST.

RGM module preserve reset source information trough all type of resets except power on reset.

Best regards,

Peter

Re: How to save data during reset

Pusoy — Mon, 08 Jan 2024 09:15:47 GMT

Hello, thank you for your reply.

I need to call the Mcu_GetResetReason() function before executing BIST to obtain the previous reset reason.
But this function clears the values of the RGM [DES/FES] registers,.
so I need another method.

Re: How to save data during reset

petervlna — Mon, 08 Jan 2024 10:48:11 GMT

Hello,

I need to call the Mcu_GetResetReason() function before executing BIST

Ok, so store the RGM content to some NVM. like EEPROM which is quite common use case.

Simply preserve the FES and DES so you can analyze it.

Best regards,

Peter

Re: How to save data during reset

Pusoy — Tue, 09 Jan 2024 02:32:35 GMT

Hello, thank you for your reply.
I forgot to mention that we currently don't have any extra EEPROM space in our project to store data, so that solution doesn't apply to us.
We need a solution where data can still be retained in a RAM area even after a destructive reset occurs.

Re: How to save data during reset

petervlna — Tue, 09 Jan 2024 05:51:27 GMT

Hello,

But this function clears the values of the RGM [DES/FES] registers,.

Since you are out of options simply modify / write your own function for RGM reads which wont clear them.

We need a solution where data can still be retained in a RAM area even after a destructive reset occurs.

Well, its called a destructive reset for some reason. RAM content is destroyed.

I have not yet found a way to identify the cause of the system reset that occurs before executing BIST.

I would set loop/break right before execution of the BIST, read out the RGM to understand the reset cause from debugger.

Usually you do system reset reading in startup code and branch the code based on its results. I do not understand why you do it right before BIST.

Best regards,

Peter