Lpc2000

At 01:29 PM 11/18/04 +0000, you wrote:
>but you pass the clock freq. to the IAP at run time!!! why on earth
>philips wants you to program thier boot loader  then program your
>boot loader then program your firmware!!!!!!!!! Can you imagine the
>cost of doing this for 1000 chips?

Cost I would expect less than twice the cost of programming the application 
itself (which obviously must be done anyway).  There is a fixed overhead 
(time and fixtures), plus download time.  Download time will vary with 
program size and if you have a reasonably large application it's download 
time will easily exceed that for the boot loader by several times.

It seems to me you have one too many programming steps in there.  That is a 
separate issue from needing to know the clock frequency.

In any case how else would you suggest the timing information get passed to 
the flash programming routines?  You (or your program) are the only source 
that knows this information.

>My point is, this is done WRONG and Philips better fix it.

I expect the fix for the bootloader will be incorporated (if it hasn't been 
already on the production line) but the need for the clock frequency (or 
something similar) is likely to remain.

You could ask Philips how long it will take to see updated bootloaders in 
production.  It is possible they are just working their way through the 
supply chain.  As a note on how lengthy that chain can be I just bought 
some new SMT resistors from Digikey and noted as I was verifying the order 
that they had a 2000 date code.

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