2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler

I'd like to have some control on watchdog events, so I can record some specifics and set some pin states in the ISR. Based on a configuration option, I then want to do a real reset as the WDT would normally do, or just halt.

I am not sure from the datasheet that I can do both of these things. Halting would just be a loop, and the reset should be doable as long as I can write the WDRESET inside the ISR.

One downside of using the watchdog interrupt seems to be that you are expecting valid code in the ISR. In the worst case scenario, the entire program space gets wiped out during operation. The WDT fires and jumps to valid but incorrect code, possibly causing problems.

Do these assumptions sound correct?

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



(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )