I've recently upgraded to 10.13 and then 10.13.1 and my VCP driver stopped working.
I have reinstalled the latest driver again, but to no avail. Any update expecte soon?
Which version of VCP driver you have installed? the latest version is 5 and was available to download here:
Are you founding this issue outside the context of virtual machine?
Does the Mac VCP driver V5 cannot work only for Mac OS v10.13 and later?
In fact I've ever sucessfully installed it on a MacBook with macOS High Sierra V10.13.1 and I see CP210x device can enumerate as expected.
If you are using a CP210x device with VID/PID customization, a customized VCP driver is required. Please contact Technical Support and fill out the CP210x Mac Driver request form which can be downloaded from the following KB article:
The Mac CP210x driver does indeed work with High Sierra.
Make sure you have taken a look at Apple Technical Note 2459 https://developer.apple.com/library/content/technotes/tn2459/_index.html about changes they made to how Kernel extensions are loaded in High Sierra. If you don't specifically approve every kernel extension, they don't load. The user interface Apple implemented for this new security feature has been confusing for many people. The result has been that the kernel extensions doesn't load and they think it just doesn't work on High Sierra and they don't know why.
I'm not saying that this is for sure the cause of the problem you are seeing, but you should rule it out first.
If you do rule it out and are still having problems, please feel free to post back. Please include the VID/PID of your device when you do that. Thanks.
I can confirm this as well, though not on every computer. Something is very wrong here, and it's not a matter of approving the installation.
It would be very helpful if there were some suggested means of debugging this.
In our particular case, using standard SiLabs installer (V5), it's showing up as a recognized usb device, but not showing up as a VCP under /dev/cu*.
The driver is incorrectly signed for Mac OS 10.13. I have opened ticked and explain the situation and it seems like silicon lab employees are ignoring it.
We have thousands of customers using your chip, and ALL 10.13 customers are reporting this issue, and this is well documented by Apple that kext which are not properly signed for 10.13 WILL NOT WORK.
Please review the developer documentation for 10.13 and kernel extensions, properly sign your driver and post the new driver.
Here is the tech note describing the issue in detail: https://developer.apple.com/library/content/technotes/tn2459/_index.html
The only reason your team cant reporduce the issue is because you already had the VPC driver installed when upgrading to 10.13.
To reproduce the issue, do a CLEAN INSTALL of 10.13 on a new system and try to install the driver and plug in a CP2102 device with your default PID/VID. It will not load under /dev/cu.*
I have this same issue with version 5.0.3 when I tried to install on a Mac Mini running MacOS 10.13.2. The drivers install but are not actually loaded.
Last Modified: 11/28/17, 10:02
Bundle ID: com.silabs.driver.CP210xVCPDriver
Get Info String: Version 5.0.3
Obtained from: Identified Developer
64-Bit (Intel): Yes
Kext Version: 5.0.3
Signed by: Developer ID Application: Silicon Laboratories Inc (52444FG85C), Developer ID Certification Authority, Apple Root CA
@Jiehui can we get an ETA on when Silabs will release an updated driver with the proper signing/permissions managment for 10.13? This is something that would literally take an hour to do and resign properly with the current driver.
We have been forcing our customers to use a fairly involved proceedure to reboot into recovery mode and manually disable the signature check in Mac OS 10.13 for the driver to be installed.
I can confirm this as well. I just bought ESP32 and installed drivers on 10.13.2 high sierra, nothing showing up under /dev/cu*
I think you have to try a fresh install on 10.13, not coming from an earlier version of high sierra to see the problem.
Same problem here with MacOS 10.13.2
Trying to use a Davis Instruments data logger. It was working fine with Sierra. Now broken.
Me too! Same problem described above using MacOS 10.13.2; again I emphasize that approving the load in System Preferences does not result in the driver actually loading.
This results in not being able to use a Davis data logger, and my weather station is offline which is a complete failure of promised functionality.