Archives
-
Watchdog in ATmega1281V
hello i am trying to use the watchdog in the interrupt mode only to wake up the ATmega1281V . It’s work but only with a delay fixe at 15ms . I have trying to modifie the watchdog prescaler by the bits WDP3,WDP2,WDP1, WDP0 but there are no modification about the time .
I use AVR Studio 4 and write in C .
Thanks for your help .
frederic
Related Forum Messages
- Re: How does this C segment work?
- Mega1281v weird problem
- ATmega168 watchdog too fast
- Write our own Watchdog function..?
- Cant STOP Watchdog
- Watchdog Timer and Sleep Modes
- Stellaris Watchdog
- Using the watchdog to wake up from sleep
- WDT and Sleep Modes
- ATMega168 Watchdog Interrupt Timing
- Watchdog problem with too much initialized data
- Watchdog lockup
- Simple watchdog set-up query
- DFU upgrade via the boot loader and watchdog
- AT91-9263 Watchdog behaviour in NOWAYOUT mode
- PIC18F26K22 and sleep mode
- Does the built in Watchdog work
- AT91SAM9263– watchdog enabling
- 68332 Watchdog problem
- Enabling Watchdog in AT91Sam9
The WDTCSR is the WatchDog Timer Control Register. Each of it's eight named bits means something different. WDE is the WatchDog Enable bit, and WDP0, WDP1, WDP2 and WDP3 are the WatchDog Prescale bits. They are used to select (effectively) the time-out on the WatchDog. The combination of WDP1 and WDP0 indicate that the timeout should be about half a second.Hey. Im using two stk500, two stk501 and two RZ502 for wireless transmission. When I got the two RZ502 radios i also got two ATmega1281V. My system have worked fine until now. I suddenly got problems connecting to one of the ATmega1281V, so i guess i must have ruined it somehow. So i got two new ATmega1281V. But now i have another problem: At the orginal ATMega1281V, which i got when i bought RZ502, it says on the package: ATmega1281V 8AU 0635. The new one I got says: ATmega1281V 8AU 0632. I inserted the new mcu's, and tried AVR2001 appl. ...Hi, for testing the watchdog I setup an ATmega168 (straight from the shop, no fuses changed) on a breadboard with an LED attached to pin PC5. For the test I used the following sniplet to toggle the pin everytime the watchdog fires which I set to 8 seconds: Code: Select all #include ltavr/interrupt.hgt #include ltavr/io.hgt int main(void) { DDRC |= _BV(PC5); // enable toggle LED sei(); ...Hi, if my understanding of Watchdog is correct, in normal operation mode, if WDT is not clear, it will reset the PIC. In sleep mode, if WDT is not cleared, it will wake up the PIC from sleep. If that is the case, then if we use WDT to reset the PIC if it hang, we can't cause the PIC to sleep for a very long time (hours) because the WDT will time out very fast which will wakeup the PIC. Just wondering, lets say I want the PIC to reset itself (if it hangs) but only wake up the PIC by ...Im using a m1284. START Watchdog is working but once startet, the watchdog cant be stopped. I tried STOP Watchdog.... The sequence: Clear_Watchdog: 'this sub toggles the watchdog into and out of interrupt / reset mode 'this ensures that no matter what mode the watchdog might have been in previously... 'it will be turned off completely CLI 'disable global interrupts WDR 'reset watchdog timer IN R16, MCUSR 'get MCUSR ANDI R16, $F7 'clear the watchdog reset bit in the status reg !OUT MCUSR, R16 'store MCUSR LDS R16, WDTCSR 'get current watchdog setting LDI R17, $58 'load int/res mode value ...Reading over the watchdog timer section of the UM for the LPC17xx family it states - "Once the WDEN and/or WDRESET bits are set they can not be cleared by software. Both flags are cleared by an external reset or a Watchdog timer underflow. [page 568 - CH28 section 4.1]". Since instructions are not executed during Sleep - how do you feed / kick / service the watchdog? I thought that by using the PCLK this would be an issue since the PCLK should not be running during Sleep, consequently not decrementing the counter but this is not ...Hello, In all of my past experiences with a watchdog timer, the behavioral model has been the following: * Configure the watchdog to certain timeout period. * Call a function to reset the watchdog more frequently than the timeout periond. * If the watchdog is not reset before the timeout period, the processor is reset. I would like to use the watchdog on my LM3S8962. But when I look at the Stellarisware watchdog example, I see that the ampquot;resettingampquot; of the watchdog timer is done in an ISR. This does not seem like a good design ...Hey, I'm trying to make a timer thingie that basically just displays the elapsed time on an LCD. I want to put the CPU to sleep every second (or every 500ms) and just wake up from sleep to refresh the LCD with the current time (need to have timer0 running so I can't do a full power-down, just power-save afaik). The documentation on the watchdog and sleep seem surprisingly sparce and I'm having trouble setting it up. Currently I'm doing something like this (just showing the bits related to sleep and watchdog): Code: #include ltavr/wdt.hgt #include ltavr/sleep.hgt #include ltavr/interrupt.hgt void setup() { ...Reading over the watchdog timer section of the UM for the LPC17xx family it states - "Once the WDEN and/or WDRESET bits are set they can not be cleared by software. Both flags are cleared by an external reset or a Watchdog timer underflow. [page 568 - CH28 section 4.1]". Since instructions are not executed during Sleep - how do you feed / kick / service the watchdog? I thought that by using the PCLK this would be an issue since the PCLK should not be running during Sleep, consequently not decrementing the counter but this is not ...To put the finishing touches on a project I'm working on, I need to execute a function once per second (it doesn't have to be perfect, but the closer the better). I have all 3 timers in use (timer0 firing an interrupt, timer1 counting on T1, timer2 generating hardware PWM) and my main function is waiting for serial port commands. I originally wanted to use timer2 to generate an interrupt and then do software counting to get a 1Hz loop, but just enabling the timer2 interrupts while in PWM mode killed the PWM. The ISR for timer0 is already fairly ...Has anyone ever seen, on the mega328, problems with the watchdog if using a lot of of initialized (zero or non-zero) global and/or static data? I've found that if I exceed approximately 1300 bytes, and the watchdog kicks in (for example, when resetting the device via software), that the program goes into a funky state, where it stops running and doesn't reset properly (hard to figure out exactly what its doing as debugger loses contact). This problem does not, however, appear if the data is unitialized. I'm guessing that this is because the intialized data adds some delay to startup, ...Hi. Today I burned 5 hours on a strange problem. I have solved it now but I like to chare it and also I have a question. Set up: ATmega88 mkII debugger through debugWire Symptom: The hardware looses contact with the emulator in the beginning of the code. A LED on the hardware that is controlled by the MCU starts to blink rapidly. Usually but not always this happend at the first Delay. The Delay uses Sleep mode. Observations: The Watchdog is enabled. Why, I have had it enabled in this code in the past but not know. And this ...Hello all, I am using an ATMEGA 88pa controller at 8Mhz clock internal frequency. I am trying to use the watchdog in interrupt mode to toggle an LED. I was reading the datasheet where I came across this statement under the WDIE enable bit section in WDTCSR register: Quote: When this bit is written to one and the I-bit in the Status Register is set, the Watchdog Interrupt is enabled. If WDE is cleared in combination with this setting, the Watchdog Timer is in Interrupt Mode, and the corresponding interrupt is executed if time-out in the Watchdog Timer occurs. Now to ...Hi all. First of all, we are using a LM3S9B90 Rev. C3 and StellarisWare rev. 6852. Our application is using a watchdog, which is working fine. However, whenever I enter DFU mode (using the USB capable boot loader), this is done by calling USBDDFUUpdateBegin(), and the device enters DFU mode without being reset. This causes an issue, as the watchdog is not disabled, and will, when it counts down, reset the MCU. Once enabled, there is no possibility to disable the watchdog, and issuing WatchdogResetDisable(WATCHDOG0_BASE) causes an error. How can we prevent the watchdog from resetting the MCU while in ...Hello, I'm using the 9263 watchdog and I have seen that when used with the NOWAYOUT option, the watchdog will not be refreshed by the driver even before /dev/watchdog is opened. http://www.mjmwired.net/kernel/Documentation/watchdog/watchdog-api.txt seems to imply that NOWAYOUT should only apply after /dev/watchdog has been opened at least once. Anyone know if this behaviour is intentional? Or is it a bug? It is currently a headache for me because my systems may be slow to start up if the flash is too fragmented and the WD may be triggered simply because the userspace daemon takes too long to start. Regards DavidI'm using the PCWHD V4.132 compiler. I have an application I would like to run on a PIC18F26K22 platform that normally uses the internal oscillator at 4MHz and also uses the sleep mode. I want the watchdog timer and an external interrupt to be able to wake the platform from sleep. I planned the watchdog to wake at the longest period (WDT32768 postscaler for a wakeup period of about 2.18 minutes) with the external interrupt (EXT0) waking immediately. I got the baseline program working with the internal oscillator at 4MHz successfully. I used the #FUSES INTRC_IO for the internal oscillator. ...I am using Mega 2560 and would like to use the watchdog. In an old thread I read that the inbuilt watchdog does not work with Arduino bootloader. Does this mean that built in watchdog cant be used in Arduino projects. Is this true even today? I can build a HW watchdog, but if there exists already one, why bother.Hi, Iam using at91sam9263 with bootstrap and uboot in dataflash and linux kernel and rootfs in nand flash. whenever i load the driver at91sam9_wdt.ko it says that watchdog is already initialised. I came to know that in bootstrap is disabled by default. at91sam9263ek.c file hw_init /* Disable watchdog */ writel(AT91C_WDTC_WDRSTT,AT91C_BASE_WDTC + WDTC_WDCR); i commented this line so that i can enable the watchdog at the later time. but by default watchdog is enabled and resets the processor every 16 seconds. also we can write to the watchdog mode register only once. how to disable the watchdog until kernel boots up ...There are two registers involved with the Software Watchdog (see the SIM book, pages 3-7 through 3-9 and pages 3-12 through 3-13) 1. SYPCR - System Protection Control Register On power up, we write 0xc0 to this register. This sets the Software Watchdog Enable bit, SWE. This also enables the clock Prescaler by 512, SWP and SWT bits. The ratio selected, 2^18 is divided by the external system crystal frequency, 32768, to obtain the watchdog timeout in seconds, 8. I have fiddled around with the HME, BME, and BMT bits, but it made no difference. 2. SWSR - Software Service Register This register is written to about every sixth of a ...Hi I'm having more problems I expected enabling the watchdog in my developper kit at91sam9g20-ek board. Using menuconfig I've compiled the watchdog driver correctly, but when booting the linux kernel, I obtain this: AT91SAM9 Watchdog: sorry, watchdog is disabled at91_wdt: probe of at91_wdt failed with error -5 Viewing the watchdog driver code I guess my problem is my watchdog is not enabled, it is? So, how can I do to enable the watchdog when booting? Another question: after loading the watchdog driver, I must refresh continuously the driver to avoid reset? In other words: the watchog is started when is enabled? Thanks you in advance Regards, ardoster