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.
I am planning to use Si5351A Programmable oscillator in my project.
27.12MHz crystal is already available in my current design. Can I make use of this 27.12MHz crystal as the reference clock for Si5351A whereas in the datasheet it is mentioned to use 25MHz 0r 27MHz crystals.
SO please let me know, I can make use of 27.12MHz crystal or I need to use 27MHz crystal only.
I am using a CP2105 USB to RS232 UART. Using the Silicon Labs CP21xxCustomizationUtility I can see the default serial number is set to '007AADF2' . On Windows 7, if I open up the device manager and find the device under Ports, right click on it, select Properties > Details, then select 'Parent' from the Property drop down, under value I can see 007AADF2 listed alongside the PID & VID values.
If I then change the Serial Number of the device from the default '007AADF2' to a unique one of our own '181108153800', and repeat the above process I would expect to see '181108153800' in place of 007AADF2. But I don't, I see '5&1b284132&0&1'. On disconnecting everything then reconnecting and checking back again with CP21xxCustomizationUtility, the serial value has been changed and is showing correctly as 181108153800, yet under device manager it is still 5&1b284132&0&1. Can someone please explain the discrepancy here - is there form of encryption used or TLP?
Ultimately though this may not be an issue as all I am looking for is a very simple way to get hold of the serial number from a programming environment (for example C# or C++) but I do not want to have to distribute an additional DLL to my customers in order for them to do this. I need to make this info readily available from the USB device as Windows sees it.
We're designing a product that needs to communicate with ios, and then we found the cp2614,so that we can just control the i2s to comm with ios devices,but we found
so is that true? why is it not recommended?
if so what's your recommendation for instead of cp2614?
I hope this is the correct board, I searched a bit but found no fitting answer yet.
I'm using the Si4703 Rev C with firmware version 19.
I followed Datashet and AN230 to setup 2-Wire I2C Bus mode and have it mostly working now.
The one thing which doesn't works is enabling the STCIEN in the SYSCONFIG1 register and configuring GPIO2 as 0x01 (for STC/RDS INTR. enable).
If I set those two (the STCIEN on powerup and the GPIO2 after powerup complete) I cannot tune anything anymore.
If I only set STCIEN, no GPIO2 it works, I can seek to a channel and listen to crystal clear radio sounds.
But setting any GPIO to a fixed HIGH/LOW with STCIEN doesn't works. Only working combination I found was STCIEN and GPIO2 to a fixed LOW.
But it isn't a power issue, the voltage always stays stable and I2C seems to continue working, chip replies too, just no tuning anymore (or at least no completed tuning)...
Currently I disabled STCIEN and leave GPIOs in tristate and continuously poll the registers to check for a STC bit change in STATUSRSSI register, but this is not ideal because:
a) busy waiting = bad
b) datasheet says that the bus should be quiet during SEEK
Do you have any pointers about what could be wrong?
Spec said a maximum of 14 buttons is supported when GPIO.9 is configured as button input, but only 7 to 8 HID Media Functions are available. My questions below :
1. How to let USB host to detect which button in the button ladder is being pressed or released ?
2. Does IOP support button ladder?
I have tried to use SetAnalogPinNotify API to generate iop_AnalogPinValue messages when there is a change in GPIO.8 (ADC input) on CP2615. The SetAnalogPinNotify command data sequence I used was :
0x2A, 0x2A, 0x00, 0x09, 0xD3, 0x00, 0x08, 0x00, 0x02
GPIO.8 was configured as ADC input. By turning the potentiometer knob on CP2615 EK2, no message was received. Setting iop_SetDigitalPortNotify for other digital ports all worked fine.
Is there any working demo code available ?
I'm trying to access a serial device through the USBXpress direct API. However, after installing the VCP and USBXpress drivers I don't see the USBXpress device appearing under the USB Controllers in the Windows Device Manager.
Subsequent API calls such as SI_GetNumDevices always return DEVICE_NOT_FOUND.
The USBXpress Device Customization Utility works so the device is not defective. Also, when I plug in the device a Virtual COM port appears.
What could be the reason for the driver not loading?
I have a PCB with a CP2615 but without a CP2112. I can configure the CP2615 by connecting the PCB to a CP2615 eval board with CP2112 and using the Simplicity Studio.
However, this results in my PC recognizing the CP2615 as a playback device when I configured it as a playback and recording device.
It is fully functional as a playback device and when I import the configuration to the Simplicity Studio, it says the CP2615 is configured as a playback and recording device.
This is very confusing and I don't know why this is happening.
Is it possible that CP2615 does not advertise as a recording device if it is not connected to a codec? I do not have a codec on my board.
Could you guide me to find an USBC device for IOS?
I have also some nice to have feature requirements:
1- My application is very power sensitive application. Less Power :)
2- My application requires remote GPIO control. If a device has some extra GPIOs, it is desirable.
Thanks and best regards,
What is the difference between CP2615-EK and CP2615-EK2 ? There seems to be another header in EK2 but are there any other differences? Does EK2 come with A02 by any chance?
Also, what is the difference between CP2615-A01 and CP2615-A02 ? I know the firmware is different but what is different about the firmware? Do they accept difference I2C strings?
I have a USB-C device with a Silicon Labs chip which I'm trying to locate the driver for Windows 7. The VID 10C4 and the PID is F505 and it identifies itself as "billboard device".