"Sean Whitesell" <seanw122@vigoris.net> wrote in message
news:d122ada9.0402250641.4692e941@posting.google.com...
> I need a design suggestion on the best way to receive data through the
> UART. Buffer it, and allow the USB task to pick it up when ready.
> There is only two endpoints that the desktop application can see.
> Because of this we are using an ad-hoc application handshaking method.
>  The app will send a packet with a command that the processor sees as
> a "Query" command. If no data then the reply is 0 else its 1 followed
> by another 64 byte packet of data until finished.  I'm worried about
> the possibility of losing data due to small buffer holding data from
> the UART.
>
> AT89C5132
> 2K xdata space; about 600 bytes free
> 57600 baudrate minimum
> USB full speed
> BulkUSB DDK driver
> App uses ReadFile and WriteFile api's
>
> Thanks
>
> Sean

Do you only do UART <-> USB or do you do anything else?
You are aware that Atmel has Communication Device Class S/W?

-- 
Best Regards
Ulf at atmel dot com
These comments are intended to be my own opinion and they
may, or may not be shared by my employer, Atmel Sweden.

I need a design suggestion on the best way to receive data through the
UART. Buffer it, and allow the USB task to pick it up when ready. 
There is only two endpoints that the desktop application can see.
Because of this we are using an ad-hoc application handshaking method.
 The app will send a packet with a command that the processor sees as
a "Query" command. If no data then the reply is 0 else its 1 followed
by another 64 byte packet of data until finished.  I'm worried about
the possibility of losing data due to small buffer holding data from
the UART.

AT89C5132
2K xdata space; about 600 bytes free
57600 baudrate minimum
USB full speed
BulkUSB DDK driver
App uses ReadFile and WriteFile api's

Thanks

Sean