*******************************************************************************
The purpose of this demo application is to present a usage of the
FS26 watchdog timer refresh using the SBC_FS26 CDD
------------------------------------------------------------------------------
* Test HW: S32K3X2EVB-Q172
* MCU: S32K312
* Compiler: S32DS3.5
* SDK release: RTD 3.0.0
* FS26 : CDD 2.0.0
* Debugger: PE micro
* Target: internal_FLASH
********************************************************************************
Watchdog type :--
NXP eval boards has ASIL-D FS26 part with challenger watchdog.
The OTP of FS26 on the board uses challenger watchdog.
Change watchdog in code :--
FS26 watchdog is started in disabled mode (means infinite period).
Later on we change the watchdog time in the code :--
Array Index for watchdog refresh timing :--
Example will run once you press switch USER_SW0 connected on PTB26 on the Evaluation board :--
Please add this type of check in your code, during development process so that, avoid any error due to FS26 watchdog mis trigger. When you use Debug FLASH then in that case code goes to flash memory & can cause your MCU to frequent RESET, which caused issue for reprogramming the NEW firmware on the board FLASH memory. If we add this type of check then we can avoid the Faulty FS26 Software to stop misbehaving before flashing new firmware on the board.
In CDD-2.0.0, If we start the Watchdog in enabled mode, watchdog notification function to refresh watchdog is called from this function :--
Sbc_fs26_InitDevice() --> Sbc_fs26_NormalFSSequence() -->
In CDD 2.0.0, Following function call will exit Debug mode & Release FS0b & FS1B pin :--
Sbc_fs26_InitDevice() --> Sbc_fs26_NormalFSSequence() :---
--> Sbc_fs26_ExitDebugMode()
--> Sbc_fs26_ReleaseSequence()
In CDD 2.0.1, Following function call will exit Debug mode & Release FS0b & FS1B pin :--
Sbc_fs26_InitDevice() --> Sbc_fs26_NormalFSSequence() --> Sbc_fs26_ExitDebugMode()