Lpc2000

Hi, Jayasooriah. Indeed the watchdog is the problem. At this stage of 
development I am only using the watchdog to provide a software reset 
function. Apparently this behavior is triggering only after using 
this function. And yes, you are right; the bit should be cleared by 
the external reset.

It looks like this behavior is 'by design' so there is no other 
workaround than switching off the unit.

Guille

--- In lpc2000@yahoogroups.com, Jayasooriah <jayasooriah@...> wrote:
>
> Hi Guile,
> 
> If you look at the user manual for WTOF bit which the boot loader 
checks, 
> it is quite clear that "external reset" will clear this bit.
> 
> Can you try without arming the watchdog to see if the problem goes 
away?
> 
> Jaya
> 
> --- In lpc2000@yahoogroups.com, "Guillermo Prandi" 
<yahoo.messenger@> wrote:
>  >
>  > My code is clearing the RISR flags at boot time by doing:
>  >
>  > #define RSIR (*((volatile unsigned char *) 0xE01FC180))
>  >
>  > RSIR = 0x0f;
>  >
>  > After that, the boards still ignores P0.14 after a watchdog 
reset.
>  > Since I cleared the watchdog reset flag, I expected the 
bootloader to
>  > invoke ISP. Is there anything else I could do from software in 
order
>  > to make the bootloader honor the P0.14 pin?
>  >
>  > Guille
>  >
>  > --- In lpc2000@yahoogroups.com, "philips_apps" <philips_apps@>
>  > wrote:
>  > >
>  > > Hello Guille,
>  > >
>  > > In case of a watchdog triggered reset, P0.14 pin is ignored by 
the
>  > > bootloader and the valid user application is executed. If 
valid user
>  > > application is not found then only isp is entered. In LPC2138 
the
>  > WDT
>  > > flag is not cleared by pin reset. POR reset clears the WDT 
flag.
>  > What
>  > > you are observing is expected behavior. I am assuming that WD 
reset
>  > > happened since you have mention it.
>  > >
>  > > Regards
>  > > Philips Apps
> 
> Send instant messages to your online friends 
http://au.messenger.yahoo.com
>