CP2102N具有一些其他CP210x器件所没有的附加配置选项。 它们显示在Xpress Configurator的[Advanced Serial Configuration]选项卡中。

这些设置仅适用于Windows和特定的应用。 这些设置适用于以下链接所描述的SERIAL_COMMPROP结构：

https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/ntddser/ns-ntddser-_serial_commprop

[Allowed Baudrates]选项用于设置结构体中的SettableBaud元素，而[Maximum Baudrate]用于设置结构体中的MaxBaud元素

SERIAL_COMMPROP结构体描述了串行端口的功能和属性，并由IOCTL_SERIAL_GET_PROPERTIES请求返回，详见如下所述：

https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/ntddser/ni-ntddser-ioctl_serial_get_properties

针对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分压电阻。

英文原文：https://www.silabs.com/community/interface/knowledge-base.entry.html/2018/10/02/self_powered_cp2102n-2gfe

Question

Do I need to install any driver for CP2615 on Windows?

Answer

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.

Related Article

Manually Install WinUsb Driver on Windows 7

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.

Related Articles:

CP2615 IOP Messages for GPIO.8/ADC Analog Input

There are three IOP messages related to analog pin in AN1139.

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

where:

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.

Question:

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?

Answer:

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:

1. From the Recording tab of the Sound window, select the CP2114 recording device.
2. Click Properties to open the Properties window.
3. Select Levels tab
4. Click the Mute button to turn on/off mute

The Record Mute LED on CP2114 evaluation board will be toggled as well.

Note:

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.

Related Articles

CP2114 B01 vs B02 Package Marking

Question: 

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?

Answer:

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.

• The first way is to execute shell command, the steps are below.

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.

• Another way is using 3rd applications, such as USBView. For the installation and usage of the USBView, please consult this document here https://www.silabs.com/community/interface/knowledge-base.entry.html/2018/07/31/how_to_install_andr-V3kQ.