Lpc2000

I await further information with interest, though it would be unlikely 
we'd be interested in using it unless it was open source. Our 
production programming is integrated into an automated test system. 
After programming, the device is reset (into normal mode), the POST 
information retrieved and further self-tests run under the command of 
the production test software. The result is then displayed (a simple 
good/bad status for the operator) and details recorded with the unit 
serial number to a back-end database. It's all fully automated and 
integrated. A fairly standard approach too, I would imagine (I'm no 
production expert). 

By the way, the interface to the Philips built-in boot loader is the 
same regardless of CPU variant (unless you're talking about non-LPC2xxx 
CPUs?), or the crystal speed. 

As I say, I await further information with interest: it's always good 
to see alternative approaches and ideas.

Brendan

--- In lpc2000@yahoogroups.com, "jayasooriah" <jayasooriah@...> wrote:
>
> --- In lpc2000@yahoogroups.com, "brendanmurphy37"
> <brendanmurphy37@> wrote:
> 
> > I misunderstood: I thought you were saying ...
> 
> Have a play with BSDC and you may understand it better.
> 
> When I find time I will explin more in my page on how it does what it
> does, and how the full version of is used on a production environment
> and handles target boards with mixed CPU variants and crystal speeds.
> 
> Jaya
>