USB转串口驱动：CH34X&CP2102

RELEASE NOTES ============= Silicon Labs Virtual COM Port (VCP) Universal Driver for Windows 10 Package version: 10.1.8 Release date: 2019-06-24 This package contains a Virtual COM Port Universal driver for Microsoft Windows 10 for use with Silicon Labs VCP USB Serial Bridges. These devices include the CP2102N, CP2102, CP2103, CP2104, CP2105, CP2108, CP2109. OS VERSIONS ----------- This package provides the CP210x VCP driver for the following versions of Windows: - Windows 10 (x64, x86) CHOOSING VCP DRIVER VERSION --------------------------- VCP drivers of version 10.0.0 and later are released for Windows 10 as Universal Drivers. This means they do not work on older version of Windows such as Window 7 and 8.1. You should use this driver if you only need support for Windows 10, or you need the Universal driver. If you require support on older versions of Windows, you should use the legacy VCP driver which can be found on the Silicon Labs web site. The legacy Windows VCP drivers have version numbers less than 10.0.0. CONTENTS -------- The VCP driver package contains the following files and directories: - silabser.inf -- Driver information file - CP210xVCPInstaller_x64.exe -- 64-bit installer - CP210xVCPInstaller_x86.exe -- 32-bit installer - SLAB_License_Agreement_VCP_Windows.txt -- Software License - CP210x_Universal_Windows_Driver_ReleaseNotes.txt -- this file Additional files needed by installer - dpinst.xml - silabser.cat - x64/silabser.sys - x86/silabser.sys INSTALLING ---------- The VCP driver is automatically installed by Windows Update for CP210x with alternate PID values of 0xEA63, 0xEA7A, and 0xEA7B. These are not default values. Otherwise, unzip the .zip file and you will have a directory containing the driver installer files. ### Prompted install ### If Windows prompts you to install a driver for a CP210x device (for example, if you plug a CP210x into your computer): 1. Use the dialog to browse for the driver location 2. Locate the driver folder (that you previously unzipped) 3. Follow the instructions ### Manual install ### 1. Using Windows File Explorer, locate the driver folder (that you previously unzipped) 2. Determine if you have 32-bit or 64-bit Windows 3. Double click to run the .exe file named CP210xVCPInstaller_xnn.exe (where xnn is x64 for 64-bit and x86 is for 32-bit) 4. Follow the instructions UNINSTALLING ------------ 1. The device must be plugged in 2. Run Device Manager 3. Locate the device you want to uninstall 4. Right click on the device and choose "uninstall" 5. Follow the instructions SUPPORT ------- For technical support please visit the Silicon Labs support site: https://www.silabs.com/support ****************************************************************************** RELEASE NOTES FOR 10.1.8 (2019-06-24) Changes for VCP Driver ============================================================================== MCUSW-412 | Certified for Windows 10 RS6. MCUSW-484 | WDFVERIFY() added to the driver. Configurable via Registry. MCUSW-495 | Clear RTS on CloseHandle(). MCUSW-508 | IOCTL_SERIAL_GET_COMMSTATUS refactored to reduce USB-bus | bandwidth, while still offering timely reporting. MCUSW-518 | WDFVerifier parameter ForceLogsInMiniDump Registry parameter | added for improved supportability. MCUSW-519 | Resolve an SDV-identified issue: do not double-complete a | Request on error paths. MCUSW-526 | Creates the framework USB device object with client contract | version USBD_CLIENT_CONTRACT_VERSION_602/0x602 (I.e. Register | with "new" (to Windows 8) Windows USB driver stack). ****************************************************************************** RELEASE NOTES FOR 10.1.7 (2019-03-26 (DriverVer = 03/26/2019,10.1.7.2399)) Changes for VCP Driver ============================================================================== MCUSW-473 | Fix length of nul-terminated legacy Dos Name string written to | HARDWARE\DEVICEMAP\SERIALCOMM Registry key. MCUSW-483 | Fixed bug for Max Baud rate for CP2101, CP2104, CP2105 and | CP2108 devices. ****************************************************************************** RELEASE NOTES FOR 10.1.6 (2019-03-19 (DriverVer = 03/15/2019,10.1.6.2388)) Changes for VCP Driver ============================================================================== MCUSW-445 | Fix a blue-screen system crash bug with handling of ioctl | IOCTL_SERIAL_WAIT_ON_MASK during power state changes. ****************************************************************************** RELEASE NOTES FOR 10.1.5 (2019-02-19 (DriverVer = 02/19/2019,10.1.5.2368)) Changes for VCP Driver ============================================================================== MCUSW-414 | Implement an undocumented Registry-configured feature to ignore | IOCTL_SERIAL_PURGE. MCUSW-417 | Read many of the Registry "parameter"-type settings first from | the "parameters key" and then from the "hardware key", with the | "hardware key" taking precedence (allows "driver wide, all | devices" setting, but provides the capability to specify per- | device settings (before we only supported per-device | settings)). | MCUSW-439 | Fixed a bug whereby Close()-Open() on a CP2102N could get USB | data toggle confused (I.e. issue USB CLEAR_FEATURE(HALT) to | bulk endpoints to reset data toggle back to DATA0). MCUSW-449 | Fix a Max Baud Rate bug (use device-specific MaxBauds (from the | data-sheets): 3 Mbaud for CP2102N, 1 Mbaud for all other CP210x | devices.). MCUSW-450 | Fix Verification BSOD (race condition in the VCP device driver | that can cause double completions): Only call | DetachForCompletionUNcancelable on success of UNmark as | cancelable in handling of IOCTL_SERIAL_WAIT_ON_MASK-related | requests. ****************************************************************************** RELEASE NOTES FOR 10.1.4 (2018-12-07 (DriverVer = 11/26/2018,10.1.4.2290)) Changes for VCP Driver ============================================================================== MCUSW-134 | Fixed an issue with handling of IOCTL_SERIAL_SET_WAIT_MASK, | IOCTL_SERIAL_WAIT_ON_MASK, with the SERIAL_EV_RXCHAR event and | data arriving from the device into the driver. Previously, an | indication of arriving data was made before making the data | available, causing, in some conditions, subsequent requests for | data after notification of data available to not deliver any | data. MCUSW-144 | Onecore-based editions of Windows 10 (I.e. Windows 10 IoT Core) | do not, by design, create PortName entries in the Registry to | specify the device's legacy DOS name (I.e. COM<n).