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 ... 10
 on: Today at 05:22:23 AM 
Started by 9ghtX - Last Post by 9ghtX
 I tried to get data from my FT220X using ftDevice.Read() and ftDevice.Purge(ref readData), but there is only zeros in data. I checked hardware signals and there is everything OK.
 So, the question. May be there problem in code (I've attached it to this topic) that causes this problem?

Hardware specifics:
 Clock: 40 Mhz
 Receiving package has 4 bytes
 Connected 2 devices FT234XD via 485 (using Serial.IO C# lib) and FT220X via SPI (using FTD2XX.dll).

 on: December 02, 2020, 10:22:52 AM 
Started by kalle - Last Post by FTDI Community

The .kext version of the VCP driver will not load on macOS 11 and shouldn't be inadvertently claiming devices connected to the machine.

Best Regards,
FTDI Community

 on: December 01, 2020, 04:39:25 PM 
Started by radimoid - Last Post by FTDI Community

Yes that is correct. Please refer to the D2XX Programmer's Guide:

FT_DEVICE_2232C = 4
FT_DEVICE_232R = 5 (also includes FT245R)
FT_DEVICE_2232H = 6
FT_DEVICE_4232H = 7
FT_DEVICE_232H = 8

Best Regards,
FTDI Community

 on: December 01, 2020, 04:34:04 PM 
Started by kalle - Last Post by macsimski
good point.

Another thing i was thinking about: what happens with the old kext if the system is updated from lets say 10.15 to 11.0? is it completely disabled and ignored, or somehow still claiming things it shouldn't. we had problems with that earlier when 10.15 came out.

Unfortunately I am not able to play around with mac os 11.0 Big Sur as I am completely linux based (besides a small virtual windows box to flash the FT232R.)

 on: December 01, 2020, 02:01:28 PM 
Started by kalle - Last Post by FTDI Community

The inbuilt apple driver (AppleUSBFTDI.dext) should work with any default FTDI VID/PID combination.
The FT232R default VID is 0x0403 and its PID is 0x6001, this definition is included in the Info.plist file for the AppleUSBFTDI.dext.

On macOS 10.15 we had noticed that a Wacom Tablet driver was preventing both our VCP driver and apples VCP driver from attaching to devices and providing a COM port in the '/dev' folder. This may still be the case for some of your customers on Big Sur, however it could be an issue with the Apple driver itself.

I will contact the driver development team to see if they can request Apple to open up their driver, however I cannot guarantee this will be possible.

Best Regards,
FTDI Community

 on: December 01, 2020, 11:13:37 AM 
Started by kalle - Last Post by macsimski
Hi All,

Hardware producer using ft232RL in our products here. we are getting more and more reports of people unable to use their devices after upgrading to Big Sur.

-amount of chips used: about 1k.
-location of devices: worldwide.

question: for what type of devices is the new driver from apple enabled? any specific product ID? we are using 0403:6001

would it be an idea that you as ftdichip aks apple to open up their driver?
It looks kinda unprofessional to me that a third party has a driver earlier than the producer of the chip

Is there anything i can do to help? I'm loosing customers!

 on: November 30, 2020, 05:40:43 PM 
Started by namklak - Last Post by namklak
I'm a bare metal embedded C programmer/hardware guy forced to help a friend with a startup - I'm trying to write a driver for Linux (Linux is where I'm a noob).

Device info
[413395.811848] usb 2-1: new full-speed USB device number 9 using xhci_hcd
[413395.968277] usb 2-1: New USB device found, idVendor=0403, idProduct=6015, bcdDevice=10.00
[413395.968281] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[413395.968284] usb 2-1: Product: MK3-USB Interface
[413395.968285] usb 2-1: Manufacturer: VictronEnergy
[413395.968287] usb 2-1: SerialNumber: HQ1901RBVH3
[413395.972452] ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
[413395.972510] usb 2-1: Detected FT-X
[413395.973142] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0

I'm writing a little test driver that uses DX33.  When I call FT_CreateDeviceInfoList, I get 0 devices.

I can open /dev/ttyUSB0 and read some data, but I feel because I'm a linux rookie I should use the ftdi driver. 

Any ideas on why I see 0 devices?


 on: November 30, 2020, 01:59:47 PM 
Started by kalle - Last Post by FTDI Community

Yes that is correct, Apple develop their VCP driver independently from our VCP driver.

Best Regards,
FTDI Community

 on: November 30, 2020, 09:57:14 AM 
Started by radimoid - Last Post by radimoid
in my app, I would like to recognize the FTDI chip type (FT232H vs FT245R). Can this be done by checking FT_DEVICE_LIST_INFO_NODE type? I didn't find any documentation to this struct member. I have just recognized that FT232H has set its value to 0x08 and FT245R to 0x05. Is this general rule? Is there any documentation of type codes?

I know that the type could be also recognized from eeprom product id. But this can be reflashed to any value (as it happened to me once).

 on: November 28, 2020, 07:03:11 PM 
Started by kalle - Last Post by Superboy
FYI also to this thread: I've tried to ask in Apple forums whether it would be possible to somehow utilize Apple's dext driver for FTDI devices with custom PID, but haven't got any answers...  :(


I'm pretty sure I read somewhere you can subclass the Apple driver with a VIP/PID of your own and the Apple driver will load. I can't help you with exactly how though I'm afraid!

Pages: [1] 2 3 ... 10