Lpc2000

--- In lpc2000@yahoogroups.com, Peter Jakacki <peterjak@...> wrote:

> Your statement although allegedly quoting Philips is misleading as it 
> lacks context or reference. You know and I know, as everyone else knows 
> that the Philips flash is organized not 16 bits wide, nor 32 bits wide, 
> but 128 bits wide, and in two interleaved banks!. That is 128 bits 
> @20Mhz or whatever exact speed it is which means in most cases 32-bits 
> @80Mhz.

The reference I was referring to appears at Philips site has been
moved and I do not know where to.  Here is what was there (from a
cached site):

<quote>

Q: Why does the code run slowly from flash when Philips claims that
the chip runs with nearly zero wait states from flash?

A: On reset, the Memory Accelerator Module (MAM) is disabled but the
MAM Timing register has a reset value of 0x7, which means that 6 wait
states are inserted for every flash access. You need to set it
depending upon the frequency at which you are running. If you are
running your application below or at 20 MHz you can set this register
to 0x1, which implies no wait states

</quote>

Do a google search on '"nearly zero" 20 MHZ LPC' and this is the first
hit shoudl give you the orignal URL relating to Philips Education and
Training for LPC2000 series.

The same information also appeared in a bug report by Philips Apps in
another forum but I cannot seem to find it now.  I know I read it, and
from memory, it said 25MHz not 20MHZ as the guaranteed instruction
rate when MAM is diasbled.

It says that LPC flash is 20MHz worst case, and I know SAM is faster
at 30MHz worst case.  I do not know about OKI flash speed but I
suspect it is in similar order of magnitute.

These things only come up when you look at comparison charts, and what
I am alluding some forum members is to look beyond anecodotal evidence
or promotional material.

I must say I find the kind of request to prove each and every bit of
trivia (that I thought were reasoble) very distracting and counter
productive.

Jaya