Lpc2000

Tom,

I am absolutely certain about this, it has been verified with Philips.
Each IAP call needs to have the frequence the device is currently
running at. If the PLL is active the parameter needs to be PLL*ext. Freq. 

The "funny" part is, it works ALMOST all the time even with the wrong
frequency.

Bob

--- In lpc2000@yahoogroups.com, Tom Walsh <tom@...> wrote:
>
> lpc2100_fan wrote:
> 
> >Hi Greg,
> >
> >one thing that I have seen before that ended up with the same symptoms
> >your are describing is an IAP call with the wrong frequency. What I am
> >referring to is you boot up let's say with 14.756 MHz and do some IAP
> >calls, then you enable the PLL and still call IAP with the same 14.756
> >although now it is 59 MHz. 
> >  
> >
> 
> Is that how you read the manual?  I thought that "system clock" was 
> referring to that of the external clocking rate, not that as the PLL
clock?
> 
> Do I have to use the PLL clock rate for this?
> 
> Regards,
> 
> TomW
> 
> 
> -- 
> Tom Walsh - WN3L - Embedded Systems Consultant
> http://openhardware.net, http://cyberiansoftware.com
> "Windows? No thanks, I have work to do..."
> ----------------------------------------------------
>