Update Watchdog description
This commit is contained in:
parent
b6279abd30
commit
9ccbd382e7
@ -1004,14 +1004,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -38,7 +38,7 @@ void watchdog_init() {
|
||||
#define WDTO_NS WDTO_4S
|
||||
#endif
|
||||
#if ENABLED(WATCHDOG_RESET_MANUAL)
|
||||
// We enable the watchdog timer, but only for the interrupt.
|
||||
// Enable the watchdog timer, but only for the interrupt.
|
||||
// Take care, as this requires the correct order of operation, with interrupts disabled.
|
||||
// See the datasheet of any AVR chip for details.
|
||||
wdt_reset();
|
||||
@ -65,7 +65,7 @@ void watchdog_init() {
|
||||
SERIAL_ERROR_MSG(MSG_WATCHDOG_FIRED);
|
||||
minkill(); // interrupt-safe final kill and infinite loop
|
||||
}
|
||||
#endif // WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
#endif // USE_WATCHDOG
|
||||
#endif // __AVR__
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1010,14 +1010,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1003,14 +1003,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1011,14 +1011,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1003,14 +1003,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1003,14 +1003,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1003,14 +1003,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1002,14 +1002,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1010,14 +1010,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1010,14 +1010,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1003,14 +1003,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1007,14 +1007,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1003,14 +1003,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -998,14 +998,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
//#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
//#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1019,14 +1019,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1004,14 +1004,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1005,14 +1005,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1006,14 +1006,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
@ -1007,14 +1007,17 @@
|
||||
|
||||
// @section safety
|
||||
|
||||
// The hardware watchdog should reset the microcontroller disabling all outputs,
|
||||
// in case the firmware gets stuck and doesn't do temperature regulation.
|
||||
/**
|
||||
* The watchdog hardware timer will do a reset and disable all outputs
|
||||
* if the firmware gets too overloaded to read the temperature sensors.
|
||||
*
|
||||
* If you find that watchdog reboot causes your AVR board to hang forever,
|
||||
* enable WATCHDOG_RESET_MANUAL to use a custom timer instead of WDTO.
|
||||
* NOTE: This method is less reliable as it can only catch hangups while
|
||||
* interrupts are enabled.
|
||||
*/
|
||||
#define USE_WATCHDOG
|
||||
|
||||
#if ENABLED(USE_WATCHDOG)
|
||||
// If you have a watchdog reboot in an ArduinoMega2560 then the device will hang forever, as a watchdog reset will leave the watchdog on.
|
||||
// The "WATCHDOG_RESET_MANUAL" goes around this by not using the hardware reset.
|
||||
// However, THIS FEATURE IS UNSAFE!, as it will only work if interrupts are disabled. And the code could hang in an interrupt routine with interrupts disabled.
|
||||
//#define WATCHDOG_RESET_MANUAL
|
||||
#endif
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user