Hello,
We have an NXP BMU board which is fitted with FS26 SBC.
I am trying to use a simple watchdog algorithm to make SBC happy.
I have followed Wdg_FS26_HLD_Example (SW32K3_SBC_FS26_4.4_1.0.0) and I found two issues:
1. The Wdg_fs26 MCAL uses WDG MCAL but the .mex in the example doesn't have it.
2. Wdg_fs26 routine reads FS_STATES (0x57) and finds out that FS is in init state so it triggers watchdog by calling "Wdg_fs26_Ip_Trigger" function. Wdg_fs26_Ip_Trigger inturn calls Sbc_fs26_WdRefresh which checks watchdog type and it comes to be disabled so the watchdog never triggers and eventually I get a reset,
Below is the trace on SPI
Initialization routine:
Initialization routine continued:
And then there is continuous request of FS State with no watchdog trigger:
Can you please guide me through this.
Regards,
Hemant Kapoor
Hi,
1. This example using Wdg_43_fs26 plugin (External Watchdog driver for the FS26), so that's why it used Wdg_fs26 module:
2. Watchdog type and it comes to be disabled so the watchdog never triggers and eventually I get a reset -> Because this is the checking for SBS watchdog, but this example is using external watchdog so it will jump into Disable condition.
In case you want to use Internal watchdog, I think you should untick the External Watchdog checkbok, then choose corresponding watchdog type then try your example again:
Hi,
1. This example using Wdg_43_fs26 plugin (External Watchdog driver for the FS26), so that's why it used Wdg_fs26 module:
2. Watchdog type and it comes to be disabled so the watchdog never triggers and eventually I get a reset -> Because this is the checking for SBS watchdog, but this example is using external watchdog so it will jump into Disable condition.
In case you want to use Internal watchdog, I think you should untick the External Watchdog checkbok, then choose corresponding watchdog type then try your example again:
The new release package for FS26 on S32K3XX is available on NXP product list, please take it for your note:
