FTDI Community

General Category => Discussion - Drivers => Topic started by: kalle on September 10, 2020, 12:20:41 PM

Title: VCP driver on macOS 11
Post by: kalle on September 10, 2020, 12:20:41 PM
The current VCP driver can't be installed on macOS 11 beta 6 as Apple seems to consider it a "legacy system extension" (https://support.apple.com/en-us/HT210999). Is there any plans to provide a driver that works on macOS 11?
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on September 11, 2020, 12:57:48 PM
Hello,

We are currently working on a .dext version of the driver to be compatible with the newer versions of macOS.
 
However in macOS 10 Apple distributed a VCP driver built into the OS which works for all standard FTDI devices, this was called AppleUSBFTDI.kext pre-Catalina and AppleUSBFTDI.dext in Catalina. I haven’t had a chance to look at macOS 11 yet, but I believe the inbuilt apple driver should still be included.


Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: on8mc on September 11, 2020, 07:25:13 PM
I use two (2) devices with a FTDI chip. An RT Systems USB-62C cable and a Microham USB Interface III.

The RT Systems USB-62C cable works fine with the built-in .dext in macOS 11 Big Sur Beta 6. The Microham USB Interface III doesn't.
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on September 14, 2020, 03:43:59 PM
Hello,

I am unfamiliar with the Microham USB Interface III, could you share its details from the hardware monitor similar to the attached screenshot?

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: on8mc on September 14, 2020, 05:57:45 PM
Here it is (in macOS Catalina):

(https://www.imgdumper.nl/uploads9/5f5fa0dcdc05e/5f5fa0dcd91ee-Schermafbeelding_2020-09-14_om_18.54.34.jpg)


in macOS 11 Big Sur:

(https://www.imgdumper.nl/uploads9/5f5fa36177059/5f5fa3616da6a-Schermafbeelding_2020-09-14_om_19.04.59.png)

Title: Re: VCP driver on macOS 11
Post by: FTDI Community on September 18, 2020, 10:45:48 AM
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
Title: Re: VCP driver on macOS 11
Post by: James on September 21, 2020, 02:44:40 PM
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
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on September 22, 2020, 03:56:28 PM
Hello,

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?

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
Title: Re: VCP driver on macOS 11
Post by: Kimball on November 12, 2020, 05:12:48 PM
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...
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on November 16, 2020, 11:18:30 AM
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
Title: Re: VCP driver on macOS 11
Post by: jcsmedley on November 21, 2020, 07:35:43 PM
Any updates?

Thanks,
Jeff
Title: Re: VCP driver on macOS 11
Post by: Superboy on November 23, 2020, 02:51:52 AM
It is now 5 months since the first developer beta of Big Sur, why is there still no updated driver? Can there be at least an update on how far along it is, 10%? 90%?
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on November 23, 2020, 02:17:18 PM
Hello

It is now 5 months since the first developer beta of Big Sur, why is there still no updated driver? Can there be at least an update on how far along it is, 10%? 90%?

Are you using a device with a non default VID/PID combination?

As far as I am aware our developers are still waiting on Apple clarifying some questions on .dext development. Unfortunately I do not have an updated schedule for release at this point. But this is a top priority for us and I will update when I have any new information.

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: Superboy on November 23, 2020, 02:49:31 PM
Thanks for the reply.

I'm using a FT2232HL, and the Apple driver returns "SetTTY (fd 5): ioctl failed: Invalid argument" when trying to use channel 0 with screen, and a similar error through Python:


Code: [Select]
File "/Users/user/.espressif/python_env/idf4.2_py3.9_env/lib/python3.9/site-packages/serial/serialposix.py", line 272, in open
    self._reconfigure_port(force_update=True)
File "/Users/user/.espressif/python_env/idf4.2_py3.9_env/lib/python3.9/site-packages/serial/serialposix.py", line 435, in _reconfigure_port
    termios.tcsetattr(
termios.error: (22, 'Invalid argument')

Strangely, trying to use channel 1 sometimes doesn't report an error though I can't test whether serial actually works as its pins aren't exposed appropriately on this board - they're usually for JTAG.

Another reason I need the FTDI drivers too is so that I can edit the Info.plist and prevent the serial driver from being loaded on the JTAG channel. A workaround before was to unload the Apple (and FTDI) driver, start the debugger and load the driver - which prevents the driver enumerating the JTAG channel. Loading and unloading the Apple dext seems to be unreliable at best right now, and even then it doesn't help with the ioctl error.
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on November 23, 2020, 03:59:36 PM
Hello,

Thanks for the details.
Just to confirm you are seeing this error only on big sur with the inbuilt apple driver?

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: kalle on November 24, 2020, 02:47:54 PM
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...  :(

https://developer.apple.com/forums/thread/659891 (https://developer.apple.com/forums/thread/659891)
Title: Re: VCP driver on macOS 11
Post by: lelebass2001 on November 24, 2020, 03:01:16 PM
Hi,
we are in a similar situation here, we currently use libftd2xx.dylib with our VID/PID. Do you plan to release a libftd2xx.dext?

Best Regards,
Daniele

Hello

It is now 5 months since the first developer beta of Big Sur, why is there still no updated driver? Can there be at least an update on how far along it is, 10%? 90%?

Are you using a device with a non default VID/PID combination?

As far as I am aware our developers are still waiting on Apple clarifying some questions on .dext development. Unfortunately I do not have an updated schedule for release at this point. But this is a top priority for us and I will update when I have any new information.

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on November 24, 2020, 03:15:09 PM
Hello,

The D2XX driver is a dynamic library file on macOS and is not related to the kernel/driver extension migration currently happening with the VCP driver.

What issues are you seeing with the D2XX driver?

Hi,
we are in a similar situation here, we currently use libftd2xx.dylib with our VID/PID. Do you plan to release a libftd2xx.dext?

Best Regards,
Daniele

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: lelebass2001 on November 24, 2020, 03:30:49 PM
You are right, my mistake.

I do not want to hijack this thread, but the question is if the libftd2xx.dylib can run under Apple ARM architecture. As far as I know the current 1.4.4 dylib has only x86_64 support.

Best Regards,
Daniele
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on November 24, 2020, 04:33:06 PM
Hello,

My understanding is that the Rosetta 2 binary translator will allow for x86_64 libraries and applications to run on the new Apple M1 processors with minimal performance loss. But I will raise this with the developers and see if they can clarify.

We of course intend to rebuild the libftd2xx.dylib for the ARM platform, but we are currently concentrating on the VCP .dext transition.

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: Superboy on November 28, 2020, 07:01:22 PM
Hello,

Thanks for the details.
Just to confirm you are seeing this error only on big sur with the inbuilt apple driver?

Best Regards,
FTDI Community


Yes, I can't load the FTDI driver at all.

I reinstalled Big Sur and initially it worked, but it has broken again. I think it may have something to do with VMWare Fusion, as it seemed to break when that was running. However I have since deleted all traces of Fusion (including kexts) and the problem persists.

The attachment shows the message that it has loaded the driver but then trying to access the serial ports with
Code: [Select]
screen again shows
Code: [Select]
SetTTY (fd 5): ioctl failed: Invalid argument.

Quite often attaching the FT2232 results in an enumeration error shown in the second attachment. Does Apple write their driver independently of yourselves? If so, i'll submit a big report to them.

Thanks.
Title: Re: VCP driver on macOS 11
Post by: Superboy on November 28, 2020, 07:03:11 PM
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...  :(

https://developer.apple.com/forums/thread/659891 (https://developer.apple.com/forums/thread/659891)

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!
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on November 30, 2020, 01:59:47 PM
Hello,

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

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: macsimski on December 01, 2020, 11:13:37 AM
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!
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on December 01, 2020, 02:01:28 PM
Hello,

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
Title: Re: VCP driver on macOS 11
Post by: macsimski on December 01, 2020, 04:34:04 PM
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.)
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on December 02, 2020, 10:22:52 AM
Hello,

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
Title: Re: VCP driver on macOS 11
Post by: n0uk on December 11, 2020, 08:24:40 PM
It is also identical to that shown below in at least one of their older products too, the Microham MicroKeyer II.

I have the same inability to use that device until the .dext VCP driver is available for Big Sur.

Chris, N0UK

Here it is (in macOS Catalina):

(https://www.imgdumper.nl/uploads9/5f5fa0dcdc05e/5f5fa0dcd91ee-Schermafbeelding_2020-09-14_om_18.54.34.jpg)


in macOS 11 Big Sur:

(https://www.imgdumper.nl/uploads9/5f5fa36177059/5f5fa3616da6a-Schermafbeelding_2020-09-14_om_19.04.59.png)
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on December 14, 2020, 03:22:34 PM
Hello,

I've doubled checked the above Product ID in the info.plist file and it looks like there are no special settings being used for this device. As such programming the device to use its Default product ID would all you to use it with the inbuilt Apple VCP driver. Are you aware of which FTDI product this device uses?

I've had an update from the developers, and they are currently working on resolve signature issues with the .dext driver package.

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: on8mc on December 15, 2020, 02:49:21 PM
I've doubled checked the above Product ID in the info.plist file and it looks like there are no special settings being used for this device. As such programming the device to use its Default product ID would all you to use it with the inbuilt Apple VCP driver. Are you aware of which FTDI product this device uses?

Are you sure? I received the following comment from microHAM:

Quote
Herwig,

Yes, you can change PID using tools FTDI provides, but than interfaces will not work with our Windows Router software anymore and it will be violation of FTDI rules and warranty for interface. I recommend you to wait until FTDI releases driver for Big Sur.

Apple is causing issue by creating own driver for default chip PID and breaking devices usability for manufacturers who play by rules, hope FTDI will backup their customers quickly.
 
Default chip PID is reserved only for experimenting, small batch or for certified FTDI OEM partner. Neither Anytone, RT System or Kenwood is FTDI official OEM partner. Using default PID in non OEM commercial product is violation of rules. Only owner of VID (FTDI) can assign PID to particular manufacturer/product or product range. Same VID/PID cannot be used by different manufacturers on different devices for different functionality, that's basic rule set by USB-IF authority (usb.org) and that's the reason why we have asked FTDI for assigning range of custom PIDs and using them for many years.

73 Jozef OM7ZZ
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on December 16, 2020, 12:51:06 PM
Hello,

Here is the entry for the device with the 0xEEEF product ID:
Code: [Select]
<key>microHAM USB Port</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.FTDI.driver.FTDIUSBSerialDriver</string>
<key>IOClass</key>
<string>FTDIUSBSerialDriver</string>
<key>IOProviderClass</key>
<string>IOUSBInterface</string>
<key>bConfigurationValue</key>
<integer>1</integer>
<key>bInterfaceNumber</key>
<integer>0</integer>
<key>idProduct</key>
<integer>61167</integer>
<key>idVendor</key>
<integer>1027</integer>
</dict>

And for reference here is a standard FT232R device:
Code: [Select]
<key>FTDI R Chip</key>
<dict>
<key>CFBundleIdentifier</key>
<string>com.FTDI.driver.FTDIUSBSerialDriver</string>
<key>IOClass</key>
<string>FTDIUSBSerialDriver</string>
<key>IOProviderClass</key>
<string>IOUSBInterface</string>
<key>bConfigurationValue</key>
<integer>1</integer>
<key>bInterfaceNumber</key>
<integer>0</integer>
<key>bcdDevice</key>
<integer>1536</integer>
<key>idProduct</key>
<integer>24577</integer>
<key>idVendor</key>
<integer>1027</integer>
</dict>

The Microham device hasn't defined any special settings for latency timer, buffer sizes of buad rate aliasing, which is where my original comment stems from. However the have omitted the bcdDevice field which may cause issues depending on which IC they are using. If they are advising their software wont work when the FTDI defaults are used then I would stick with this advice. But in general as a stop gap solution it is perfectly fine to re-program a device to use FTDI defaults.

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: on8mc on December 16, 2020, 04:26:46 PM
Thanks for the information. I changed the PID of the microHAM USB Interface III to 0x6001 (24577) and it works now with the standard macOS Big Sur .dext
Title: Re: VCP driver on macOS 11
Post by: kalle on December 23, 2020, 10:02:39 AM
Related to this, it seems that there's some problem with the kext driver version 2.4.4 notarization, so the installer refuses to start even on macOS 10.15.
Title: Re: VCP driver on macOS 11
Post by: Kimball on January 11, 2021, 09:19:00 PM
Any update on VCP drivers for Big Sur? I'm hearing daily from upset customers that their device does not work.. and Big Sur has been out for months now.... :(
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on January 12, 2021, 02:06:10 PM
Hello,

Unfortunately there hasn't been any updates from our driver team as of yet, but I will be sure to post any updates when I receive them.

Best Regards,
FTDI Community
Title: Re: VCP driver on macOS 11
Post by: Kimball on February 18, 2021, 07:10:00 PM
It's been more than another month now... it seems clear that nobody is actually working on this. The new driver requirements are not *that* horrible - they are no longer .kext, but Apple is pretty transparent about how you need to set them up and sign them etc.

Any chance we'll get new drivers from FTDI this quarter?

03/19/2021 Update: No. No chance they'll get this out this quarter. Maybe this summer.
Title: Re: VCP driver on macOS 11
Post by: n0uk on March 05, 2021, 01:46:21 AM
This is getting really pretty old.  When is this problem going to get any attention?
Title: Re: VCP driver on macOS 11
Post by: n0uk on March 05, 2021, 01:52:00 AM
Thanks for the information. I changed the PID of the microHAM USB Interface III to 0x6001 (24577) and it works now with the standard macOS Big Sur .dext

Thanks for verifying that it's possible to get a Microham device working with Big Sur's native driver.  What exactly did you have to do to get it working?  Presumably just editing some text configuration file, but which/how?

Chris, N0UK
microKEYER II user!
Title: Re: VCP driver on macOS 11
Post by: on8mc on March 06, 2021, 09:38:52 AM
@n0uk

I changed the PID with FTDI's FT_Prog software on a Windows computer. It's a pretty easy exercise.
Title: Re: VCP driver on macOS 11
Post by: macsimski on March 17, 2021, 12:45:17 PM
I was reminded of this problem by one of my customers. can someone give the developers some strong coffee? and make it a very big red point on the top of their list? this is becoming very embarrassing.
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on March 17, 2021, 03:09:50 PM
Hello,

I have be liaising with the driver team recently and they are making good progress. We are currently establishing which features supported in our driver but not in the Apple driver are most pertinent for a beta release. For example, baud rate aliasing or latency timer settings.

If you are using any of these feature please let me know.

Best Regards,
FTDI community.
Title: Re: VCP driver on macOS 11
Post by: n0uk on March 19, 2021, 01:52:02 PM
@n0uk

I changed the PID with FTDI's FT_Prog software on a Windows computer. It's a pretty easy exercise.

Thanks
Title: Re: VCP driver on macOS 11
Post by: dosch on March 23, 2021, 11:39:02 AM
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 just registered an account on this forum to confirm that uninstalling Wacom resolved my connection issues.
I was fighting this problem for several days before I found this solution. I hope that my confirmation saves someone else some time.

Wacom drivers are the worst...
Title: Re: VCP driver on macOS 11
Post by: patters on June 18, 2021, 11:19:09 AM
I have an FT23R-based USB-Serial device running on Big Sur and it's used for bidirectional serial communications with a legacy device, making use of flow control using the RTS and CTS pins. However, with both the Big Sur OS-integrated driver, and with the FTDI-published VCP beta driver dated 2021-05-18 (https://ftdichip.com/Drivers/vcp-drivers/) for macOS 11 the file transfers only work in one direction - from mac to the device. Retrieving files from the device to the Mac does not work.

The same USB-Serial device works fine for transfers in both directions on Windows 10 using the same open source client software, so there appears to be something fundamentally broken with this driver. I also found this error report, which may be the same issue (CTS not working properly?):
https://www.gitmemory.com/issue/serialport/node-serialport/2243/834035511
Title: Re: VCP driver on macOS 11
Post by: FTDI Community on June 18, 2021, 02:21:17 PM
Hello,

Thank you for your feedback, I have reported this back to the development team for investigation.

Best Regards,
FTDI Community