libftdi Archives

Subject: Re: How do I discover port names (/dev/cu.usb… or COM…) from devices

From: Xiaofan Chen <xiaofanc@xxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Sat, 10 Mar 2018 10:11:22 +0800
On Sat, Mar 10, 2018 at 8:39 AM, Robert Poor <rdpoor@xxxxxxxxx> wrote:
> Uwe Bonnes writes:
>> you can use libftdi for all the application? I don't see why you shop for
>> another tool.
>
> Using libftdi s really my preferred approach at this moment, as long as I
> can continue to use the FT232R in both serial and bitbang mode.

What exactly do you mean by the serial mode? You still want to see tje
FT232R appear as a serial port in Windows Device Manager? Right?

If that is the case, you can either use FTDI's proprietary vendor driver
which supports both the serial port (VCP) and the D2XX direct driver.
There are python bindings. You should be able to use pyserial as well.
Or you can use usbdk backend of libusb-1.0 Windows, then
libftdi/pylibftdi; or pyusb/pyftdi under Windows. You can still use pyserial
or other serial port utilities after finish running libusb/libftdi based
applications.

If you do not need the FT232R to appear as the serial port, then you
can use Zadig to install WinUSB driver, that is the most stable way
to run libftdi under Windows since it is the most mature backend
of libusb-1.0 Windows.


-- 
Xiaofan

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx   

Current Thread