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?
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?
"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?
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.