[En-Nut-Discussion] Watchdog problems with v4411 on SAM7X256-ek

[steve]

Zack,

  Thanks for that - it makes good sense.

  But, sorry to be so crap, after editing the .S file what do I have to do
  to make it work with my app?

  Thanks again.

Steve.

>Steve,
>   I got around this by modifying the code in:
>nut\arch\arm\init\crtat91sam7X256_rom.s
>
>I commented out the following code as shown:
>
>          /*
>           * The watchdog is enabled after processor reset. Disable it.
>           */
>/*
>          ldr     r1, =WDT_BASE
>          ldr     r0, =WDT_WDDIS
>          str     r0, [r1, #WDT_MR_OFF]
>*/
>
>
>    Let me know if this helps.
>
>    Thanks!
>     Zack
>
>
>
>At 01:24 PM 8/28/2008, you wrote:
> >Hi,
> >
> >   I'm trying:
> >
> >     printf("Starting watchdog\n");
> >     NutWatchDogStart(2000, 0);
> >     for(;;);
> >
> >   under NutOS v4411 running on an AT91SAM7X256-EK.  The processor
> > never resets.
> >   Is this a known problem, am I doing something wrong, any ideas?
> >
> >   Thanks for your help.
> >
> >Best Regards,
> >Steve.
> >
> >_______________________________________________
> >http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
>
>
>------------------------------
>
>Message: 7
>Date: Fri, 29 Aug 2008 09:53:49 +0200
>From: Harald Kipp <harald.kipp at egnite.de>
>Subject: Re: [En-Nut-Discussion] Watchdog problems with v4411 on
>         SAM7X256-ek
>To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
>Message-ID: <48B7AB0D.2060804 at egnite.de>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>ennut at thezachariasgroup.com wrote:
> > I commented out the following code as shown:
> >
> >          /*
> >           * The watchdog is enabled after processor reset. Disable it.
> >           */
> > /*
> >          ldr     r1, =WDT_BASE
> >          ldr     r0, =WDT_WDDIS
> >          str     r0, [r1, #WDT_MR_OFF]
> > */
>
>Arrrgh! That was too obvious. I received several requests about non
>working watchdogs on the SAM, but never had enough time to evaluate this.
>
>Indeed the problem is, that the watchdog on some CPUs is activated on
>reset. If disabled, it can't be enabled again. IMHO, this paranoid
>design is "krank" (http://dict.leo.org/).
>
>Harald
>
>
>------------------------------
>
>Message: 8
>Date: Fri, 29 Aug 2008 10:07:19 +0200
>From: Harald Kipp <harald.kipp at egnite.de>
>Subject: Re: [En-Nut-Discussion] Change Ethernut repository to SVN
>To: "Ethernut User Chat (English)" <en-nut-discussion at egnite.de>
>Cc: btnode Development <btnode-development at list.ee.ethz.ch>
>Message-ID: <48B7AE37.1010702 at egnite.de>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Thiago,
>
>Thiago A. Corr?a wrote:
> >
> > Actually, since svn commits are "atomic", a set of changed files all
> > share the same revision number and thru svn log one can figure out
> > which files chnaged in each checkin. This makes specifying the files
> > changed in the Changelog a bit less important.
>
>Agreed.
>
> > Also, makes it quite easier to do branch and merge operations.
>
>Dito.
>
> > server.  Later we moved on to berlios, but it was just because of
> > bandwidth issues at that time.
>
>Sourceforge's bandwidth, performance and refresh periods are quite well
>these days. We only have to accept, that Sourceforge is not willing to
>let us move the complete project history to another service.
>
>IMHO, the recent commercialization of the site (banner ads etc.) is not
>really annoying. But it is out of our control and may change when
>financial pressure increases.
>
>Harald
>
>
>
>
>
>------------------------------
>
>_______________________________________________
>http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
>
>End of En-Nut-Discussion Digest, Vol 58, Issue 23
>*************************************************