Lpc2000

Since your traffic is mostly one way it would be very easy to implement 
a bit-banged serial I/O. This can driven off a timer interrupt or if it 
doesn't matter too much then a simple polled routine. If you only needed 
to transmit then you can select a very high baud rate which would then 
take up less CPU cycles. The timer interrupt per bit is another viable 
alternative which is very easy to implement also.

Bit-banged serial I/O typically only needs a 100 bytes or so of code 
space to implement.

I would certainly steer clear of hanging dedicated UARTs whether 
parallel or SPI off the micro as they do tend to be rather expensive. 
Why it's cheaper to use a micro as a Uart but you still need code to 
talk to it anyway.

EXTRA SERIAL CHANNEL SELECTION GUIDE
------------------------------------------
EXTERNAL UART + CODE + INTERFACE    = $$$
EXTERNAL SPI UART + CODE            = $$$
EXTERNAL MICRO + CODE               = $
BIT-BANGED I/O + CODE               = free


my2cents
Peter Jakacki


ggindele wrote:

>I'll need a 3rd serial port to debug the application, just to dump out
>logs. Maybe SPI? But then I would need a SPI-RS232 converter. 
>Any recommendation?
>
>Gabe
>
>
>
>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>
>
>
>  
>