Q1:Is the VCP driver a Microsoft Windows Universal Driver?
A1: The VCP driver 10.1.1 is a Windows 10 Universal driver for Windows 10 only.
Q2: What are the requirements for a driver to be classified as a "universal driver"?
A2: According to Microsoft, a Universal Windows Driver is a driver that is reilient to installs/updates and runs on all Windows 10 OS Editions. There are four Universal Driver Pillars - Declarative, Componentized, Hardware Support Apps, Universal APIs. If a driver satisfies these requirements (D/C/H/U), it qualifies as a universal driver. Here is a brief description of the pillars -
Declarative - It is possible to install drivers offline.
Componentized - Establishing a core driver for all systems
Hardware Support Apps - Apps are optional and serviced from Widnows Store
Universal APIs - Driver can install and work on any Windows 10 Edition
Q3: What requirements (D/C/H/U) does the VCP driver satisfy?
A3: The VCP driver satisfies all the D/C/H/U requirements.
Q4: Which Windows 10 logo is this driver certified for?
I just installed the latest USB to UART Bridge Virtual COM Port (VCP) drivers on my Mac OSX computer, but system info still depicts the driver version as 1.00. Why?
Answer:
Verifying the driver version number on Mac OSX requires some extra steps. For example, on a MacBook Pro the System Information (or System Profiler) utility may reveal something like this:
At first glance, it appears that the system is using driver version 1.00 to interact with the attached CP2102. However, the version "1.00" string appearing here does not refer to the driver version - it instead refers to the variant of the set of USB descriptors returned to the OS during the enumeration process that occurs between the CP2102 and the USB Host controller when first connected.
On a Mac, the actual VCPdriver version string can be found within some text files - typically located at a path like
Macintosh HD/Library/Extensions/SiLabsUSBDriver.kext/Contents
At this location resides a file of type "*.plist", which is really a text file (with XML content formatting) that you can view in a text editor (textedit). Within this file you'll see elements like "Version 5.0" - these references do indeed indicate the version of the driver installed on your system.
The CP2200 provides the MAC and PHY layer of ethernet. These layers are not aware of which version of the Internet Protocol is being used. The CP2200 can be used with IPV6, it is the responsibility of the software stack to implement IPV6.
Can the CP210x VCP drivers be installed in a way that prevents Windows from prompting for a reboot?
Answer
The requirement to reboot is determined by the operating system as system and driver files may be locked during the driver installation. A reboot may be required to unlock these files for driver update.
Once the CP2614 evaluation board's volume is muted, sometimes turning the volume back up fails. No audio is heard when the volume is turned up.
Workaround
This is a known bug, and the errata for the CP2614 will be updated soon to reflect this. Meanwhile, the workaround is to redo the mute/unmute to get the volume working again. This will be fixed in the next revision of the CP2614.
Every qualified event detected by the CPT112S capacitive sensing input engine generates a single 4-byte packet that can be retrieved by the host processor over the event buffer I2C interface, the event packet is transmitted MSB first.
The device's I2C slave address is configurable through the configuration profile, by default, the address is 0xE0. The device will ACK its slave address only when the interrupt pin is low, signalling that a packet is ready to be read by the host. If the interrupt pin is logic high, the device will not ACK its slave address.
When the device comes out of reset and has not been commanded to enter sensing mode, the device responds to the slave address 0xC0. Additionally, the device will only respond to commands with address 0xC0 if the host drives the interrupt pin low, using the pin as a chip select.
In sensing mode, the device responds to I2C transactions addressed to the slave address stored in the configuration profile.
Interface Knowledge Base
VCP driver - Windows 10 Universal Driver Requirements
Q1: Is the VCP driver a Microsoft Windows Universal Driver?
A1: The VCP driver 10.1.1 is a Windows 10 Universal driver for Windows 10 only.
Q2: What are the requirements for a driver to be classified as a "universal driver"?
A2: According to Microsoft, a Universal Windows Driver is a driver that is reilient to installs/updates and runs on all Windows 10 OS Editions. There are four Universal Driver Pillars - Declarative, Componentized, Hardware Support Apps, Universal APIs. If a driver satisfies these requirements (D/C/H/U), it qualifies as a universal driver. Here is a brief description of the pillars -
Q3: What requirements (D/C/H/U) does the VCP driver satisfy?
A3: The VCP driver satisfies all the D/C/H/U requirements.
Q4: Which Windows 10 logo is this driver certified for?
A4: RS3
Identify the CP210x VCP driver version installed on Mac OSX
Question:
I just installed the latest USB to UART Bridge Virtual COM Port (VCP) drivers on my Mac OSX computer, but system info still depicts the driver version as 1.00. Why?
Answer:
Verifying the driver version number on Mac OSX requires some extra steps. For example, on a MacBook Pro the System Information (or System Profiler) utility may reveal something like this:
At first glance, it appears that the system is using driver version 1.00 to interact with the attached CP2102. However, the version "1.00" string appearing here does not refer to the driver version - it instead refers to the variant of the set of USB descriptors returned to the OS during the enumeration process that occurs between the CP2102 and the USB Host controller when first connected.
On a Mac, the actual VCP driver version string can be found within some text files - typically located at a path like
At this location resides a file of type "*.plist", which is really a text file (with XML content formatting) that you can view in a text editor (textedit). Within this file you'll see elements like "Version 5.0" - these references do indeed indicate the version of the driver installed on your system.
CP2200 compatibility with IPV6
Windows reset prompt when installing drivers
Question
Can the CP210x VCP drivers be installed in a way that prevents Windows from prompting for a reboot?
Answer
The requirement to reboot is determined by the operating system as system and driver files may be locked during the driver installation. A reboot may be required to unlock these files for driver update.
CP2614 does not recover from mute
Problem Description
Once the CP2614 evaluation board's volume is muted, sometimes turning the volume back up fails. No audio is heard when the volume is turned up.
Workaround
This is a known bug, and the errata for the CP2614 will be updated soon to reflect this. Meanwhile, the workaround is to redo the mute/unmute to get the volume working again. This will be fixed in the next revision of the CP2614.
How to retrieve CPT112S event packets through I2C
Every qualified event detected by the CPT112S capacitive sensing input engine generates a single 4-byte packet that can be retrieved by the host processor over the event buffer I2C interface, the event packet is transmitted MSB first.
The device's I2C slave address is configurable through the configuration profile, by default, the address is 0xE0. The device will ACK its slave address only when the interrupt pin is low, signalling that a packet is ready to be read by the host. If the interrupt pin is logic high, the device will not ACK its slave address.
TouchXpress Device Features Comparison
Here is a full feature comparison table for all TouchXpress devices.
I have configured the CPT212B's slave address, but it's not responding to that address. What went wrong?
When the device comes out of reset and has not been commanded to enter sensing mode, the device responds to the slave address 0xC0. Additionally, the device will only respond to commands with address 0xC0 if the host drives the interrupt pin low, using the pin as a chip select.
In sensing mode, the device responds to I2C transactions addressed to the slave address stored in the configuration profile.