My unsigned, customized driver with GUI installer will not install on Windows XP 32-bit.
Customized VCP driver v6.6 and USBXpres driver v3.3 generated by Application Note software AN220SW use Microsoft's DPInst installer. This installer differs from the installer used in previous versions of the VCP and USBXpress driver.
Enable the legacyMode configuration flag. This can be done via command line when calling the installer executable or via a modification to the DPInst installer XML file:
After resetting the CP2114, why is it sometimes necessary to change the CP2114 volume and/or mute settings to hear playback audio?
On bootup, the CP2114 audio output volume is set to minimum and is muted. The first time the CP2114 is connected to a Windows machine, the Windows audio volume and mute are set accordingly (minimum volume and muted). Thereafter, when Windows detects the CP2114 device insertion it will apply the most recent volume and mute settings. If the CP2114 is disconnected from the system or held in reset for several seconds, Windows recognizes the device removal and insertion events and properly sets the CP2114 volume and mute to their previous settings. However, if the CP2114 is reset from the application software or by quickly pressing and releasing the RESET switch, Windows may not recognize the device removal and re-insertion and will not re-apply the most recent volume and mute settings. Since the CP2114 boots up with volume set to minimum and muted, there will be no playback audio even though the Windows volume and mute controls appear to be at their previous settings. In this case it is necessary to change the Windows volume and mute settings manually so that these settings are sent to the CP2114.
Why does the CS42L55 audio output clip when playing full-scale waveforms at high volume levels?
The clipping is due to a CS42L55 configuration setting that is easily changed. The CS42L55 default configuration specifies the Headphone and Line Out amplifier power supply to be VCP/2. Creating a new configuration that specifies VCP allows the CS42L55 to reproduce full-scale signals at high volume without clipping.
The reason that the CP2114 default CS42L55 configuration specifies VCP/2 rather than VCP is to accommodate the limited current sourcing capability of the Camera Adapter used in conjunction with the iPad. When driving the CP2114/CS42L55 with an iPad and Camera Adapter and playing high-amplitude audio at high volume with the CS42L55 CODEC configured at maximum output capability (VCP), the momentary short that can occur when plugging into the 3.5mm headphone jack could cause the iPad to report that the USB device draws too much power. This situation does not occur when the CP2114 is connected to a standard USB host port.
"CP2114_config_0A_CS42L55.txt" is a pre-build configuration which sets the LineOut amplifier to VCP allowing 0dB FS audio without clipping. It can be found in the supplemental Coded configurations here:
Where can I find the factory-programmed and supplemental CP2114 configurations?
The CP2114 website has text files for the three factory-programmed configurations as well as numerous supplemental configuration files. These files can be used as-is or can be modified to meet exact requirements. The CP2114 website can be found here: www.silabs.com/CP2114
How do I make the USB driver choose a lower com port?
For development with the EM260 serial, I am using Cygwin for my host. As I plug in my USB to serial device, it keeps showing up at an increasingly higher COM port. How do I clean out the old COM port information?
From your Windows machine, begin the regedit program (start->run->regedit). Search for HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionPorts and clean out all the lower COM port entries.
How do I manually uninstall the CP210x VCP driver?
The CP210x VCP driver should be uninstalled through the Windows Control Panel to avoid registry corruption.
However, in some cases you may want to manually uninstall the CP210x VCP driver to ensure a complete removal and repair a corrupt installation. To do so:
Uninstall the driver using Device Manager a) Ensure that your VCP device is connected to the system, so that it appears in Device Manager. b) Select the VCP device, right click, and select "Uninstall". c) Check "Delete the driver software for this device." checkbox if available; this will remove the driver from the Windows Driver Store. d) Click OK.
Unplug the VCP device from your system a) Decline or Cancel any subsequent attempts by Windows to reinstall drivers for the VCP device b) Now that you've uninstalled the VCP device via Device Manager, physically disconnect it
Uninstall the driver using Control Panel (Add/Remove Programs or Programs and Features) a) Uninstall any driver entries such as "Silicon Laboratories CP210x USB to UART Bridge (Driver Removal).
Remove INF files a) Browse to the folder: C:\WINDOWS\inf. b) Look through each OEMxx.inf file, and if it references a CP210x remove it and its corresponding PNF file. The default INF files will have slabbus.inf, slabw2k.inf (4.40) or silabser.inf (5.x, 6.x) in the comments at the top of the file. Customized INF's will have xxxxbus and xxxxw2k.inf at the top depending on the name given.
Remove driver files a) Browse to the folder: C:WINDOWS\system32\drivers. b) Remove the files: slabbus.sys, slabcm.sys, slabcmnt.sys, slabser.sys, slabwh.sys (4.40) or silabser.sys, silabenm.sys (5.x, 6.x).
Remove Registry keys: a) Go to Start->Run... and type "regedit". b) Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ (32-bit OS) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ (64-bit OS). The default uninstall key is SLABCOMM&10C4&EA60. Any custom drivers will be of the form SLABCOMM&&. Delete these entries to get rid of the "Add/Remove Programs" entry. c) Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Silicon Laboratories, Inc.\Silicon Laboratories Driver Installations\VCP CP210x Cardinal\ (32-bit) or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Silicon Laboratories, Inc.\Silicon Laboratories Driver Installations\VCP CP210x Cardinal\ (64-bit). The default installation status key is SLABCOMM&10c4&ea60. Any custom drivers will be of the form SLABCOMM&&. Delete these entries to get rid of the proprietary driver installation records. d) Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\. Delete the slabbus and slabser keys (4.40) or the silabser and silabenm keys (6.x/5.x). These are the services for the driver. Deleting these does not stop the driver service - you must reboot immediately after this, otherwise the services are not unloaded.
Windows will assign a COM port number that is the next free COM port in the list.
For example, if you attach a CP210x to a machine with three hardware COM ports and have never attached a CP210x or other virtual COM port prior, the CP201x will show up as COM4. From that point on, whenever a CP20x with the same VID, PID, and serial string is attached, it will come up as that same COM port number.
What are the supported EMIF bus widths? Can the EMIF operate in 8-bit address mode?
When operating in non-multiplexed mode, the address size is fixed to 16 bits and data size is fixed to 8 bits.
When operating in multiplexed mode, the address and data width of the EMIF is controlled by the EMIFWIDTH bits in the device Port Configuration module. The default size for both after a reset is 8 bits, which can be expanded to 24 bits of address and 16 bits of data. The data width is controlled separately using the BUSWIDTH bit in the EMIF interfaces (EMIFIF).
Do the CP210x or Silicon Labs USB MCU devices have USB On-The-Go capabilities?
The CP210x or Silicon Labs USB MCU devices cannot operate as USB Hosts or Hubs. They are only USB peripheral devices and do not have USB host / hub capabilities. They do not have USB 'On-The-Go' (OTG) capabilities, as that requires the ability to act as a USB host.
Yes, multiple CP2400 LCD controllers can be cascaded in order to drive several LCDs on the board (each LCD with its own set of COM pins). The devices may share the same SCK, MISO, and MOSI lines, although each device will require its own NSS signal.
Multiple CP2400 LCD controllers cannot be combined to control a single LCD with more than 128 segments, as this would require sharing of the COM pins.
How do I access a CP210x device after installing the Mac OS VCP drivers?
The Silicon Labs CP210x Mac OS X Virtual COM Port (VCP) driver creates a standard 'tty' serial port on the Mac. The port is named '/dev/tty.SLAB_USBtoUART'. This port can be used just like any standard hardware serial port.
Can I write/erase FLASH through a Silicon Laboratories MCU serial interface such as UART, SPI, or I2C? Can I connect to the IDE and debug the device through one of these interfaces?
Silicon Laboratories devices have the ability to read, write, and erase on-chip FLASH. This feature enables the user to execute firmware that can reprogram parts of codespace. Firmware can use this feature in coordination with a serial interface such as UART, SPI, or I2C to 'bootload' the device. Bootloading requires that some region of codespace be reserved for bootloader firmware. Bootloader firmware the communicates across a serial interface with a host controller, and the host drives the process by transmitting the application firmware image to be bootloaded.
In order to program FLASH through one of the serial interfaces, bootloader firmware must be pre-programmed into the device. This pre-programming step must be accomplished through the device's dedicated debug interface. For most devices, this is the C2 interface. After programming the bootloader region of codespace through the debug interface, an in-system host can perform all future Flash programming using the serial interface allocated by the bootloader firmware.
The Silicon Laboratories debug adapter can only communicate with the debug interface on devices. This means that the debug adapter cannot use a device's UART, I2C, or SPI interfaces to perform debug and development tasks such as code downloading and breakpoint control.
I successfully re-certified the CP210x drivers and received the *.cat file from WinQual. What do I do with this file to certify the drivers?
The *.cat file received from WinQual should be placed in the same directory as the *.inf file. The *.inf file specifies the location of the driver files (*.sys), which may or may not be in the same directory. After placing the *.cat file in the same directory as the *.inf file, Windows will automatically recognize that the driver is certified when a user attempts to install it.