Lpc2000

Dave,

same people listening to all of you here, replying to the forum, 
specifying new features, writing documentation....

Will do our best to catch up and improve documentation!

Robert


--- In lpc2000@yahoogroups.com, "dave_baker_100" 
<dave_baker_100@y...> wrote:
> Excellent! A semiconductor manufacturer listening to the users and 
> then responding in a relatively quick time (taking into account 
tape 
> out times & validation). This will help Philips to stay ahead of 
the 
> competition. The only other thing I'd add is that the datasheet 
people 
> should also listen to the users in this group or even look at other 
> manufacturers datasheets to see how its done ! (checkout Silicon 
Labs 
> as an example of excellent, albeit non-ARM, datasheets)
> 
> Dave
> 
> 
> --- In lpc2000@yahoogroups.com, "philips_apps" <philips_apps@y...> 
> wrote:
> > Hi all,
> > 
> > today the LPC2148 was announced to the press. The preliminary DS 
has 
> > been posted on this group by our marketing recently. One very 
> > important improvement is the port access time. This is the first 
> > device that has the ports mapped to the local bus. This enables 4 
> > times faster toggle times. The max is now Processor clock divided 
by 
> > 4. This will not get you to 20 Mhz but 15 is as close at it will 
> ever 
> > get (without increasing the max. clock rate). 
> > 
> > May be 15 MHz is fast enough ?
> > 
> > We plan to have evaluation boards through IAR and Keil available 
> > second half of July.
> > 
> > Hope this helps, Robert
> > 
> > --- In lpc2000@yahoogroups.com, Robert Adsett 
<subscriptions@a...> 
> > wrote:
> > > At 01:01 AM 6/28/05 +0000, markevans_1 wrote:
> > > >Hi guys,
> > > >I am finding it a little tricky to calculate how fast this 
chip 
> can
> > > >actually go for my app. (Instruction cycles and MAM)
> > > >
> > > >I was wondering if anyone can tell me how fast it would 
execute 
> > this
> > > >code at 60MHz:
> > > >
> > > >Read in 16 bits from port1
> > > 
> > > That's the slow part.  Pin toggle rate is about 3.8MHz.  
Narrowest 
> > part of 
> > > that has a time of 118nS.  If you need to run any sort of 
> > handshaking slow 
> > > that down by at least 2to 3x.
> > > 
> > > See a very early thread in this forum titled "Simple test 
program 
> - 
> > is now 
> > > instruction pipeline/VPB question" about Nov/Dec 2003.
> > > 
> > > 
> > > >store in RAM
> > > >increment pointer
> > > >loop for N times
> > > >
> > > >I basically want to buffer data as fast as possible in bursts. 
> > Ideally
> > > >at 20MHz.
> > > 
> > > Not going to happen without external support.
> > > 
> > > >How much faster would it execute in RAM.
> > > 
> > > Probably not enough faster to notice. The port access time is 
> going 
> > to be 
> > > noticeable,
> > > 
> > > >Could I make it faster by using an infinite loop and using a 
> timer 
> > to
> > > >'break out' of the loop.
> > > >
> > > >Mark.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > > 
> > > " '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
> > > http://www.aeolusdevelopment.com/