Archives
-
Problem with watchdog
Greetings.
I’m working with the RCM5700 module.
I need to use the hardware watchdog timer.
Supposedly, the watchdog is always enabled, but I never use the hitwd function to restart it, and my device never restarted.
Now. I use the Enable_HW_WDT function to enable the watchdog, but my hardware never restarted.
Is there anything I forgot to configure?
Please help me.
Thanks
Related Forum Messages
- AVR Built in WatchDog Timer Reliability
- Watchdog Timer of ADUC842
- Problem using Watchdog timer
- Stellaris Watchdog
- Watchdog lockup
- Enabling Watchdog in AT91Sam9
- Watchdog – ATMEGA16A
- no watchdog driver support
- Watchdog: not able to suspend Linux on at91sam9263
- AT91SAM9263– watchdog enabling
- Watchdog timer not running
- Watchdog reset using C32 v2.00 compiler
- WatchDog and ADC conflict
- Watchdog relation and interrupt 0
- DFU upgrade via the boot loader and watchdog
- 18F8277 WatchDog disable kills timer0?
- Using watchdog as a watchdog
- Watchdog, strange behavior
- LastResetCause?
- How to use Watchdog with at91sam9263 and angstrom linux?
Hi all, I am developing an application for Elevator Control, and I want a reliable WatchDog timer, I had a bad experiance when I was working with PIC mircocontroller that on power up the PIC didnt make self reset and also the watchdog timer didnt reset the PIC even the WatchDog was Enabled by Fuse(not by the software), my current design is using ATMEGA8, I am afraid this problem may occar with the ATMEGA8, so I made a design for a hardware WatchDog timer, but this will take more area on the PCB, so I need your advice, can I ...Dear sir, I am using ADUC842 for my design. I want to set watchdog timer of 2 sec for any errorneous condition. In my main function, i have enabled all interrupts already... I need to configure watchdog timer. But before that i should disable all the interrupts,set the watchdog timer and again enable the interrupts. since i have enabled all interrupts,i cant configure watchdog timer in the main function. where should i configure the watchdog timer ? pls help. Regards, Mayuri GI'm having a problem utilizing the watchdog timer. I've enabled the GHI watchdog time, but purposely did not call the reset function to see if it would work but the ChipworkX never restarted. See code below I used to enable and set the watchdog timeout. uint wdTimeout = 5000; GHIElectronics.NETMF.Hardware.LowLevel.Watchdog.Enable(wdTimeout); I then ran it in debug mode in Visual Studio and got the following error: A first chance exception of type 'System.InvalidOperationException' occurred in GHIElectronics.NETMF.Hardware.dll An unhandled exception of type 'System.InvalidOperationException' occurred in GHIElectronics.NETMF.Hardware.dll If I then stop debugging and reset the device (without debugging), the program seems to start up fine. However the watchdog timer never ...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 ...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 ...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, ardosterHello, I have a couple of questions about how to deal with watchdog. 1- I need to induce a reset in the Atmega16A. I have programmed the usart to send/receive data from the PC. If I receive a reset message the device should be restarted. I have read that the best option is to provoke a watchdog reset. So... please correct me if I am wrong. Code: #include ltavr/wdt.hgt main () { //enable the watchdog wdt_enable(WDTO_15MS) .... } Inside other functions that can take longer time ...Hi, I'm trying to get the watchdog driver to run in my kernel configuration but it's not there. Help in menconfig for the watchdog device driver is quite clear. I have enabled these 3 options: CONFIG_WATCHDOG=y CONFIG_WATCHDOG_NOWAYOUT=y CONFIG_AT91SAM9X_WATCHDOG=y Evidently, based on the above, I should be able to see this string in my bootup output at some point if the driver is there: "AT91 Watchdog Timer enabled" But I don't!! Module support is turned off. Could there be another conflicting option that prevents support for the watchdog? The reason why I ask is that I have observed the above bootup message claiming support for the the watchdog driver ...Hello, If I enable the watchdog in the bootstrap, then I can't suspend linux because there's no way to kick the watchdog if I do that. Furthermore, I can't disable the watchdog as it can be done with the at91rm9200. I have tried to configure the watchdog so that it disables itself when the processor is in idle state, but this way the watchdog never resets the processor while working in linux. What can I do? Thanks in advanceHi, 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 ...Hi all, i'm quite new with AT91. Hope can get helps from you all... Currently I'm using AT91SAM7S256 for my project... and planning to use the watchdog to reset the system when the software hanged. I had went through the database search, and did the same things.. but doesnt working.. As mentioned in datasheet, the watchdog is using slow clock at 32.768kHz. Would like to double confirm whether I need to set any clocks in order to get the slow clock run at 32.768kHz as needed for watchdog. If yes, what is the sequence to configure the clock properly? Below is my code. Does the watchdog ...Compiling an existing PIC32 project using the v2.00 C compiler produces a continual watchdog reset. This problem does not appear using the previous v1.12 compiler. Changing the watchdog postscaler value (up to 1048 seconds) has no effect. The watchdog reset occurs almost immediately after startup, definitely not enough time for the timer to expire. Disabling the watchdog allows the code to run as expected. There was a change to the startup code in v2.00, but I am not using any custom startup code to my knowledge. Could there be a problem with the timer used by the watchdog not being ...Hello, 1)I have coded PIC16F676 for one system. Before using WatchDog, the ADC code in my program works appropriately. I am taking analog signal on Port A - 0 pin (AN0). But after enabling Watchdog through Configuration bits, ADC working is erratic. Code structure is below: This is with watchdog CONFIG bit enabled 1. Init registers,ports etc 2. Call ADC routine 3. ----- 2)If I disable the Watchdog CONFIG bit and then if I assign prescalar to Watchdog through the code given in datasheet(initially for 30 secs I am using prescalar for Timer), then Watchdog is not active at all. I ...Hello, I have a problem when i disable the watchdog // WDTCN = 0x0DE; // WDTCN = 0x0AD; at the begining of the main. I put a breakpoint at the external interrupt 0. It will never go in and stop at the breakpoint. When i stop the program. I will stay inside the while loop and I checked the interrupt peripheral, it seems that interrupt 0 has been requested. This problem will not happen when I enable the watchdog in the begining of the main. WDTCN = 0xFF; // lock out the watchdog disable feature WDTCN = 0xA5; // enable ...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 ...New here, but not my first rodeo.. I am working on a rather complex program that uses the Watchdog timer for its obvious uses. Timer0 is also used to generate interrupts for the system clock. I need to be able to disable the Watchdog via a command from another system so that both systems can be reburned in the field. The watchdog is under software enable via the swdten bit (and this is working). When I disable the watchdog, the interrupts from timer0 also stop. I have even added code to enable timer0 immediately after resetting the swdten bit, to ...Hello everyone, I would like to use the watchdog as a watchdog, instead of as a timer. Meaning I would like to set the watchdog timer to a certain time and if I do not disable it before the time expires, it should reset the MCU. Does anyone have an example code for this? GreetingsI am working on a program for an 18LF45K22 using the CCS compiler. There is one section of the code where I go into an infinite loop with a while(1) and I want the watchdog to time out and reset the CPU. Immedaitely before the code hits the while(1) I disable global interrupts. For some reason the watchdog will never time out and reset unless I take out the disable global interrupts. The watchdog works just as expected if the global interrupts are enabled when it hits the while(1). I could find nothing in the documentation to indicate why the ...Hi all My users will have the option to reboot the device at any stage. At the moment I just make a call to: Microsoft.SPOT.Hardware.PowerState.RebootDevice(false, 100); When my application restarts it checks: GHIElectronics.NETMF.Hardware.LowLevel.Watchdog.LastResetCause and then writes to a log file to indicate why the application restarted. No I have tried calling RebootDevice with the soft boot param set to true and false, but when the device restarts it is always getting a LastResetCause of WatchdogReset. Why when I set soft reset to false does the watchdog still see the restart as a watchdog restart, and is there a way to override the ResetCause enum? Any help ...ive been trying to get this to work. i have at91sam9263 with bootstrap and uboot in dataflash and linux kernel and rootfs in nand. i have no idea how to get it to work. bootup says at91sam9_wdt: invalid timeout (must be between 1 and 16) i studied this and found out that watchdog in bootstrap is disabled by default. at91sam9263ek.c file hw_init /* Disable watchdog */ writel(AT91C_WDTC_WDRSTT,AT91C_BASE_WDTC + WDTC_WDCR); i changed this to writel(0xFFF | (0xFFF ltlt 16) | AT91C_WDTC_WDRSTEN | AT91C_WDTC_WDDBGHLT | AT91_WDTC_WDIDLEHLT,AT91C_BASE_WDTC + WDTC_WDCR); now the watchdog seems to be functioning because the device resets itself every 16 ...