This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Shannon Holland wrote:
The data point I was using regarding overrun was that if I unplug the serial cable while everything is running, the at91 keeps plugging away with new data for a while until it finally empties the buffer. Making the serial buffer larger or smaller changes this time appropriately.
That does sound more like an overrun then.
Flow control is definitely a solution. I also need to implement a[snip]
eCos has support for this. If you implement hardware flow control in the same way as the 16x5x driver, it should all just work theoretically. The generic serial driver layer (in io/serial) will call into the hardware driver to diddle your flow control lines if the generic layer is going to run out of space.In my application, the only way to get around this byte-dropping problem was by implementing flow control. I chose to implement it at the software (i.e. protocol level) instead of hardware. (Strictly speaking, hardware flow control is not automatic with the at91 USART. So what I'm really saying for hardware flow control, is dedicate an I/O pin and call it DTR [or whatever] and drive it manually with the software.)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |