I attempted to use the sample program "Sbc_fs26_Example_DS" to put FS26 into normal mode, but it failed. It seems that the first watchdog feed during initialization is already failing. Here is my code and the UART printout. I noticed that whenever it exits debug mode, it causes the entire FS26 to reset, repeatedly cycling through this code.
#S32K3-T-BOX #FS26
已解决! 转到解答。
Hello,
I hope all is great with you. Thank you for using the NXP communities.
Please review the response from one of our specialist below:
WD need right Content regardless of WD refresh time if SBC is in debug mode.
so please check if the WD refresh content is right or not.
Below is an process for SPI commands to let FS26 enter normal mode. For your reference.
I hope this information helps.
Regards,
David
Hello,
I hope all is great with you. Thank you for using the NXP communities.
Please review the response from one of our specialist below:
WD need right Content regardless of WD refresh time if SBC is in debug mode.
so please check if the WD refresh content is right or not.
Below is an process for SPI commands to let FS26 enter normal mode. For your reference.
I hope this information helps.
Regards,
David
I followed your instructions to set up FS26, but I still couldn't successfully feed the dog. I have tried feeding it with the default value 5AB2 and also attempted to change the token to AAAA for feeding, but none of these attempts were successful. Below is the information I printed. I also tried adding "exit Debug mode" directly afterwards, but every time I add it, FS26 resets. I even attempted to disable the watchdog, but it didn't make any difference.
How can I resolve the following issues?
thanks a lot
Hello,
Please accept my apologies for the delayed response.
The SW sequence is first WD refresh and then exist Debug mode, from your description, there is no Reset during first WD refresh, but Reset happaen when sending Exist Debug mode commands,Right ?
If so, that means first WD refresh is OK and the reset is happen due to leaving debug mode. Please check whether customer has configured WD window to be 0 with beloew 2 commands. other wise, customer need feed the WD with configured window time Periodly in non-debug mode.
Regards,
David