FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  


Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support

New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Pages: 1 [2] 3 4 ... 10
 on: March 01, 2021, 04:42:10 PM 
Started by Anshumantech - Last Post by FTDI Community
Hello Asrorr,

Are you using a custom hardware design or one of the FT2232H Mini Modules?

If you are using the mini module, please ensure you have powered the device in either configuration as per Section 3 of the datasheet (see the bottom of page 7). It is important that you make all of the connections denoted for either a Self or Bus powered configuration.

Best Regards,
FTDI Community

 on: February 28, 2021, 03:10:21 AM 
Started by Anshumantech - Last Post by asrorr
In my case, my two laptops are detecting ft2232h as a ft4232h on both ft_prog and mprog >:(.
Why this happens? :-\

 on: February 25, 2021, 02:38:34 PM 
Started by earnie - Last Post by FTDI Community

Thank you for your question.

Yes, essentially USB products can’t reliably be used in real-time applications with time interval resolution guarantees.

Sometimes the inherent behaviour of USB can be a problem and applications cannot be guaranteed throughput.
If there is more USB traffic then the OS and USB have to schedule the communication with each of the USB devices.
It’s highly dependent on the OS and USB Host and is out with our control.

This explains why on occasion you are seeing data update seeming out of order for a given microcontroller.

Switching to a D2XX implementation would certainly allow you to delay printing of a row of ASCII text in your output until all of the data has been read for the corresponding rows with FT_Read calls. For example, you could configure you program to read 1 byte from each microcontroller before allowing the data to be output by your application. This should negate any issues where the data is being printed from devices out of order. But it is still important to note that the USB host controllers scheduling algorithms do not change from using the VCP driver to the D2XX driver.

Best Regards,
FTDI Community

 on: February 25, 2021, 12:18:41 PM 
Started by earnie - Last Post by earnie
I have 11 UART Serial Adapter Cables of the following types that are logging information simultaneously from 11 microcontrollers:


I have written a simple terminal application that can handle 11 com port connections simultaneously and writes all the received ASCII-characters in the same window row-by-row. I sometimes find that ASCII-text from two different microcontrollers are received in the wrong order and I believe this has something to do with the fact that USB likes to wait for a certain amount of bytes before sending the packet. My question is, if I switch from using VCP-driver to the D2XX-driver, would this likely improve so all the text in my terminal window would appear in chronological order?

 on: February 24, 2021, 04:19:18 PM 
Started by AlwaysBufferGhz - Last Post by FTDI Community

Which OS are you using?

Can you please use Microsoft USBView to check the details of the hardware that you are using?
Make sure the config descriptors option is selected (Options menu) and you may press F5 to refresh.
Now select the device that is highlighted by the exclamation mark, if applicable.
The idVendor and idProduct numbers are of interest.
Please include all the information in your reply like this:

Code: [Select]
Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x08 (8)
idVendor:           0x0403 (Future Technology Devices International Limited)
idProduct:          0x6001
bcdDevice:          0x0600
iManufacturer:        0x01
0x0409: "FTDI"
iProduct:             0x02
0x0409: "USB <-> Serial Converter"
0x0409: "USB <-> Serial Converter"
iSerialNumber:        0x03
0x0409: "FT123456"
bNumConfigurations:   0x01

Have you also tried pre-installing the driver on the PC with our setup executable?
Note that you can also point to the 2.12.28 drivers in Device Manager.

Also refer to the Installation Guides.

Best Regards,
FTDI Community

 on: February 24, 2021, 04:18:26 PM 
Started by earnie - Last Post by FTDI Community

OK Windows uses the VID, PID and Serial Number to enumerate the device, so that's why you can see that in the Device instance path property.
However note that sometimes Windows may not assign the serial number in the registry entry. It may use different nomenclature so it shouldn't be relied upon.

The Product Description can only be read using the D2XX Driver.

Your program could easily use the D2XX driver to find out the information and pass that information to continue using the VCP Driver.
You could use the following D2XX functions to find out the information that you require:

FT_Open / FT_OpenEx

Best Regards,
FTDI Community

 on: February 24, 2021, 09:26:28 AM 
Started by earnie - Last Post by earnie
The D2XX driver is used to program the device parameters like serial number and description.
Using the VCP-driver, I can view the serial number in the Device Manager by right-clicking -> Properties -> Details tab -> choosing Device instance path in the Property combobox. Can I do something similar to view the contents of the description you're referring to, in the Device Manager when using VCP-driver? Everything I'm able to view in the Device Manager, my C# application can view as well. So my idea is that I program the EEPROM using the D2XX-driver, but once the EEPROM is programmed, from then on I only use the VCP-driver.

 on: February 23, 2021, 04:35:41 PM 
Started by earnie - Last Post by FTDI Community

The workaround that I provided relies on the D2XX driver for listing and opening the device with a custom parameter.

Using the VCP driver is limited to open by COM Port number.

The D2XX driver is used to program the device parameters like serial number and description. This is a one time task as it will be stored in the device EEPROM. It can be programmed using FT_PROG or see AN_428 D2XX EEPROM Programming Examples.

You can write some application code that uses both the D2XX and VCP driver functionality.

Best Regards,
FTDI Community

 on: February 23, 2021, 04:33:02 PM 
Started by AlwaysBufferGhz - Last Post by AlwaysBufferGhz

On Windows 7 I have a device using the FT232RL (maybe generic) serial port which is a native windows driver. Unfortunately, someone deleted the USB composite serial converter, checked "delete the driver software for this device" and now the COM port or serial converter will not appear in device manager when a reboot is performed.

I have downloaded the drivers on the website, extracted them, and directed them to search for the drivers however the searching bar does not stop searching.

 on: February 23, 2021, 04:02:39 PM 
Started by FTDI Community - Last Post by lgk
I have the same warning on Catalina 10.15.7.

$ sudo kextutil /Library/Extensions/FTDIUSBSerialDriver.kext
    Dependency lacks appropriate value for OSBundleRequired and may not be available during early boot:
        com.apple.iokit.IOSerialFamily - Safe Boot

(kernel) Notice - new kext com.apple.driver.usb.AppleUSBHostPlatformProperties, v1.2 matches prelinked kext but can't determine if executables are the same (no UUIDs).

I have installed D2XX 1.4.22, D2XXhelper and VCP drivers 2.4.4
The driver is loaded after the above command but I cannot see any devices /dev/tty.usbserialXXX or /dev/cu.usbserialXXX under /dev.

In system information Hardware-> USB I get the following information.

Dual RS232-HS:

  Product ID:   0x6010
  Vendor ID:    0x0403  (Future Technology Devices International Limited)
  Version:      7.00
  Speed:        Up to 480 Mb/s
  Manufacturer: FTDI
  Location ID:  0x14220000 / 16
  Current Available (mA):       500
  Current Required (mA):        500
  Extra Operating Current (mA): 0

Pages: 1 [2] 3 4 ... 10