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.
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
I want to use 2 devices with CP2102 under USBxpress, for the 2nd device I change PID for EA62 (so, it would be unregistered driver).
Would one expect a problem, installing unregistered (changed) USBxpress driver under Windows 10?
This problem appeared under Windows 7 and appropriate article AN220.pdf and answer in the Forum were placed on SiLabs site.
But what about Win10? I have not PC under win10, so, answer me, please, are the methods to install the customized USBxpress driver the same as for win7 ?
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 184.108.40.206.
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.
macOS 11.2.3 (20D91)
52444FG85C com.silabs.cp210x (6.0.1/1) com.silabs.cp210x [activated enabled]
Hello. There was a problem compiling the sketch. Arduino cannot connect to /dev/cu.SLAB_USBtoUART port. What could be the problem?
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?
I have a circuit that has a CP2105 bridge for debugging and battery charging only. When not connected, it must run on batteries and is very power sensitive.
What is the state of GPIO pins (including TX and RX) when the USB cable is not attached?
Will the CP2105 drain current from the main circuit in this unattached state? If so, how much current will be drained?
The above driver will not install on my Windows 10 PRO. I receive this message when installing
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-220.127.116.11:1.0: cp210x converter detected
[465272.772737] cp210x 1-18.104.22.168:1.0: failed to get vendor val 0x370b size 1: -32
[465272.772741] cp210x 1-22.214.171.124: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-126.96.36.199:1.1: cp210x converter detected
[465272.775271] cp210x 1-188.8.131.52:1.1: failed to get vendor val 0x370b size 1: -32
[465272.775274] cp210x 1-184.108.40.206: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.
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 trying to use the CP2102N-EB development board to communicate with an ARM microcontroller. This microcontroller's USB port is configured as CDC host.
I am writing the firmware for this microcontroller.
I thought the CP2102N's device class would be 0x02 (CDC Device). But I now know that it identifies as 0xFF (Vendor Specific)
Is there a way to configure the CP2102N to be able to communicate using standard CDC. Or do I have to write a specific driver for it?
Thanks in advance,