how can i use the warchdog timer in netduino Plus (with firmware 4.2)
i tried
Watchdog.Enabled = true;
but it still always false !!!!
any help will be welcome
  | ||||||||||||||
WatchDog Timer & netduino Plus
Started by HAMZA, Dec 09 2012 02:08 AM
6 replies to this topic
#1Posted 09 December 2012 - 02:08 AM
Hi
how can i use the warchdog timer in netduino Plus (with firmware 4.2) i tried
but it still always false !!!! any help will be welcome Attached Files#2Posted 09 December 2012 - 09:48 AM
Look at this thread: http://forums.netdui...-netduino-plus/
The watchdog is there on the hardware, but the stock firmware just turns off the watchdog, and has stubs for all the functionality.
I got it working on ND+ firmware 4.1.0.6, my next goal is to make it working with CW2's 4.1.1b1 firmware with 1-wire support.
#3Posted 09 December 2012 - 12:47 PM
hi ToniA thank your for help i have an DS1820 that i want to try with netduino+, if 1-wire work also, i will be very happy #4Posted 10 December 2012 - 05:32 PM
Please let me know if this works for you (unfortunately 1-wire isn't yet available on 4.2-based firmware): https://github.com/d...re_watchdog.zip
Flashing procedure:
#5Posted 21 February 2013 - 10:15 PM ToniA,
I'd love to know how you enabled the watchdog. I'm compiling my own STM32F4 firmware using GCC 4.6.2. I see all the driver files and the stubs you mentioned, but I don't know what I should change. Please let me know. #6Posted 06 March 2013 - 09:55 AM I've been working with the watchdog on the Netduino 4.2 firmware (using CW2's 1-wire additions). And I have faced an interesting problem, something in the firmware is constantly setting the watchdog on and off.
As a debug version, I modified the file DeviceCode/Drivers/Stubs/Processor/stubs_WATCHDOG/stubs_functions_WATCHDOG.cpp on the firmware side, so that every time the watchdog is enabled the on-board led is turned on, and every time it's disabled the led is turned off. I'd expect the led to change status every time I set the 'Watchdog.Enabled' property on the managed code side, but now it's flickering all the time, meaning that the firmware is turning it on and off all the time. What the heck...
I did the same trick for the method 'Watchdog_ResetCounter', and at least that proves that the watchdog is indeed fed frequently enough. #7Posted 06 March 2013 - 12:59 PM
The CLR runtime calls Watchdog_xxx functions during execution (in CLRCoreExecution.cpp), and in a few other places too. 1 user(s) are reading this topic0 members, 1 guests, 0 anonymous users | ||||||||||||||
|
||||||||||||||
This webpage is licensed under a Creative Commons Attribution-ShareAlike License. | ||||||||||||||