- Silicon Labs Community
- Welcome and Announcements
- Silicon Labs Knowledge Base
- 8-bit MCU
- 32-bit MCU
- Bluetooth / Wi-Fi
- Other Products Category
- Optical/RH/Temp Sensor
- Other Products
- Hardware and Software Tools
- Simplicity Studio and Software
- General Discussions and Suggestions
- Chinese Forum
- Software Libraries
- Development Kits
- Reference Designs
- Third Party Tools
- White Papers
- Official Blog of Silicon Labs
- Chinese Blog
08-08-2017 02:53 AM
thanks for your answer. with 10.12.5 It worked perfectly! when I updated to .6 the mac hanged starting up. After long research I removed the silabs .kext from the extensions folder and mac os could start normally. I then tried to install from installer last version of vcp driver but again mac was not able to start. Again removed the kext file... Probably this will not show on all mac hardware, but on forums I found many people having problems with usb related kext files after updating to 10.12.6. Hope in an update of the vcp driver :-) thanks anyway.
08-08-2017 05:00 AM
Do you mean that the mac os 10.12.6 will not able to start after installing the VCP driver or just the CP2102 can't work on the mac os 10.12.6 ?
I have upgraded the new MacBook to the latest 10.12.6, and looks like every goes well...
08-08-2017 08:08 AM
We had a very similary problem (specifically with the Adafruit Arduino Metro Mini).
However, for us, the macOS 5.0 driver would not work at all, no matter what the OS version was.
The nature of the problem was such that the device would appear but there would be serious communication errors when attempting to communicate with it.
Fortunately the included Legacy MacVCP Driver (Version 4.11.2) did work, so we were able to use that. But it certainly appears that there's a serious bug in the 5.0 driver and it would be nice if this could be fixed.
Feel free to ask if more information is required to help debug this.
08-08-2017 09:08 AM
I confirm, the whole mac os was not able to start with the silabs .kext file in the extensions folder. This is known in forums for 10.12.6 also with other usb drivers, not only the Silabs (for example canon, hp etc usb printers). unfortunately it affects the VCP I would like to continue to use on my mac.
As told it is not the same on every mac hardware. Whit your recent MAcBook you are luck and have no problem... do you think there could be a fix also for older macs?
thank you for your precious help.
08-08-2017 09:19 AM
my problem seems quite different: in my case when the driver is installed mac os was not able to start at all. You stated about the 5.0 driver. where did you find it? on the download page the last seams to be the 4.11.0. In fact this is the one I'm referring to in this post. Can you send me the link to VCP 5.0? may be interesting I test it on my mac... have a good day!
08-08-2017 09:36 AM
We did not have problems with either the v5.00 or the v4.11.2 driver preventing macOS startup. This makes me wonder whether there is some other issue with your computer.
Even though the driver page says v4, if you look at the release notes file inside the install dmg, that indicates the driver is version 5.00 and the included legacy driver is version 4.11.2. We experienced this with several computers, too, so it doesn't seem like an isolated incident (for us).
Since macOS doesn't start up: what do you get if you hold down Command-V during boot (for verbose mode)?
08-08-2017 03:13 PM
thank you very much for the hint. I will download and test the v5.00. Hope to have better results than you :-)
I know that it might sound strange a mac that is not able to start for a not compatible kernel extension file (.kext) but I found in forums that it happened same way to a lot of people mainly with the recent 10.12.6 (not on all mac models) and mainly with USB printer drivers that install kext files to work (hp and canon for example).
It's probably a sort of incompatibility of these drivers with the usb hardware deployed in some older macs... But of course I don't pretend every vendor can support any kind of mac hardware, but may be for the developers of silabs there is a way to adapt their driver to 10.12.6 and fix this problem... and I would be very thankful about.