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?
@ Dave and David
I have a Davis (VP2) as well. It is working fine on Sierra. I want to buy a new Mac but that will come with High Sierra.
Question: since posting were you able to get it working? Btw what software are you using? I"m using Weather Display
10.13 has a new restriction on kext like the others have said. If you want to manually load it:
sudo kextload /Library/Extensions/SiLabsUSBDriver.kext/
You will then see the security error:
/Library/Extensions/SiLabsUSBDriver.kext failed to load - (libkern/kext) system policy prevents loading; check the system/kernel logs for errors or try kextutil(8).
Now, from your System Preferences, go to Security & Privacy at the bottom of that window you will see OSX is asking you to approve the kext from Silicon Labs. Do that and you should now be able to see the device:
ls /dev/cu.* ... /dev/cu.SLAB_USBtoUART ...
I also had trouble with this problem.
I started writing this post so I could exactly document my problem to maybe give some extra information and to join the queue seeking a resolution.
As I started to document the sequence of steps I had followed all morning trying to figure this out, blow me the damn thing worked!
I had tried every trick I could find online to get it to work and eventually gave up.
A couple of hours later on I figured I really should join the queue and hope someone can help sooner rather than later.
I had looked at the Tech Note from Apple which strongly says if it was working in Sierra it will still work in High Sierra which in my case wasn't really correct.
Following along the troubleshooting in this thread and the "Troubleshooting the CP210x USB to UART Bridge VCP Drivers on a Mac" guide, I couldn't get it to work.
Now 2 hours later I don't really know what has changed since this morning to make it work.
I had restarted the Mac twice after running some of the commands just in case (I know what you're thinking, it's not Windows it shouldn't need to be restarted :-) )
Here's the basics of what happened this morning - as I tried things, I tested and failed, but this afternoon it now works so I have no idea which bit did fix it.
This mornings story:
I just did an upgrade from Sierra (10.12.6 I think) to 10.13.3.
The same devices have been working in Sierra for 6 months.
Like others have mentioned, I can plug a device in, it's recognised as a CP2012.
I use Parallels so it asks me whether to give it to the Mac or my Windows 8.1 Virtual Machine.
If I give it to Windows VM, it all works fine just like it used to.
If I give it to the Mac (my strong preference) my applications can't see it.
I can see it in System Report/USB as a CP2102 - PID 0xea60 - VID 0x10c4 - Version 1.00
I can't see it in ls /dev/cu.*
I uninstalled and installed the latest MacOS driver.
I never got a prompt to go to Security & Privacy to unlock the KEXT.
I did go there looking, but it was never there.
I tried to manually load it, which appeared successful and gave no errors.
My apps still couldn't see it.
So if you have the same problem as me, try everything in this, the Apple Tech Note and the troubleshooting guide and see if you can figure out which bit does fix it!
I've got a NodeMCU with this chip on it, SILABS CP2102DCL00X 1708+, installed the V5 driver on Mac OS High Sierra 10.13.3 and nothing. The device doesn't show up under /dev/c* neither at /dev/tty.*
same here, trying to flash an ESP32 via arduino ide.
fresh installation of high sierra after problems upgrading from sierra (where it worked without problems). now after some minor high sierra updates at 10.13.3.
security warning & prompt came, was confirmed, kext loaded perfectly fine:
> kextstat -b com.silabs.driver.CP210xVCPDriver Index Refs Address Size Wired Name (Version) UUID <Linked Against> 138 0 0xffffff7f80eef000 0x9000 0x9000 com.silabs.driver.CP210xVCPDriver (5.0.4) AB2A33AD-B60D-35F9-A3F5-084252A66E50 <115 23 4 3>
no /dev/cu* or /dev/ttyUSB*
I managed to got it working, on Mac OS X High Sierra 10.13.3 MacBook Pro (13-inch, 2016, Two Thunderbolt 3 ports). I was fiddling around with it for quite some time, so I'm not sure if these steps are exactly what fixed it, but give it a try and please do report back.
Again, I'm not sure if this is what helped me to fix this, but I guess. Anyway, it does work. But not out-of-the box that's for sure.
Edit: make sure to try out different USB cables as well. It's like the 5th one worked for me. Just sayin
just to let you know that I've published your proposal in another German Forum and some other people tried it last night and do report SUCCESS!
So Thank you very much for sharing your 'patch' in order to enable us to continue working!
Just to make sure it's clear -since you can fix this:
1. download the driver,
2. within 30 minutes go to your mac's preferences,
3. go to Security and Privacy
4. At the bottom click on the 'Allow' button at the bottom and you're good to go.
Me too! Same problem described above using MacOS 10.13.3; I emphasize that approving the load in System Preferences does not result in the driver actually loading.
I need to transfer code in NodeMCU Amica V1 and now it's impossible! Please post asap new driver!
i also strugeled with the Driver install.
Same problems with Registering and loading the Kext. Got this managed.
Also made a fresh install of 10.13
Important REBOT THE MAC. Sounds horrible but the driver locks up the iBridge device.
I have also > 10 devices.
now it gets interesting.
2 devices worked fine. In Console (Applications/Utilities/console) in searchfield key in usb
then you see related messages.
first two devices get recognized with message „driver installed“
So i thought „YEAH FINALY DONE“
i connected third device and the silabs driver comes and then says „can‘t get propperties. ... the chip shows up wit the same pid vid in profiler. Chip also works fine.
ok tried another one which worked before. NO message at all. Ok changed the port on the mac.
connected the working one. Yep confirmed working SLAB showed up also.
again the weird one. Again message of can‘t get propperties.
okay. Reconnected working one. Nope.
connected mouse. Nope
i paniced because i thought i fried the ports.... on a mac ? Nope cant be. Rebooted the mac.
wait loooong shutdown time.
okay need to investigate. My mac is blazing fast......
okay also back in system.
all ports working. So not fried.
Also tested again same way. Same results.
now i looked deeper.
Messages of appleusb regarding ibridge lockdown popping up.
fresh reboot all working.
now i tried something different.
i connected a non powered usb hub.
can you imagine ? It worked perfectly. Except that in communication the log gets spammed with buffer messages from silabs driver.
i think that because usb is like a tree built, the enumeration works on a already enumerated hub.
Detailed report with log files will come later.
no magic involed
I had to bypass the CP2102 chip since the driver are causing so much trouble.
I had an USB port that became unable to detect any device (even my flash drive) after flashing a couple of time an MCU with an CP2102. First I thought that I just blowed a fuse, but after rebooting my USB is now back again.
I strongly suspect the Silabs driver behind this one.
For now on I’m using my trusty FTDI since the silabs drivers are really unusable on macOS.