FT232R, async bit-bang, ftdi_write() -- how to know when it's done?
Hi, I'm trying to use FT232R chip in asynchronous bit-bang mode with libftdi and I'm confused. I've read the examples, but they all only write data. >From what I understand, if I send data with ftdi_write(), it will be sent to the chip in one burst and the chip will proceed to output it to its GPIO pins at the previously set baudrate (actually, I'm sending one byte at a time, but I know the general idea). How do I know when all data has been sent? I'd like to read another pin (set as an input pin) using ftdi_read_pins(), but first I have to be sure that all data that should be sent has been sent. D2XX drivers have FT_GetStatus() function for that. I can't find anything similar in libftdi. Bonus question: what values should I write to bits that were configured as inputs? Does it matter? Thanks. -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to libftdi+unsubscr...@developer.intra2net.com
Re: [PATCH] CMake: move options to a dedicated file
Hi Yegor, On 01/03/2018 01:46 PM, Yegor Yefremov wrote: > Also disable all options having extra dependencies. > > If an option is selected makes its dependencies as REQUIRED. thanks for the big patch. It's almost merged :) What needs a bit of discussion is the change in default behavior: The old cmake script was "best effort": If you f.e. had libconfuse installed, ftdi_eeprom was automatically build. With the new way of doing things, ftdi_eeprom needs to be enabled upon request. This changes user expectations that have grown over many years. Do you think we can re-enable ftdi_eeprom and the python bindings by default? Not sure how widespread the C++ wrapper is used. What about having libconfuse / boost library detection in CMakeOptions.txt to set the default values? Cheers, Thomas -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to libftdi+unsubscr...@developer.intra2net.com
