FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

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 5

Author Topic: VCP driver on macOS 11  (Read 117037 times)

FTDI Community

  • Administrator
  • Hero Member
  • *****
  • Posts: 891
    • View Profile
Re: VCP driver on macOS 11
« Reply #30 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
Logged

on8mc

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: VCP driver on macOS 11
« Reply #31 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
Logged

kalle

  • Guest
Re: VCP driver on macOS 11
« Reply #32 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.
Logged

Kimball

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: VCP driver on macOS 11
« Reply #33 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.... :(
Logged

FTDI Community

  • Administrator
  • Hero Member
  • *****
  • Posts: 891
    • View Profile
Re: VCP driver on macOS 11
« Reply #34 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
Logged

Kimball

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: VCP driver on macOS 11
« Reply #35 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.
« Last Edit: March 19, 2021, 08:51:07 PM by Kimball »
Logged

n0uk

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: VCP driver on macOS 11
« Reply #36 on: March 05, 2021, 01:46:21 AM »

This is getting really pretty old.  When is this problem going to get any attention?
Logged

n0uk

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: VCP driver on macOS 11
« Reply #37 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!
Logged

on8mc

  • Newbie
  • *
  • Posts: 5
    • View Profile
Re: VCP driver on macOS 11
« Reply #38 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.
Logged

macsimski

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: VCP driver on macOS 11
« Reply #39 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.
Logged

FTDI Community

  • Administrator
  • Hero Member
  • *****
  • Posts: 891
    • View Profile
Re: VCP driver on macOS 11
« Reply #40 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.
Logged

n0uk

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: VCP driver on macOS 11
« Reply #41 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
Logged

dosch

  • Newbie
  • *
  • Posts: 1
    • View Profile
Re: VCP driver on macOS 11
« Reply #42 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...
Logged

patters

  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: VCP driver on macOS 11
« Reply #43 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 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
« Last Edit: June 18, 2021, 03:23:34 PM by patters »
Logged

FTDI Community

  • Administrator
  • Hero Member
  • *****
  • Posts: 891
    • View Profile
Re: VCP driver on macOS 11
« Reply #44 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
Logged
Pages: 1 2 [3] 4 5