S32K3 FastStandby Wakeup Problem

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32K3 FastStandby Wakeup Problem

1,390 Views
AmitoYao
Contributor II

a.png

Call function reset in faststandby's wake-up function will cause the variables assigned in this function to not take effect.

These variables are all defined in standbyram.

It seems that function reset in the faststandby wake-up function will restore the standbyram to the state before entering standby.

But this will not happen if you jump through bl reset_handler。

What is the problem?

0 Kudos
13 Replies

1,331 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@AmitoYao

very interesting question.

After spending a long time, I finally found that you just need to add a delay to ensure that the command

has enough time to execute.

Senlent_1-1701850998348.png

 

 

0 Kudos

1,328 Views
AmitoYao
Contributor II

It's so strange. How could a simple assignment statement take so long? This results in longer wake-up times。

0 Kudos

1,323 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@AmitoYao

This delay is just what I used for testing, not the minimum delay time.
But this should be the cause of the problem

0 Kudos

1,320 Views
AmitoYao
Contributor II

But why is there no such problem through jump "bl reset_handler" ? That is no delay time.

0 Kudos

1,298 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@AmitoYao

It's difficult for me to explain the difference, it's beyond my capabilities.

0 Kudos

1,285 Views
AmitoYao
Contributor II

I tested this because after the standby wakes up, It will cause the WDI watchdog timeout problem using the fls driver to erase and program the dflash, but the function reset will not. Can you give feedback on this problem?

0 Kudos

1,269 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@AmitoYao

"I tested this because after the standby wakes up, It will cause the WDI watchdog timeout problem using the fls driver to erase and program the dflash, but the function reset will not. Can you give feedback on this problem?"

Is this a new problem?
Isn't it okay to close SWT before entering standby mode or before performing memory operations?

0 Kudos

1,264 Views
AmitoYao
Contributor II

It is not the SWT. It is the wdog used for flash .

a.png

0 Kudos

1,253 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@AmitoYao

more difficult to understand
You can sort out your problem, provide a demo program that can reproduce the problem (non-MCAL demos are best), and then send it to me, and I will upgrade it to the internal forum.

0 Kudos

1,373 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@AmitoYao

I guess it's because the program will Init Standby SRAM after function reset

Senlent_1-1701767598761.png

 

 

0 Kudos

1,356 Views
AmitoYao
Contributor II

I didn't init the standby ram when function reset, the var modified in the main function didn't lose

.

0 Kudos

1,353 Views
Senlent
NXP TechSupport
NXP TechSupport

Hi@AmitoYao

Could you please share the project so that i can reproduce your problem.

0 Kudos

1,348 Views
AmitoYao
Contributor II

Attached is my project.

0 Kudos