Before following the steps below, please take some time to read the generic tips for troubleshooting and asking questions from this post:
[Note2] If you are not the manufacturer of the device you are troubleshooting, note that Silicon Labs does not support end users directly. Please contact your product manufacturer for support. For more information, please see the following knowledge base article:
Following steps are considered as additional to information described from above. When you will post a question regarding VCP driver for Mac OS, please provide some information as below:
1) The SCH/Layout of your board if It is your custom design (eg: not Silicon Labs' EK).
2) The part number and the VID/PID of the part that you are using.
3) The output of the commands below (make sure your board is plugged in because the driver will not be loaded if there is no device attached to your system):
Get Mac Version: $ sw_vers
For Big Sur: $ systemextensionsctl list | grep -iE '(silabs|cp210x)'
For Older Mac OS (ex: Catalina): $ kextstat | grep -iE '(silabs|cp210x)'
List USB devices: $ ls /dev/cu.*
4) Your test code or scripts if any that you are using and have the issue with.
Before posting a question
When posting a question, make sure to include the following:
Note: If you are not the manufacturer of the device you are troubleshooting, note that Silicon Labs does not support end users directly. Please contact your product manufacturer for support. For more information, please see the following knowledge base article: http://community.silabs.com/t5/Silicon-Labs-Knowledge-Base/Troubleshooting-a-Product-Using-a-CP210x-USB-to-UART-Bridge/ta-p/131318
For general community usage please refer to the Silicon Labs Community Guidelines
We've recently become aware of an issue with a new update to Windows 10 and our CP210x VCP "Universal" Driver for Windows 10, driver version v10.1.1. When attempting to install the driver, an error is given by Windows that states "A service installation section in this INF is invalid." This occurs because Windows has changed drive INF requirements slightly, and our current driver's INF file does not meet these requirements.
We currently are working to fix this issue, although due to testing and recertification requirements, we do not expect the fixed driver to be available until mid-June.
A work-around exists currently, but it involves manually editing the .INF file for the driver. This causes another issue - the driver is no longer signed in this case, so the driver must be forced to install, and Windows will show a warning that the driver is unsigned.
Firstly, the work-around is as follows:
Download the Windows 10 Universal driver from here: https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers
Edit the .inf file with this driver, performing the following modifications:
On or around line 118, change/edit
ServiceBinary = %13%\silabser.sys
ServiceBinary = %12%\silabser.sys
And on or around line 160, change/edit
Silabser_CopyFiles_FileListSection = 13 ; Driver package's Driver Store directory (%WINDIR%\System32\DriverStore\FileRepository ) (was 12 Drivers directory (%SystemRoot%\system32\drivers))
Silabser_CopyFiles_FileListSection = 12 ; Driver package's Driver Store directory (%WINDIR%\System32\DriverStore\FileRepository ) (was 12 Drivers directory (%SystemRoot%\system32\drivers))
I.e. replace every 13 in the file with 12.
Once these changes are made, attempt to re-install the driver. A warning will be shown that the driver is unsigned, but you can ignore this for now. If you do not receive a warning issue, or if Windows refuses to install the unsigned driver (you may get an error about the hash being invalid), you can disable driver signing enforcement by following these instructions: https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Alternatively, rolling back to a previous build of Windows also resolves the issue.
In a project that I am working on I have a CP2102 implemented on the board, now this is my USB VCOM Device.
The VNC2 is not able to communicate with CP2102 (but it is able to communicate with WSTK BRD4001 as it implements JLink CDC Device).
Is there any way to implement CDC - Device on CP2102?
Can anyone suggest any changes I can make to VNC2 so that it will work with CP2102?
Hello, my custom CP2615 programming board is not recognized by Simplicity Studio.
I've programmed the CP2112 to have PID 0xEA93 and have connected the CP2112 and CP2615 as follows:
I'm using Simplicity Studio version 220.127.116.11.
Here's a capture of the I2C bus between the CP2112 and CP2615:
write to 0x18 ack data: 0xFF 0xFB read to 0x18 ack data: 0x32 0x36 0x31 0x35 0x2E 0x31 0x2E 0x31 0x2E 0x38 0x00 0x00 0x00 0x00 0x00 0x00
Every byte has an ack except for the last one.
Unfortunately, Simplicity Studio does not detect the CP2615. Excuse the CP2615_programmer typo.
Any help would be appreciated.
Several years ago we developed a custom tool for configuring the B01 version of the CP2114 device. We recently populated a B02 device into a board and tried to use the same software and encountered errors. Is there known issues with using B02 devices with older versions of the SDK/DLLs?
I am using Simplicity Studio 18.104.22.168 (Xpress Configurator 4.2.2) and the CP2615-EK-2 running on a Mac Pro using MacOS 10.15.7 (Catalina). When I press either the "Import from Device" or "Program to Device" buttons, I get the error message: "The device 'CP2615 Evaluation Kit (ID: 0) (00B1D755) : CP2615-A01-GM' has no SofIndex." See the attached screenshot. I have tried unplugging and plugging the USB connector, but this makes no difference. I only connect the configuration USB port and leave the audio USB port disconnected. The shorting blocks are installed as recommended in the User's Guide for J15, J16, J13, J14, and J21. The headers J5, J4, and J2 are set for the USB Bus-powered configuration.
Do I actually need to connect the audio USB port as well to provide power to the CP2615? When I do so, macOS keeps enumerating the USB connections in a loop, so this doesn't seem right. Would it make sense instead to apply 3.3V to the evaluation board?
Simplicity Studio seems to be configured properly, but perhaps I am missing something here? Or is it possible that the software has a bug?
Any help would be appreciated.
I have a product that is supposed to enumerate as two VCP ports. This works fine under Windows after installing drivers, but I need to get the VCP ports working in Linux.
I have modified the cp210x.c driver and added the VID/PID for the product, but after rebuild the driver and loading the kernel module I'm seeing two errors for each VCP...the first is erroneous but the second indicates a failure in enumerating the com port:
cp210x 1-22.214.171.124:1.0: cp210x converter detected
[465272.772737] cp210x 1-126.96.36.199:1.0: failed to get vendor val 0x370b size 1: -32
[465272.772741] cp210x 1-188.8.131.52:1.0: querying part number failed
[465272.772935] cp210x ttyUSB0: failed get req 0x4 size 2 status: 0
[465272.772943] cp210x: probe of ttyUSB0 failed with error -5
[465272.775151] cp210x 1-184.108.40.206:1.1: cp210x converter detected
[465272.775271] cp210x 1-220.127.116.11:1.1: failed to get vendor val 0x370b size 1: -32
[465272.775274] cp210x 1-18.104.22.168:1.1: querying part number failed
[465272.775451] cp210x ttyUSB1: failed get req 0x4 size 2 status: 0
[465272.775459] cp210x: probe of ttyUSB1 failed with error -5
I've searched around for information on "failed to get req 0x4" but have not found much on the error or how to fix it. Anyone have any ideas?
I am trying to send and receive serial from an esp32 to an STM32MP1.
From what I understood the download in the silabs repo has not been update for a while. I tried to cross compile the cp210x with the STM32 SDK and tool chain but I get a headers mismatch.
make ARCH=arm CROSS_COMPILE=arm-ostl-linux-gnueabi-
will return in missing headers.
I also tried to get the updated source for kernel 10.10.10 but the compile error persists.
I’m using an ESP32 WeMos Bluetooth WiFi Battery Board (wemosbat).
My Mac Version: High Sierra, version 10.13.6 and sometimes I got upload or monitor the serial, sometimes I got the error:
Errno 16] could not open port /dev/cu.SLAB_USBtoUART: [Errno 16] Resource busy: '/dev/cu.SLAB_USBtoUART'
I use Visual Code with PlatformIO extension, but I face this erro even using any other program to access the board, for instance:
screen /dev/cu.SLAB_USBtoUART 115200
It’s important to notice that some times I get upload and open serial monitor with SiLabs driver, but not in a regular basis. Example: I got upload the binary to the board, if I try to open serial monitor, I need to repeat the process: unplug, plug, until Error 16 (Resource Busy) disappear. And I cannot identify what exactly happens before I got the connection.
I’ve already tried to
# unplug the board sudo kextunload /Library/Extensions/SiLabsUSBDriver.kext/ sudo kextload /Library/Extensions/SiLabsUSBDriver.kext/ # plug the board
But even with this procedure I got resource busy error (but as I said before, some times it works).
Doing more tests, some times I cannot unload driver even with board disconnected
# unplug the board $ sudo kextunload /Library/Extensions/SiLabsUSBDriver.kext/ (kernel) Can't unload kext com.silabs.driver.CP210xVCPDriver; classes have instances: (kernel) Kext com.silabs.driver.CP210xVCPDriver class com_silabs_driver_CP210xVCPDriver has 1 instance. Failed to unload com.silabs.driver.CP210xVCPDriver - (libkern/kext) kext is in use or retained (cannot unload).
How to know what exactly is using the resource, and how to release it in these cases?
I would like to ask for help. I am using CP2110 and USB-C connector on my device.
All works great on Mac if it is connected via a USB hub and the LED turns ON. However, the device is not recognized by MacBook when connected directly to the very same USB-C port as was used to connect the USB hub — the LED stays OFF.
Is there some specific CP2110 guidance or configuration for USB-C or devices using USB 3.1 or USB 3.0?
Any idea how might we make it work connected directly to Mac (without a USB hub)?
P.S. Attaching my system report screenshots to compare how it looks when connected via USB Hub or directly.
Many thanks in advance,
The above driver will not install on my Windows 10 PRO. I receive this message when installing