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. My concern is that, if I get a new chip with boot loader version 1.63 (newest) and I use philips boot loader (address, data, clock) do I have to update the philips boot loader with the clock? In other words, why the clock variable is needed twice? One, inside the boot loader and second passing it through code? Gus --- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> wrote: > At 02:38 PM 11/18/04 +0000, you wrote: > >passing the clock speed in my code should be enough. I don't want to > >re-do thier job! Or they program the chips for me before they ship. > > I'm confused. Are you complaining about loading an updated boot program or > about telling the micro what the clock speed is when it has to program flash? > > If it's updating the boot program, check with Philips (and the errata?) and > find out what date codes you have to avoid and make it part of your > purchase spec. > > The clock speed you are going to need no matter what part of the flash you > are updating (it's not getting burned into the flash after all). > > 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
Message
Re: FLASH errata (bigining to hate LPC)
2004-11-19 by Gus
Attachments
- No local attachments were found for this message.