Re: SH7043 Maximum baud rate
Thanks so much for your prompt reply, Stan.
I'm using interrupts as well. I am able to send data at 115Kbps
successfilly but
reception of chunks of data(say 1k) eventually results in an Overrun
error.
>>From my understanding, the SH7043 has UART\SCI with a single byte
hardware
buffer. I was under the impression that because the SCI does not have a
FIFO queue for buffering, high baud rates would be unreliable.
But the fact that you are able to communicate at 115Kbps suggests that
my understanding is incorrect. I will go back and try to figure this
out.
I would greatly appreciate any advice that you can offer.
Thanks again !
Vivek
.
Relevant Pages
- Re: Sockets and File Transfer and Corruption Problems
... For some reason when I load the winsock buffer with data and send it and I ... how it is loading the socket with the data but it's not working then if I ... chunks of data to arrive in same sizes as sent. ... in the file then another 1024 bytes of data is nothing but zeros. ... (microsoft.public.win32.programmer.networks) - Re: Expat problems
... > buffer is nul-terminated. ... Not a standard header. ... was read in by "chunks" instead of the whole file into memory. ... I say read in the data in chunks. ... (comp.lang.c) - Re: How to split a compressed file programmatically?
... value is there in converting that to a string and then back to a long? ... And why allocate a new buffer for each chunk you want to write, ... void splitFile(string path, string path_parts, int size_part) ... just read chunks of the original file until you can't ... (microsoft.public.dotnet.languages.csharp) - Re: serving a file to a client --- background fcopy read fileevent event puts socket cha
... probably not -size (although having -size pre-load the input buffer ... you can't even observe the progress of the [fcopy] from outside (ie. ... 4096 byte chunks. ... The division of functionality I mentioned should have negligible impact ... (comp.lang.tcl) - Re: How to split a compressed file programmatically?
... Personally, I would forget about the calculation altogether and just write a loop that keeps writing bytes in chunks as large as you want or however many bytes you have remaining, whichever is less, until you have no more bytes to write. ... The "size_part" variable is already a long; what possible value is there in converting that to a string and then back to a long? ... And why allocate a new buffer for each chunk you want to write, and why does that buffer have to be the length of the original file, and given that you're allocating a new buffer each time, why read the data anywhere other than the beginning of the buffer? ... void splitFile(string path, string path_parts, int size_part) ... (microsoft.public.dotnet.languages.csharp) |
|