--- In lpc2000@yahoogroups.com, "brendanmurphy37" <brendanmurphy37@...> wrote: > I think you should read again what I actually said, which > was: "...but see the OKI ARM7 MCUs for a very similar device that > handles booting and programming differently". How do you equate the > word "differently" to "they are alike"? I do not. I equate "very similar devices" above to mean "alike". To refresh your memory, I started this thread with the statement: > I think the kind (of) hardware *and* software (in the supplied > Bootloader) problems on the LPC Family is without precedent. The differences are significant. Unlike the LPC, both OKI and SAM have: JEDEC compliant SDP flash; both watchdog *and* analog inputs can be used; cannot be locked out by corrupt software; and so on. One has to try come up with what is good about LPCs to appreciate this sentiment. > To my way of thinking it is preferable to have a watchdog reset the > system to a known state, rather than leave it in some unknown state: > who knows what state the peripherals are in when the system's > software (probable cause of the watchdog reset) may have done > anything in the lead up to the watchdog being triggered? This thinking goes against the "keep options open" rule of good system design. The user (like you) can set everything back to the reset state if they so wished. In the LPC, it does it for you in a way that watchdog and analog inputs are mutually exclusive resources. This cannot be considered a good design. > By the way, I've nothing further too add to this topic: it's already > lost its original usefulness (a warning to be careful of how the > boot-loader select pin can be inadvertantly asserted, and practical > suggestions of how to avoid the problem). Looks like you have not noticed the change in thread title ... Jaya
Message
Re: LPC hardware+software problems
2006-04-29 by jayasooriah
Attachments
- No local attachments were found for this message.