Compiler/TMS320F28379D: watchdog

Ashish,

Not very clear on the issue. WDCR is control register and bit 2-0 are the prescaler to divider the clock which increments the WD counter. If you are keeping this value less then your WD should issue reset even earlier. Can you post the snapshot of your code and let us know where it's getting stuck?

Vivek Singh

THIIS IS MY MAIN FILE.

#include "F28x_Project.h"

#define BLINKY_LED1 31 //31 is Blue led.

void InitWatchdog(void);

Uint16 loopcount = 0;

void main(void)
{
InitSysCtrl();
InitWatchdog();
GPIO_SetupPinMux(BLINKY_LED1, GPIO_MUX_CPU1, 0);
GPIO_SetupPinOptions(BLINKY_LED1, GPIO_OUTPUT, GPIO_PUSHPULL);
GPIO_WritePin(BLINKY_LED1,1);
DELAY_US(1000*500);
GPIO_WritePin(BLINKY_LED1,0);
DELAY_US(1000*500);
while(1)
{
loopcount++;
}
}

THIS IS MY WATCHDOG CONFIGURATION CODE.

#include "F2837xD_device.h"

void ServiceDog(void);

void InitWatchdog(void)

{
asm(" EALLOW");
WdRegs.SCSR.all = 0x0000;
asm(" EDIS");
ServiceDog();
asm(" EALLOW");
WdRegs.WDCR.all = 0x002F;                     
WdRegs.WDWCR.all = 0x0000;
asm(" EDIS");
}

HERE IF I KEEP DELAY TIME OF 1500 ms THEN CONTROL GETS STUCK IN FIRST DELAY LOOP IN MAIN FILE.BUT IF I KEEP DELAY 500 ms THEN THIS WORKS FINE LIKE "IT IS TOGGLING LED ONCE PER RESET."

Ashish,

Could it be that when your loop is bigger (or WD prescaler value is low) then WD count experes early and code execution does not reach to "GPIO_WritePin(BLINKY_LED1,0);" and this pin has external pull or floating value is seen as '1' by LED)hence you don't see LED toggling ?

Regards,
Vivek Singh

Hello Vivek,
This is the issue only. But does it means that i cannot take a delay of more than 839.04 ms (this is maximum watchdog timeout period)
How can i take a delay of more time than watchdog timeout period ,do i need to service watchdog inside the delay loop or do i need to disable the timer before going into the delay loop ?