Lpc2000

--- In lpc2000@yahoogroups.com, "philips_apps" <philips_apps@y...> 
wrote:
> Hi all,
> 
> this group has been such a great pool of help for each other and 
also 
> for us at Philips. Some of the questions trigger internal design 
> investigations, changes in documentation, slides for presentations 
> and so on. Be assured we are reading and even participating.  
> The "Philips_Apps" ID is used for "official" purposes only by 
several 
> members of our technical team.
> 
> Today I would like to pick your brains and get the top-ten charts 
of 
> most wanted features in future LPC2000 devices. I promise this will 
> have an impact on product definition planning if a large number of 
> you participate. 
> 
> By the way, some of the listed features are already in development 
> but we would like to have confirmation we are working on the right 
> things. The majority in the list however is totally open whether 
the 
> features will be implemented in the future or not, your vote 
counts. 
> Last but not least let me tell you that the price tag for these 
> options is very different, e.g. doubling the memory size is a lot 
> more expensive than adding a serial interface. 
> 
> Thank you for the great community in the group and for your help 
> planning upcoming devices. 
> 
> Looking forward to your numerous responses, Robert


Hello philips_apps,

Others have mentioned suggestions which I second:
* An RTC that actually works, i.e. can keep time while the processor 
is in power-down.
* An integrated 1.8V regulator.

And I'd like to add:
* Faster GPIO operation.  It takes way too many clocks, even with a 
pclk divider of 1.
* An integrated reset/brownout circuit.
* PWM: A way to make new PWMMRx values take effect without waiting 
for a PWMMR0 event.  The PWM outputs could then be used to generate 
arbitrary, precisely timed pulses.

Karl Olsen