Yes, with LPC you can tell the source of the startup, but in this case the startup is hardware-originated, so I am pretty sure it is hardware. You suggest that the processor doesn't clear the proper bits for the bootloader to tell? Guille --- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@...> wrote: > > At 10:23 AM 2/7/06 +0000, Guillermo Prandi wrote: > > > Any chance you've triggered a watchdog or some such? > > > >Well, yes... the program might have triggered the watchdog but... why > >should it matter after the reset pin being low for half a second? > > Truthfully, I don't know. I only raise the possibility because the User > Manual indicates there is an internal flag set by the watchdog so that if > it is the source of the interrupt the ISP pin is ignored. If that flag is > not cleared somehow then any subsequent reset could also ignore the > pin. Off hand I wouldn't expect the length of the reset pulse to make any > difference on whether it entered ISP mode or not. > > If you have an extra pin I'd set it on startup to indicate the startup > source. I seem to remember you can tell that on startup, I hope I'm not > confusing the LPC with a different processor. > > Robert > > " 'Freedom' has no meaning of itself. There are always restrictions, be > they legal, genetic, or physical. If you don't believe me, try to chew a > radio signal. " -- Kelvin Throop, III > http://www.aeolusdevelopment.com/ >
Message
Re: Fwd: Bootloader not always invoked after reset with P0.14 low
2006-02-07 by Guillermo Prandi
Attachments
- No local attachments were found for this message.