Atmel family has another type of Timer to watch the program flow. We can enable the timer and if error occurs it will restart the CPU. So much we are excited, for it is hard to succeed developing absolutely perfect and error free program. The watchdog cannot help us to better programs however it can ensure that our program, if it said good-by and the \u00b5C start again. Let\u2019s write a program to set PORTB of ATmega32 from bottom to top. Let\u2019s write the program-<\/p>\n\n\n
It seems like in a continuous loop i.e. while(1) PORTB is set from bottom to top and again from bottom to top and the process continue. But if you run the program and simulate in proteus or in real life it is seen that PORTB will set from PINB7 to PINB0 and the loop terminate there. No repeat, so what happen? Completely simply, because as unsigned defined variable can never become smaller than zero. But the compiler does not give any warning or error? The program would hang itself up in here and would turn eternally in the loop. And here the watchdog comes exactly to the course. The watchdog cannot correct the program but start from beginning just like RESET. It simply gives some time to execute, if the execution hanged itself than it RESET the microcontroller and start from begin. We will discuss this in this article however the correction in the above program is replace the uint8_t x=7<\/strong> with int8_t x=7<\/strong>. <\/p>\n\n\n\n
The Watchdog contains a separate timer\/Counter, which with an internally produced clock by 1MHz with 5V one clocks, so no need for external timer. It is already calculated for every microcontroller without the effect of internal or external oscillator. Let\u2019s first see the control register and there uses<\/p>\n\n\n\n<\/figure>\n\n\n\n
You can use register from the table or the function available in the #include<avr\/wdt.h><\/strong> library. Let use both. To enable the Watchdog \u2013<\/p>\n\n\n\n
WDTCR|=(1<<WDE); or wdt_enable(WDTO_xS);<\/p>\n\n\n\n
Enable the watchdog timer, configuring it for expiry after timeout<\/code> (which is a combination of the WDP0<\/code> through WDP2<\/code> bits to write into the WDTCR<\/code> register; for those devices that have a WDTCSR<\/code> register, it uses the combination of the WDP0<\/code> through WDP3<\/code> bits). Some Timeout values and pre-defined as constants and some are listed according to the bit setting.<\/p>\n\n\n\n<\/figure>\n\n\n\n
For use the time out condition see the bits available as watchdog timer prescaler.<\/p>\n\n\n\n
To disable watchdog<\/p>\n\n\n\n
The bet can be only deleted as long as the bit WDTOE stands to 1. That means after you enable Watchdog timer the thing you need is <\/p>\n\n\n\n
WDTCR |= (1<<WDTOE) | (1<<WDE); or wdt_disable(); [use the #include<avr\/wdt.h>]<\/p>\n\n\n\n
Let\u2019s change the program which is discuss at the beginning by replacing the uint8_t with int8_t and set the watchdog timer to check our logic. If the logic is correct then the watchdog disable otherwise it reset the microcontroller. Let the process be seen by our self. In that case we set a PINB0 of ATmega8 and it is clear if the loop success. The full code as follow-<\/p>\n\n\n
Here int8_t can have both positive and negative value. So the watchdog timer disable before 2s timeout. Now your task is to check the program by replacing int8_t with uint8_t and see what happen?<\/p>\n\n\n\n
![\"\"](\"https:\/\/iotthinghub.com\/wp-content\/uploads\/2024\/06\/watchdog-timer-1024x658.jpg\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/iotthinghub.com\/wp-content\/uploads\/2024\/06\/watchdog-time-out-1024x386.jpg\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/iotthinghub.com\/wp-content\/uploads\/2024\/06\/sensor-checking-1024x477.jpg\")
<\/figure>\n\n\n\n