General Category > Discussion - Drivers

VCP driver on macOS 11

<< < (2/13) > >>

FTDI Community:
Hello,

I see that your device is using the Product ID (PID): 0xEEEF with our default FTDI Vendor ID (VID): 0x0403.
This VID/PID combination is included in our VCP driver (FTDIUSBSerialDriver.kext), however it is not included in the inbuilt Apple VCP driver (AppleUSBTDI.dext).

Unfortunately at this time we do not have a .dext version driver available for macOS 11 Big Sur, but we hope to have this available shortly.

Best Regards,
FTDI Community

James:
Hi there, we are also looking forward to the .dext driver version.

We have a few products using the default FTDI vendor ID with our own PID (granted by FTDI some years back). Will our VID/PID combination also work in the upcoming .dext driver?

Thanks

FTDI Community:
Hello,


--- Quote from: James on September 21, 2020, 02:44:40 PM ---We have a few products using the default FTDI vendor ID with our own PID (granted by FTDI some years back). Will our VID/PID combination also work in the upcoming .dext driver?

--- End quote ---

If your VID/PID combination is currently included in our macOS VCP driver's Info.plist file then yes it will be included in the .dext version of the driver.

Best Regards,
FTDI Community

Kimball:
Big Sur is officially being released today, and there is still no VCP driver available. We have thousands of customers out there with FTDI devices that use a custom VID/PID who are inevitably going to be updating to Big Sur, rendering our equipment completely unusable.

I know FTDI has been working on an update for Big Sur for a while, but can we get a timeline for when it will actually be available? I'll be happy to test a beta version if you have it ready now...

FTDI Community:
Hello,

I have chased the development team up for a relapse schedule for the new .dext driver.
When a beta is available I will post this for community user testing.

Best Regards,
FTDI Community

Navigation

[0] Message Index

[#] Next page

[*] Previous page