Lpc2000

Ooof... seems like a stinky sticking problem. I'll better attack it 
only if it becomes a real PITA. For the moment, instructing the 
programming operator to do a power-on reset by hand is perfectly 
acceptable.

Thanks a lot.

Guille

--- In lpc2000@yahoogroups.com, Jayasooriah <jayasooriah@...> wrote:
>
> Hi Guile, I should have said "power on reset".
> 
> I removed the problem (was not keen on solving it at that time) by 
avoiding 
> use of GPIO pins that the boot loader has allocated for purposes of 
> "external boot" feature (something that is not necessary and hence 
of 
> dubious value in the context of embedded systems).
> 
> I believe there are some registers that the boot loader fiddles 
with which 
> exhibit "stuck zero" behaviour -- when one writes a zero, these 
bits stays 
> zero until power on reset event.
> 
> In the 2292 that I am now working on for POE application, I found 
that if 
> you do not re-map interrupt vectors to your own memory space, UND, 
PRE, and 
> ABT type exceptions can also cause the system to lock up in similar 
> ways.  Power on reset got me out each time this happened.
> 
> Jaya
> 
> >    Date: Tue, 07 Feb 2006 13:07:11 -0000
> >    From: "Guillermo Prandi" <yahoo.messenger@>
> >Subject: Re: Bootloader not always invoked after reset with P0.14 
low
> >
> >Hi, Jayasooriah. What do you mean by "hard reset"? If you mean 
having
> >the reset pin low, then I *am* performing a hard reset. The problem
> >shows up when I attempt to access ISP via serial port (DTR goes to
> >RESET, RTS goes to P0.14).
> >
> >Guille
> 
> Send instant messages to your online friends 
http://au.messenger.yahoo.com
>