Lpc2000

0x3999 works fine.

Richard

--- In lpc2000@yahoogroups.com, "Leighton Rowe" <leightonsrowe@y...> 
wrote:
> Phillips_apps,
> 
> I'm planning to update the bootloader on the lpc2114 chip that's 
> running on a 14.7456 MHz Xtal. I only see frequency numbers 
provided 
> for 10 MHz & 12 MHz that's supposed to go in Ram Buffer location 
> 0x40000200.
> 
> What's the safest value to put for 14.7456 MHz? 
> 
> Leighton
> 
> --- In lpc2000@yahoogroups.com, "philips_apps" <philips_apps@y...> 
> wrote:
> > Hello Leighton,
> > 
> > The version of the bootloaders that do not have the improved 
timing
> > behavior is different for the LPC210x  and all other LPC2000 
family
> > members in the 64-pin or 144-pin package. 
> > 
> > For devices in the 64-pin package like yours, the updated version
> > should be V1.63 or later. So, the bootloader you have could show 
> the
> > problem, however, as mentioned in the Errata Sheet it affects up 
to
> > 10% of the devices ot in other words, 90%+ of the devices will 
> never
> > show this problem. 
> > 
> > The most critical event is an IAP call while running the device 
> with
> > max speed at hot temperature (could be 10% failure rate). The 
least
> > critical running it at 10-12 MHz room temp (you will probably 
never
> > see the issue). 
> > 
> > Look at this Errata like a patch from some big company for their
> > Exploration software. In all likelyhood the devices that did not 
> show
> > the problems in a given enviroment will continue to work fine in 
> the
> > same enviroment. A change in enviroment, speed, temperature... 
> could
> > however trigger the misbehavior. So, if you have the opportunity 
to
> > upgrade your bootloader version it is a good idea to do so, if 
not 
> and
> > your environment does not change, no sweat.
> > 
> > Hope this helps to clarify the issue. 
> > 
> > Best regards, Robert