Call "ForceInternalWatchdogTrigger".  That prevents any other tasks from running so after a few seconds, bang!  The command to do that is "test internal wd".

There is code for an external watchdog (i.e. using a wd chip outside of the processor) but that won't be used on the Launchpad.

73,

Burns Fisher, WB1FJ

AMSAT(R) Engineering -- Flight Software

On Mon, Oct 2, 2023 at 4:18 PM Chris Thompson via pacsat-dev <pacsat-dev@amsat.org> wrote:

I made some changes to allow the watchdog to be started.  Once I added some calls to the Uplink task and removed the CAN task from the wdReports list it stopped rebooting in a loop due to the watchdog.

I now have it running with the watchdog enabled but I can't cause it to trigger the watchdog from a task.  So I either don't understand what needs to be done or the watchdog is not working properly.

The watchdog enabled code is checked into g0kla_watchdog

If there is a simple line of code to trigger the watchdog then let me know.  I was just trying to add a suitable delay.

73

Chris

--

Chris E. Thompson
chrisethompson@gmail.com
g0kla@arrl.net

-----------------------------------------------------------

pacsat-dev mailing list -- pacsat-dev@amsat.org
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org
To unsubscribe send an email to pacsat-dev-leave@amsat.org
Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org