[En-Nut-Discussion] Watchdog/Idle thread issues again

[Alexander Baranov]

If it is NutOS independent you have to set it up independently of NutOS:

void ExtWD_reset(void)
{
 PORTD = PORTD&~(1<<WDT_OUT);
 _NOP();
 _NOP();
 _NOP();
 _NOP();
 _NOP();
 _NOP();
 _NOP();
 _NOP();
 _NOP();
 _NOP();
 PORTD = PORTD | (1<<WDT_OUT);
 //sbi(PORTD,WDT_OUT);
}

SIGNAL(SIG_OUTPUT_COMPARE2)
{

 if( (time_to_reset >0)&& (bReboot!=0xAA ) )
 {
  time_to_reset--;
  ExtWD_reset();
 }
 wdt_reset();

}

But I just thought that I still use version 3.4.1, while the newer ones may
have new timep features.
Regards, Alex
----- Original Message ----- 
From: "Ulrich Hertlein" <ulrich.hertlein at artcom.de>
To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
Sent: Wednesday, December 07, 2005 12:43 PM
Subject: Re: [En-Nut-Discussion] Watchdog/Idle thread issues again


> Alexander Baranov wrote:
> > Interrupt service program is fully yours if the interrupt is not used
> > somewhere in NutOS.
>
> Sorry, what I meant is, is it OK to use NutTimerStart()?
>
> If not how can I setup a Nut/OS independent timer for these purposes?
>
> /ulrich
>
> -- 
> Ulrich Hertlein | Software Development
>
> ART+COM AG
> Kleiststr. 23-26 | 10787 Berlin | Germany
>
> phone: +49.30.21001-433
> fax: +49.30.21001-555
> http://www.artcom.de
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>
>