There wasn't much to it. I originally assumed that the FT232R was
involved in processing XON/XOFF messages in some way because of the
SIO_XON_XOFF_HS and related entries in
ftdi.h. My hope was that XON/XOFF bytes on the UART side would be
changed into status bit changes on USB.
Once I gave up on that direction (still not really understanding
what the chip does with flow control), I realized that the
XON/XOFF bytes were in the data stream untouched by the hardware,
and so I started to process them.
I'm going to spend a little more time trying to understand the
different flow control modes and how they impact both the UART and
USB sides of the chip, but I've solved my immediate problem. I'd
really like to do out of band interrupt signaling, but that's a
project for another day.
Thanks again for a great library. Even though I'm not using it
directly, having it as a reference has been very helpful. If you
want to see what I've been doing, my code is up on github at
https://github.com/mattstock and I have a video of my application
using an early version of the USB code at
https://www.youtube.com/watch?v=Ym3K71dbbVw.
-Matt
On 5/30/2012 8:58 AM, Gautam Morey wrote:
What did you find Matt? Can you please share it.
On Wed, May 30, 2012 at 8:45 AM, Matthew
Stock <stock@xxxxxxxxxxx>
wrote:
On 5/29/2012 9:41 AM, Thomas Jarosch wrote:
libftdi doesn't have built in support for XON/XOFF, you
have to handle this at the application level.
Never mind - I figured it out. Once I realized that the
software flow control options for the chip were a bit of a red
herring, I looked for and found the flow control bytes in the
data stream. All better!
-Matt
--
Gautam
libftdi - see http://www.intra2net.com/en/developer/libftdi
for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
|