>Given that it's true though I fall back to what I said earlier about having >to take into account startup conditions when you design a system. That's >why you have to read both the data sheet and user manual before selecting a >chip. Also errata and user experiences. > > > Yeah, and one or two working prototypes certainly help. heh. I've been burned in the past by deploying a design, only to find out about 6 years later that an expansion path to a larger EPROM was closed. I'd made a mistake on the banking logic, actually gave drafting the wrong schematic and never caught it until I needed it. I just assUmed that since the proto worked that the production board was ok. Doh! TomW -- Tom Walsh - WN3L - Embedded Systems Consultant http://openhardware.net, http://cyberiansoftware.com "Windows? No thanks, I have work to do..." ----------------------------------------------------
Message
Re: [lpc2000] Re: re : LPC hardware+software problems (was: UART0 interrupts without FIFOs)
2006-04-30 by Tom Walsh