Lpc2000

Hi Robert,

Making the flash timing parameters compile time constants will resolve this 
issue quite nicely given the we know what the crystal frequency is and 
given it is fixed for any given design.

Jaya

>Message: 14
>    Date: Wed, 22 Feb 2006 12:40:33 -0500
>    From: Robert Adsett <subscriptions@...>
>Subject: Re: Re: bootloader
>
>At 09:30 AM 2/22/2006 -0700, Steve Franks wrote:
> > > 1/  The coding of the flash programming algorithm in the boot loader
> > > unreliable because: a) it depends on wait loops rather than polling the
> > > flash controller status register; and b) it requires clock frequency 
> to be
> > > passed as a run-time argument.
> >
> >I, for one, had origonally assumed the presence of a crystal-freq in
> >the isp app was just for setting baud-rate dividers appropriately,
> >though in hindsight, it's obvious that that's needed in the device,
> >not the pc.  This news makes one very cautious, and I don't hesitate
> >to say that a bootloader requiring a human to type in the crystal freq
> >to program memory is worthy of being disparaged, in my opinion.  Which
>
>How else do you propose they determine the frequency in order to set
>internal timing dependent parameters?
>
>Robert

Send instant messages to your online friends http://au.messenger.yahoo.com