Lpc2000

Gus wrote:
> I guess so far no one understood my point! When you use the philips 
> bootloader from your code, you pass (address, data, clock) so far 
> everything seems fine. Now, in the philips update bootloader 
> document, there is a step telling us to enter the clock in the RAM 
> buffer before running the code.

I and I suspect everyone else here had trouble understanding what your 
actual question was amidst all the shouting about Philips making 
mistakes and the cost of reprogramming 1000 chips.

What I _think_ you are asking is "do I need to update the on-chip 
bootloader a second time if my system's clock frequency will be 
different to the one I was using when I first updated the bootloader?"

I believe the answer is no. The reason you need to set the clock 
frequency variable in the RAM buffer before executing the 
bootloader-update program from RAM is because the bootloader-update code 
needs to know what the _current_ frequency (while the bootloader update 
is taking place) is for flash timing purposes.

Note that you could speed up the process if you have to run the 
bootloader update on 1000 chips by modifying the frequency variable in 
the hex file and using a hacked version of l21isp to upload the 
bootloader-updater to ram and execute it in a single step.

-- 
------------ Alex Holden - http://www.linuxhacker.org ------------
If it doesn't work, you're not hitting it with a big enough hammer