Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Compatibility

2004-12-16 by onestone

Hi Kris, I'm not even sure the ARM is what I want. It seems underdone - 
overkill if you see what I mean. Not as bad as some other ARM devices, 
but still too much of some things and not enough of others.

The smallest part has 8k RAM, and 32k flash IIRC. Even the tiniest parts 
have more comms interfaces than NASA, But you have to get to really big 
parts to get an ADC, and even then it's only 10 bits. To me it's XA'ish. 
  A good idea done badly. Philips rationale for low res ADC is that on 
chip noise makes anything more useless. Its odd that most other vendors 
don't have problems here, By the time I get an ADC I've got 2 UARTs, 2 
SPI's IIC, a CAN of worms, and who knows what other comms interfaces 
eating up the silicon. I don't want comms. I want to process sensor 
data. maybe 1 UART would be fine. An SPUI or IIC as well. Sure it's 32 
bit, that doesn't mean it has to be a mammoth. The only reason I'm 
looking at the ARM is it's flash base and higher execution speeds. 
Couple that with 32 bit processing (which I could live without) for fast 
calcs. It also is quite low current for what it can do. So I don't see 
it as anything more than an 8 bitter that has faster bigger number 
crunching. Every one of the top micro suppliers, in terms of volume, 
makes a large part of their market through small devices, low pin count. 
basically that's what I want. a 20 pin device that is damned fast, and 
which eats numbers, without sucking the sort of juice that a DSP does. 
So I'd be happy with 8K of flash, 2k of RAM, 4 A/D channels at 12 bits 
or better, 8 capture compares, 1 UART, 1 SPI/IIC. 60MHz, slower I/O is 
fine. I just want the built in multiplier. Philips don't even come close 
on their road map.

So, although I'm having a look I don't see much of a future in it for 
me. There are better, lower cost options on the horizon, that approach 
the same processing speeds, at lower currents, with a more rational (for 
me) peripheral/memory mix.

Al

microbit wrote:

> Hey Al,
> 
> Nice to meet here :-)
> The J-link outputs onto the standard 20 pin JTAG, and should just
> drop into the 20 pin JTAG on MCB2100.
> 
> -- Kris
> 
>  > Can anyone tell me if the J-Link unit that comes with the IAR tools is
>  > compatible with the MCB2100 board from Keil, please.
>  >
>  > Cheers
>  >
>  > Al
> 
> 
> Yahoo! Groups Sponsor
> ADVERTISEMENT
> <http://us.ard.yahoo.com/SIG=129i2n2qk/M=295196.4901138.6071305.3001176/D=groups/S=1706554205:HM/EXP=1103239419/A=2128215/R=0/SIG=10se96mf6/*http://companion.yahoo.com>
> 
> 
> ------------------------------------------------------------------------
> Yahoo! Groups Links
> 
>     * To visit your group on the web, go to:
>       http://groups.yahoo.com/group/lpc2000/
>        
>     * To unsubscribe from this group, send an email to:
>       lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     * Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>. 
> 
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.