As discussed in the following thread, it appears the v5.x SiLabs driver is completely broken.

http://community.silabs.com/t5/Interface/mac-os-10-12-6-and-cp2102/m-p/206785

Fortunately the v4.x driver, which is included in the "Legacy MacVCP Driver" folder in the same download, works fine. Do note that you might have to install it twice for it to work, as the first install will just remove the existing driver. If it's installed, there should be a "SiLabsUSBDriver.kext" file in /Library/Extensions with a date created of June 16, 2017.

 

Can someone from SiLabs look at this?

@david_rysk

 

I have been trying for ages to resolve this problem including using the legacy drivers. All to no avail. Delete this - install that, emails to Davis Instruments and trilogy, chat sessions with Apple and so on and so forth. However having discovered your reply, I tried using your double installation trick and -surprise surprise!! my weather station is once again telling the world it's raining in Northern Ireland. Thanks for your help. 

I've been trying to get these devices working on a 2017 MBP with USB-C for a week now.  One ESP32 dev board has CP2102 and works reliably.  I have small CP2102 USB to Serial breakouts from several different sources, and another ESP32 board from another manufacturer that do not work.  They do not show in the system report, or anywhere.  VirtualBox does not see them.  I see no error messages in the system logs.  The devices that have a status LED only flash, and do not stay solid like they normally would.  They all work on my older, 2012 MacBook Pro.  I tried the legacy driver and it did not work either.  Tried uninstalling each time, installing twice, rebooting, installing again, etc...  No luck until today.

Finally, I found that if I run them through a powered USB 2.0 hub, they all work perfectly.  They all consistently show up as /dev/cu.SLAB_USBtoUART

I hope this helps someone!

After reading the previous responses, I found out that I had a USB cable that was power only ("bad cable"). Once I replaced it with a cable that had proper wiring for power and data the latest version of the driver worked (no need to use the legacy version).

MacOS High Sierra 10.13.4

I have MacOS High Sierra 10.13.6  and MP 2017 with usb-c connected to adapter MOSHI that has RJ45 and standard USB together and none of those drivers work, new one and legacy, installed like 10 times. Same cable worked fine on my old High Sierra Mac Air 2011. How to make it work?

I have had the same issue all day as I've received some UART adapters based on CP2102 QFN-28.

On Macbook Pro with USB-C ports only the issue is even stranger.
I use USB-C to micro-USB cables for all my devices which require them, and these adapters are the only thing which doesn't work.
If I plug a USB-C to USB-A adapter, then use an USB-A to micro-USB cable it also doesn't work.

I have tried one more thing: I use a HyperDrive double USB-C side hub (the one which plugs directly into 2 USB-C ports, and through this one I can use the cable which didn't work before (USB-C to micro-USB), but only in the non pass-through port.

This is by far the strangest glitch I've had in a while.

Every device based on CP2104 I own works flawlessly. I guess my design will implement that one just to be safe ;)

if you are all referring to the same cheap chinese implementations I think I found a solution.
apparently on this design coming from who knows where there's a trace connecting pin 9 (/RST) of the CP2102 QFN-28 to a capacitor.
This seems to keep the device in reset state if not enough current is provided (not sure why they did that).

Cutting the trace makes the device come up on your Mac.

Also the same issue causes the pin 3V3 of the adaptor to raise up to 4V3 which is potentially damaging the device you connect it to.

Good luck

ubi

If still someone is still coming to this forum (as I did today) and does have this problem: for me the normal install worked after I confirmed (after installing) in the system's security settings that SI Labs may put the latest V5 driver on my Mac with Mojave.

I was already asked during install for my admin password but this seemed not to be enough. After allowing access in the security settings it worked for me and Arduino IDE shows port " cu.SLAB_USBtoUART ". This allows now access to my ESP32.

I hope this helps.

 

@Chris Miller

I've been trying to get these devices working on a 2017 MBP with USB-C for a week now.  One ESP32 dev board has CP2102 and works reliably.  I have small CP2102 USB to Serial breakouts from several different sources, and another ESP32 board from another manufacturer that do not work.  They do not show in the system report, or anywhere.  VirtualBox does not see them.  I see no error messages in the system logs.  The devices that have a status LED only flash, and do not stay solid like term papers normally would.  They all work on my older, 2012 MacBook Pro.  I tried the legacy driver and it did not work either.  Tried uninstalling each time, installing twice, rebooting, installing again, etc...  No luck until today.

Finally, I found that if I run them through a powered USB 2.0 hub, they all work perfectly.  They all consistently show up as /dev/cu.SLAB_USBtoUART

I hope this helps someone!

 

Hello Chris,

Thanks for the solution. I tried everything too, all recommendations with no luck. The result as it seems is a wrong USB-C to USB 3.0 reduction. Any experience with USB-C reduction for external HDD?

Randy

 

I've looked through these screenshots and description, hope this helps: 

https://www.silabs.com/community/interface/forum.topic.html/mac_os_10_12_6_andc-soundcloud converterUuTs

 

Nice to see this post here and thanks for sharing this to us. Get the details of best hidden camera app android here.

Nice to see this post here and thanks for sharing this to us. Get the details of best hidden camera app android here.

have you downloaded the new version yet? hill climb racing