The CP2108 comes into three revisions: B01,B02 and B03. The top marking lines are defined as below:
Even there are many information available, the top marking does not indicate anything about the part revision. To determine the revision number we can do by two ways using software.
If you are using a CP2108-EB, you can use Simplicity Studio Debug Adapter to read the revision of the chip. Plug the device into your computer, open Simplicity Studio, and the Debug Adapter window should contain the chip revision.
Another way to get firmware version is to use CP210x_GetFirmwareVersion() function from the CP210xManufacturing.dll. The function will return a firmware version in a major, minor and a build number. The following table shows the firmware version and the corresponding revision number.
Note: the firmware in the following table is in decimal
|Firmware version (Major.Minor.Build)||Revision|
More information about CP210xManufacturing.dll can be found in AN978.
The CP2102N comes in two revisions: A01 and A02. There is no way to determine the entire revision number by looking at the top marking of the chip.
The top marking is divided into three lines, and each line is defined as below:
1. Part Number
2. Manufacture Trace Code
3. Date Code and Letter Revision
Some people may see "A01" in the second line of the top marking, but this is actually part of the trace code and does not indicate anything about the part revision. The only way to determine the revision number is via software. There are two says to do this in software:
1. Simplicity Studio:
If you are using a CP2102N-EB, you can use Simplicity Studio to read the OPN of the chip. Some CP2102N OPNs contain the revision number in it. Plug the device into your computer, open Simplicity Studio, and the Debug Adapters window should contain the OPN.
2. CP210xManufacturing.dll CP210x_GetFirmwareVersion()
If you are using a custom board or the revision number doesn't show up in Simplicity Studio, you can use the CP210x_GetFirmwareVersion() from the CP210xManufacturing.dll. The CP210x_GetFirmwareVersion() function returns a major, minor, and build number. The following shows the corresponding firmware version number and the revision number.
|Firmware Version (Major.Minor.Build)||Revision|
More information about the Manufacturing.dll can be found in AN978.
The MAX13235E transceiver on the CP2102N-EK will not transmit the first bits of data if left idle for more than 30s.
The MAX13235E transceiver on TXD enters AutoShutdown Plus mode after 30s of inactivity on the data bus. Exiting the mode requires a transition edge. The transceiver takes ~40uS to return to normal operation. This will cause incorrect data on the RS-232 side of the transceiver.
To workaround this issue, place the MAX13235E in always-on mode by moving the 1KOhm resistor at R13 to R23.
Problem: A CP2130 device becomes unresponsive after issuing a control command transfer (i.e. Set_GPIO_mode_and_level or other control functions).
Cause: Any active SPI transfer must complete on the SPI bus before the host starts a USB Configuration and Control Commands transfer. This includes reading or writing GPIOs or checking status. USB bus traffic will determine when a transfer reaches the CP2130. Sufficient time must be inserted after SPI transfers for USB bus traffic and the SPI bus transfer itself, before starting any USB Configuration and Control Command transfers.
Since timing for active SPI transfers are not guaranteed, there is no specific min or max wait time required before submitting a control command.
Q1) I have obtained a unique VID/PID combination for my VCP or USBXpress (Direct Access) driver and have contacted Silicon Labs to obtain reseller status, however the package that is shipped to me via Microsoft Dashboard has the Silicon Labs default VID/PID. How do I recertify a driver with my VID/PID combination?
Q2) Changing the VID/PID of the default Silicon Labs driver invalidates the driver signature. I understand that that means I must recertify the driver. Does that also mean that I must rigorously retest the driver prior to recertification?
A1) In the case that you have your own VID/PID combination already, you must customize both your devices and your driver with this VID/PID combination according to AN721: CP210x/CP211x Device Customization Guide and AN220: USB Driver Customization, as well as complete the following steps:
1. Purchase the appropriate certificate from a certificate vendor.
2. Contact Silicon Labs technical support (http://www.silabs.com/support) for reseller status. Please provide the driver used (VCP or USBXpress), driver version, and the WHQL registered company name.
3. Add your certificate to the Microsoft Hardware Dashboard.
4. Add the certificate to the certificate store on your computer.
5. Download a file to sign, sign it, and upload the signed file.
6. Download the DUA shell (a .hlkx file) from the driver shipped to you.
7. Download the signed files. Modify the .inf file as desired. (Or upload the modified .inf output of AN220: USB Driver Customization Software. This is how you can create a customized driver using your VID/PID combination.)
8. Download and install the latest version of HLK Studio. Open HLK Studio.
9. Change to the package tab. Right click on the driver and choose [Replace Driver]. Choose a folder with the signed driver files and your modified .inf file.
10. Click [Create Package].
11. Sign from the certificate store on your computer. Save the .hlkx file.
12. In the Microsoft dashboard, click [Upload New] and choose your new .hlkx file.
You can find greater detail on this list of steps in AN807: Recertifying a Customized Windows HCK Driver Package, including illustrative screenshots.
A2) Many driver customizations, including changing the VID/PID, product and manufacturer strings, and other minor changes require modification of the .inf file only and do not affect the binary executable or functional portion of the driver. In such cases the resigning process is eligible for re-certification as Driver Update Acceptable (DUA), which is a streamlined re-certification process that does not require the detailed testing that Silicon Labs must undergo for the initial submission of the original driver that Silicon Labs ships to customers via the Microsoft dashboard. Please follow the steps outlined above and in the linked documentation and customization utilities to complete the process.
首先，CP210x驱动程序v10.1.1是Windows Universal驱动程序。 有关此驱动程序的更多信息，请参阅此KBA - https://www.silabs.com/community/interface/knowledge-base.entry.html/2017/12/27/vcp_driver_-_windows-Ulur.
CP210x驱动程序v6.7.5目前是“传统”驱动程序，可以在Windows 7, 8和10上使用。两个版本的驱动程序之间的差异体现在以下方式:
这写差异可以通过release notes文档获取，可以从此链接获取 - https://www.silabs.com/documents/public/release-notes/CP210x_Universal_Windows_Driver_ReleaseNotes.txt
驱动程序版本v6.7.5适用于Windows 7及更高版本的“桌面”系统，即Windows 7, 8, 8.1和10.请注意，这些驱动程序仅适用于“桌面”系统，即PC和服务器。 Windows v10.1.1是一个通用的Windows驱动程序。 微软在Windows 10中引入了“Universal”。“Universal”表示支持Universal的Windows桌面系统，嵌入式系统和移动操作系统等版本，即Windows 10。有关Universal驱动程序的更多信息，请参阅Microsoft的文章 - https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/getting-started-with-universal-drivers。 SiliconLabs社区论坛上的KBA提供了有关Universal驱动程序的更多信息，特别是驱动程序v10.1.1 - https://www.silabs.com/community/interface/knowledge-base.entry.html/2017/12/27/vcp_driver_-_windows-Ulur。
在v6.7.5中使能了Serial Enumeration，而v10.1.1未启用Serial Enumeration。关于Serial Enumeration的介绍请参阅https://www.silabs.com/community/interface/knowledge-base.entry.html/2016/01/13/what_is_the_seriale-ZSIi
从技术上讲，驱动程序版本v6.7.5几乎是一个“legacy”驱动程序。 Windows和Silicon Labs计划未来仅使用v10.1.1并对该版本的驱动程序进行更新（如有必要）。
CP2102N具有一些其他CP210x器件所没有的附加配置选项。 它们显示在Xpress Configurator的[Advanced Serial Configuration]选项卡中。
[Allowed Baudrates]选项用于设置结构体中的SettableBaud元素，而[Maximum Baudrate]用于设置结构体中的MaxBaud元素
针对SERIAL_COMMPROP结构体对CP2102N做的这些配置对设备的行为没有直接影响。 例如，如果 [Maximum Baudrate] 设置为300，应用程序仍然可以请求更高的波特率，并且CP2102N能够支持请求。由应用程序读取SERIAL_COMMPROP结构，并决定是否阻止用户请求在该结构体中不支持的波特率。
我使用的是CP2102N，还有一个外部的3.3 V稳压器，用于为VREGIN和VDD提供3.3 V电压。 我将VBUS引脚连接到USB 5 V。 VBUS是否需要分压电阻来降低输入电压？ 或者，是否支持将VBUS引脚连接到3.3V稳压器输出引脚这样的配置？如果是，可以去掉VBUS上分压电阻吗？
如果上述电源配置是自供电配置，那么VBUS引脚上的需要分压电阻。 采用分压电阻的这种电源配置如CP2102N数据表第9页的图2.6所示。 请注意，在任何供电模式下（无论是自供电还是总线供电），USB的VBUS信号连接到CP2102N VBUS的引脚都需要分压电阻（如图2.6所示），以避免VBUS上可能出现的过压情况（参见https://www.silabs.com/community/interface/knowledge-base.entry.html/2018/03/31/cp2102n_requiresav-NFly）。
至于VBUS引脚连接到VDD和VREGIN的相同3.3V电源，只要CP2102N上的稳压器被旁路（即VDD = VREGIN =外部提供的3.3 V），该配置应该是可接受的。下面这种情况下不支持：如果器件是自供电的，内部稳压器用于为VDD供电（例如，如果USB 5V VBUS信号连接到VREGIN），VDD上升时间的延迟可能会导致其超出了VBUS PIN上最大额定电压的限定。 在这些情况下，都应使用VBUS分压电阻。
Do I need to install any driver for CP2615 on Windows?
CP2615 USB digital audio bridge is a composite USB device that provides three USB interfaces:
1. USB Audio Class 1.0 to I2S digital audio bridge
2. USB HID Class consumer control device for volume and mute synchronization
3. Vendor specific USB serial data bridge using CP2615 I/O Protocol
The USB HID and digital audio interfaces are standard class implementations and natively supported by most operating systems, no custom driver needed.
The CP2615 serial I/O USB interface uses bulk transfers, and WinUSB driver is required for Windows platform. However, some user may observe one of CP2615 interface cannot enumerate successfully on Windows 7 which the WinUSB driver has not been installed properly. In this situation, you need to install the WinUSB driver by yourself if you want to use this interface. For more information on how to install the WinUSB driver, please see here.
Below is the CP2615 device viewing in Device Manager on Windows 7 with WinUSB driver installation.
Question 1: CP2615 GPIO.9/Buttons can be configured to report common consumer control buttons through HID interface, do the same predefined buttons can be assigned to more than one slot?
Answer: Yes. The HID media buttons can be assigned to more than one slot using Xpress Configurator. When the feature is enabled, USB Host can see the predefined HID consumer reports when associated buttons are pressed. Here note that the report will not contain any slot number information, hence host does not know which slot generated the report.
Question 2: Is GPIO.9/Buttons readable through CP2615 IO Protocol?
Answer: No CP2615 IOP message supports reading GPIO.9/Buttons pin state directly per AN1139. However, there are three IOP messages related analog pin input, GPIO.8/ADC analog input pin, user can use these IOP messages to read the current voltage on GPIO.9/Buttons pin by tying GPIO.8 to GPIO.9 together if desired.
For more information about the GPIO.9/Buttons connection, please see the GPIO section in CP2615 Datasheet.
There are three IOP messages related to analog pin in AN1139.
Configure automatic reporting of analog pin.
Report current analog pin value.
|CP2615||Current analog pin value|
These IOP messages are intended to be used for CP2615 GPIO.8/ADC analog pin only, see AN1139 for more details about the format of these messages.
When USB host sends these API commands, the first parameter 'PinNumber' for iop_SetAnalogPinNotify (0xD300) and iop_GetAnalogPin (0xD301) must be set to 0. It is invalid for the two commands if the pin number is set to other values.
The ADC analog value message returned by iop_AnalogPinValue looks as below:
0x2A 0x2A 0x00 0x0D 0xA3 0x01 pp vv vv tt tt tt tt
0x2A2A is the preamble of CP2615 IOP message
0x000D is the total message length for this message (header + message payload)
0xA301 is the ID of iop_AnalogPinValue message
pp is the analog pin number, here it is 0x00
vv vv is the current value read from the analog pin, 10-bit right-justified, full-scale VDD corresponds to 0x03FF.
tt tt tt tt is 32-bit timestamp, MSB, 1 ms resolution
The CP2615 GPIO pins can be configured using Xpress Configurator in Simplicity Studio. Ensure the GPIO.8 is set as ADC input when using these IOP messages, otherwise host will not receive analog notification if it is configured as GPIO function, although the GPIO.8 is set to ADC input by default.
I am using the CP2102N and I have an external 3.3 V regulator that is used to supply 3.3 V to VREGIN and VDD. I have the VBUS pin connected to the USB 5 V. Do I need a voltage divider for VBUS to reduce the input voltage? Alternately, is connecting the VBUS pin to the 3.3 V regulator output a supported configuration, and if so, can the required voltage divider on VBUS be omitted?
The power configuration described above is that of a self-powered configuration, and requires a voltage divider on the VBUS pin. This power configuration, with the voltage divider, is shown in Figure 2.6 on page 6 of the CP2102N datasheet. Please note that any power configuration (self or bus-powered) in which the USB VBUS signal is connected to the CP2102N VBUS pin requires a voltage divider (as shown in Figure 2.6) on VBUS to avoid a possible overvoltage condition on VBUS (see https://www.silabs.com/community/interface/knowledge-base.entry.html/2018/03/31/cp2102n_requiresav-NFly).
As for the connecting of the VBUS pin to the same 3.3V supply connected to VDD and VREGIN, this configuration should be acceptable as long as the regulator on the CP2102N is bypassed (i.e. VDD = VREGIN = externally supplied 3.3 V). If the device is self powered with the internal regulator used to supply VDD (for instance if the USB 5 V VBUS signal is connected to VREGIN), the delay in the rise time of VDD may cause a violation of the maximum voltage rating on the VBUS pin, which is not supported. In these cases, the VBUS voltage divider should be used.
Problem: Couldn't recognize CP2615 as output audio device in Mac OS when configured for 24-bit-only output.
Root cause: The failure to enumerate is due to the Mac OS not tolerating the Interface 3 Alt 1 zero-bandwidth descriptor that is sent by the CP2615 when configured for 24-bit-only operation. The presence of this zero-bandwidth descriptor is not prohibited by the USB standards and is tolerated by other operating systems (Windows, Linux, Android).
Workaround: The problem can be avoided by configuring the CP2615 Audio Out interface for 24/16 bit operation, instead of 24-bit-only. This just adds the 16-bit capability in addition to 24-bit, so there is no loss in the quality. 24-bit source material will still be sent over USB as 24 bits; the only difference is that 16-bit source material will get transmitted across USB as 16 bits, rather than being artificially padded to 24 bits as it would if the CP2615 was configured for 24-bit-only operation. (Padding 16-bit audio to 24-bit does not increase its actual resolution, it just wastes USB bandwidth.)
CP2114 supports record mute by USB host or GPIO pin. CP2114 mutes Record when the USB host sends an Audio Class-Specific request SET_CUR (0x01) to mute the Record audio. In addition, single-pressing the Record Mute button (GPIO.0 by default) will toggle between record mute and unmute states. The Record Mute LED (GPIO.4 by default) is turned on/off accordingly for both control methods.
For Windows machine, the CP2114 device record can be muted with following steps:
The Record Mute LED on CP2114 evaluation board will be toggled as well.
1. Record Mute controlled by Host PC is available for CP2114-B02 revision only. See CP2114 Errata for more information.
2. Record functionality must be enable. User can test with the index 0 of preprogrammed configuration by installing all jumpers of GPIO.5 ~ GPIO.8 on the CP2114 EVB.
Table 3.13 in the CP2615 Datasheet (captioned "Read CP2615 Firmware Revision") depicts an operation available in Configuration Mode to read the Firmware Version Number. How does the value obtained by this sequence map to a CP2615 firmware revision?
The CP2615-A02 firmware version number consists of an ASCII-encoded null-terminated string in the format 2615.x.y.z, where 'x', 'y', and 'z' comprise the firmware version number, and can be one or more characters each. The following table illustrates the data returned by reading 16 bytes from address 0xFFFB on a CP2615-A02 device:
The CP2615-A01 device does not have its firmware version encoded as described above. For the -A01 device, reading 16 bytes from address 0xFFFB returns the following data
For more information, including an alternative means to determine the revision of a CP2615 device (suitable for an end-user situation, e.g. where an app running on the phone or USB host would query the version number), see the KB article "Methods to determine CP2615 revision".
When a CP210x device is connected to the USB host, the host will send a reset signal to the USB device to start the enumeration process. After reset, the host will read the USB device’s information and assign a unique address. If USB host has the driver for the device, the driver will be loaded after enumeration done.
Sometimes the USB enumeration may fail because of bad USB signal quality, incorrect USB driver for the specified VID/PID device, etc. So, it is important to check if the CP210x device is enumerated successfully.
This KBA introduces two methods for checking this.
a) Connect the CP210x device to USB host on Linux.
b) Start a terminal on Linux, type “lsusb” and press Enter. There will be one more USB devices, take the CP2104EK as an example, it named CP210x UART Bridge / myAVR mySmartUSB light (it's a wrong name because of Ubuntu OS, it should be "Silicon Labs CP210x USB to UART Bridge") in my case. The hex value 10c4:ea60 represents VID and PID as shown below. The PID and product name may different if the device is customized.
c) Typing“lsusb -d VID:PID -v” and press Enter, it is “lsusb -d 10c4:ea60 -v” in my case. Then the CP210x device descriptor will be printed out on the screen. By checking the descriptor information we should know if the device has been correctly enumerated. However, if all the data is zeroes (0x0000, for example) or if an error is reported, the device did not properly enumerated.
USBView is a graphical user interface application that enables you to browse USB controllers and connected USB devices on your computer. It displays the information on each of the USB devices (like VID, PID, Product String, descriptors, etc.). The driver for the device does not need to be installed or loaded for USBView to read the information, as the utility uses the low-level USB driver to talk to the device. This is useful when a CP210x is not enumerating because of an incorrectly programmed PID.
You can run USBView by double-click a USBView.exe package on Window. But there is difficulty to run it on Linux. This article will explain how to install and run USBView on Ubuntu.
Gtk3.0 is required for running USBView, you can install gtk3.0 by typing below command and press Enter on terminal.
$ sudo apt-get install libgtk-3-dev
The Ubuntu website provides a .deb package and source code of USBView, you can download it from following link: http://manpages.ubuntu.com/manpages/trusty/man8/usbview.8.html. If you choose to install USBView with .deb package, you can finish it just by double-click .deb package. If you want to install it with source code, you should extract the source code package and enter the extracted directory, then follow three steps to install it.
$ sudo ./configure $ sudo ./make $ sudo ./make install
After installation, you will see the following directory structure.
Running the USBView by typing “sudo ./usbview”, and the graphical display of connected USB devices are shown as below.
Detailed information may be displayed by selecting individual devices in the display.
Some CP210x devices include GPIO pins that can be controlled at runtime. This article discusses reading and writing the latch value of these pins with software on different operating system platforms.
Before connecting to a device, the host must install relevant VCP driver, you can get the appropriate installation package from the link below:
After installing the VCP driver, the CP210x device is recognized by the host when it was plugged in the host USB port. Silabs offers a CP210x Port Read/Write Example application to read/write GPIO latch at runtime.
Taking CP2104EK as testing platform to show how to read/write the GPIO by the CP210x Port Read/Write Example, the CP210x Port Read/Write Example application can be found in AN223SW. Besides, reading AN223 for more information, you can get both of them from the website here https://www.silabs.com/community. we will write value to GPIOs and then read it back by three steps blow.
The CP210x Port Read/Write Example illustrates how the GPIO latch can be read from and written to device by using the CP210xRuntime.DLL. You can develop a custom application using CP210xRuntime.DLL, the functions in this API (CP210xRT_ReadLatch() and CP210xRT_WriteLatch()) give host-based software access to the CP210x device’s GPIO latch using the USB connection.
The CP210x driver has been distributed as part of the Linux kernel since v2.6.12, and GPIO operations also be supported by Linux 4.10.0 kernel or later.
If you are using an older kernel version, please download the latest Linux VCP driver from link below and merge the GPIO operation related source code into your kernel. The .zip package contains VCP driver and example code show how to control GPIOs.
After merging the VCP driver cp210x.c, compile it with make command and install it with command "insmod ". Note that the command "rmmod cp210x.ko" should be executed if VCP driver already exists before installing the driver that support GPIO control.
In the cp210x_gpio_example.c, use the following function to open a CP210x device.
fd = open("/dev/ttyUSB0", O_RDWR | O_NOCTTY | O_NDELAY);
Use the function below to read latch, where the third parameter gpioread is a buffer address of one-byte length for storing the read latch value.
ioctl(fd, IOCTL_GPIOGET, &gpioread);
The returned read latch value is represented as follows: bits 0–7: Current latch state, where bit 0 is GPIO0, bit 1 is GPIO1, etc. Up to GPIOn where n is the total number of GPIO pins the interface supports.
Use the function below to write latch, where the third parameter gpio is write latch value.
ioctl(fd, IOCTL_GPIOSET, &gpio);
The write latch value that is supplied in the Data phase represents as follows:
bits 0–7: Mask of the latch state (in bits 8-15) to write, where bit 0 is GPIO0, bit 1 is GPIO1, etc. Up to GPIOn where n is the total number of GPIO pins the interface supports.
bits 8–15: Latch state to write, where bit 8 is GPIO0, bit 9 is GPIO1, etc. Up to GPIOn where n is the total number of GPIO pins the interface supports.
Get more information from AN571.
Compile the application with “gcc cp210x_gpio_example.c”, a executable file “a.out” is generated. Execute it with “./a.out”.
The Mac VCP driver v5.0 or later version supports the GPIO control on the CP210x devices. Download the latest driver here:
https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers. We can control the GPIO pins with python.
For using the python, you should install libusb and Pyusb library on your Mac machine, please refer to the following code to write a Python script to control the CP210x GPIO.
import time import usb.core import usb.util PID = 0xea60 VID = 0x10c4 dev = usb.core.find(idVendor=VID, idProduct=PID) if not dev: print "CP2104 was not found :(" exit(1) print "Yeeha! Found CP2104" reqType = 0x41 bReq = 0xFF wVal = 0x37E1 while True: wIndex = 0xffff print "toggling On" dev.ctrl_transfer(reqType, bReq, wVal, wIndex, ) time.sleep(5) print "toggling Off" wIndex = 0x00ff dev.ctrl_transfer(reqType, bReq, wVal, wIndex, ) time.sleep(5)
You can learn more through this video from Lady Ada.
The python script is also suitable for other OS including Window and Linux.
The CP2102N has some additional configuration options that are not available on other CP210x devices. These are displayed in the [Advanced Serial Configuration] tab in Xpress Configurator.
These settings are Windows only and application specific. These settings apply to the SERIAL_COMMPROP structure described here: https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/ntddser/ns-ntddser-_serial_commprop
The [Allowed Baudrates] options set the SettableBaud element in this structure, while the [Maximum Baudrate] sets the MaxBaud element in the structure.
The SERIAL_COMMPROP structure describes the capabilities and properties of the serial port, and is returned by the IOCTL_SERIAL_GET_PROPERTIES request, described here: https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/ntddser/ni-ntddser-ioctl_serial_get_properties
These settings for this SERIAL_COMMPROP structure have no direct impact on the device's behavior. For example, if the [Maximum Baudrate] is set as 300, an application can still request a higher baudrate, and the CP2102N will happily oblige. It's then up to the application to read the SERIAL_COMMPROP structure and then prevent the user from requesting baudrates that are set to be not supported.
Using CP210x in Linux embedded platform, when host sends requests to CP210x, it returns below error:
"cp210x ttyUSB1: failed set request 0x7 status: -32"
How to interpret the error message?
Table 6 Interface Commands in AN571 lists all API commands that CP210x device supports. Viewing from this Table, request of 0x7 represents SET_MHS command, which is used to set modem handshaking (DTR and RTS lines) states.
The negative error is returned by the underlying call to usb_control_msg() from the cp210x.c driver.
If this function is not successful, a negative error number is returned.
How does CP210x handle the SET_MHS request from host?
For CP210x SET_MHS (0x07) command, as AN571 stated, the DTR and RTS values can be set only if the current handshaking state of the interface allows direct control of the modem control lines.
When the device receives the SET_MHS command intending to change the state of DTR or RTS pin, CP210x device will then check current Flow Control setting in the device base on the SET_FLOW() from host, and then make a different response.
If the hardware Flow Control is currently enabled, it means the handshaking lines have been managed by the CP210x device itself rather than host, the device will not response the current SET_MHS request, and a STALL would be returned.