Robert Adsett 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. > > > I'd noticed something like that as well. I played with the watchdog a little and found that it didn't work as expected. IIRC, I had to do a powerdown to get the system to run again. I didn't look further than that, as I decided this watchdog thing was going to take some serious thought. It doesn't work as a simple LTC590 monitor... Probably over-engineered. Tomw >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/ > > > > >Yahoo! Groups Links > > > > > > > > -- Tom Walsh - WN3L - Embedded Systems Consultant http://openhardware.net, http://cyberiansoftware.com "Windows? No thanks, I have work to do..." ----------------------------------------------------
Message
Re: [lpc2000] Re: Fwd: Bootloader not always invoked after reset with P0.14 low
2006-02-07 by Tom Walsh
Attachments
- No local attachments were found for this message.