最終更新:2016-03-23 (水) 14:15:08 (2956d)  

USB20CV
Top / USB20CV

USB 2.0 Command Verifier

http://www.usb.org/developers/tools/

USB20CV is the compliance test tool which evaluates High, Full and Low-speed USB devices for conformance to the USB Device Framework? (Chapter 9), Hub device class (Chapter 11), HID class, and OTG specifications. Also included are mass storage class and USB video class specification tests. All USB peripherals are required to pass the Device Framework tests in order to gain certification. The other tests are mandatory for certification when supported. If you have installed a previous version of the USB 2.0 Command Verifier, you must uninstall it before installing the new version

インストール時の注意

履歴

  • USB20CV R1.4.16.2
    USB20CV R1.4.15.02015/04/02
    USB20CV R1.4.10.2
    USB20CV R1.4.10.12013/09USB20CV tool is supported on Windows 7 and Windows 8 only. It is no longer supported on Windows XP
    USB20CV R1.4.9.7Windows XP SP2?,Vista/7 UAC off
    USB20CV R1.4.9.2Windows XP SP2?,Vista/7 UAC off
    USB20CV R1.4.4.12011/05
    USB20CV R1.4.3.0
    USB20CV R1.4.2.32010/07Windows XP SP2?,Vista/7 UAC off
    USB20CV R1.3.5.7Windows XP SP2?,Vista/7 UAC off
    USB20CV R1.3.5.6Windows XP SP2?,Vista UAC off
    USBCV R1.3.2
    USBCV R1.3.1
    USBCV R1.32006/11/20Windows XP SP2 only
    USBCV R1.2.12003/08
    USBCV R1.22003/06
    USBCV R1.12002/122000/XP

動作環境

  • USB 2.0 Command Verifier (USB20CV) is a new tool that replaces the old USBCheck?. This tool has been tested on Windows 7, Windows 8 and Windows 8.1 with the latest service packs and updates installed in each case.

署名

メモ

  • http://noritan-micon.blog.so-net.ne.jp/2008-03-23
  • USBCVは走っている間はWindowsのUSBスタックを置き換え、完全にUSBを乗っ取ります。USBマウス、キーボードは通常の使用はできません(テスト対象となってしまう)。ノートPCのキーボード、パッドなどは通常内部でPS/2で接続されているのでOKです。

仕様

  • USB Command Verifier Compliance Test Specification?

EULA

  • USB Command Verifier - 64-bit version
    Version 1.4.15
    Release Notes
    April 2, 2015
    USB Command Verifier
    ·	You must uninstall any previous versions of USB20CV before installing.  The USB20CV installer does not uninstall earlier versions of USB20CV.  You must do it yourself.
    ·	USB 2.0 Command Verifier (USB20CV) is a new tool that replaces the old USBCheck. This tool has been tested on Windows 7, Windows 8 and Windows 8.1 with the latest service packs and updates installed in each case.
    ·	For Windows 7, Windows 8 and Windows 8.1, User Account Control (UAC) must be turned off. After turning off UAC, the system must be rebooted in order for the changes to take effect.
     ·	Windows 7, Windows 8 and Windows 8.1 must be run with Driver Signature Enforcement disabled. 
     ·	For Windows 7:  At system start-up, press F-8 for Advanced Boot Options screen, then select Disable Driver Signature Enforcement.
     ·	For Windows 8 and Windows 8.1:  
      ·	Go to the Settings screen by moving the mouse to the bottom right corner of the screen and then moving it up to select the Settings icon.
      ·	Holding the shift key down, click on the Power icon and select Restart.  In a few seconds, this will take you to the Choose An Option screen.
      ·	Select Troubleshoot
      ·	Select Advanced Options
      ·	Select Startup Settings
      ·	Select Restart.  This will reboot the computer.  When Windows 8 starts up again, you will be taken to a Startup Settings screen.
      ·	Select Disable driver signature enforcement.
    ·	This tool requires that Microsoft XML (MSXML) version 6.0 be installed on your computer.  This is the default version for Windows 7 and Windows 8.  If necessary, it can be downloaded from www.microsoft.com.
    ·	You will need a browser to view the results of the test.
    ·	This version of the tool requires that you have at least one EHCI compliant USB 2.0 host controller card in your system. Further, to test full and low speed hubs/devices a USB2.0 HUB is required.
    ·	A description of the tests that USB20CV performs is provided in the USB Command Verifier Compliance Test Specification.
    ·	This version of the tool supports the use of mouse and keyboard plugged directly into the root ports of the USB 2.0 host controller on your system.
    
    To complete the installation:
    Download the Company list file (USB.if)
    ·	You can get this file at http://www.usb.org/developers/tools.  Follow the instructions to download the company list and save the file under the lib subdirectory where USB20CV was installed. (default path C:\Program Files\USB-IF Test Suite\USBCommandVerifier\lib).
    
    Using USB20CV:
    Usage Models/Restrictions
    ·	This version of the tool requires that you install the eHCI compliance driver for your eHCI-based host controller prior to running USB20CV.
    ·	A device to be tested must be connected to the system, either directly or to a USB 2.0 Hub (in the case of a full/low speed device) in order for the test suite to detect it and perform tests on it.
    ·	Devices connected down stream of a hub under test (only applies to Hub tests) must be capable of remote wakeup. Preferably use mice.
    ·	Upon completion of a test an html report is created in the Reports subdirectory where USB20CV was installed.
    
     
    Testing High Speed Capable Devices
    ·	In order to test high speed mode of high speed capable devices, the device can be connected directly to the root port of the EHCI compliant USB2.0 controller or to an A-receptacle of a USB 2.0 hub.
    ·	In order to test full speed mode of high speed capable devices, the device must be connected below a full speed (USB 1.1) hub. The full speed hub must then be connected to the EHCI based host controller behind another high speed hub.
    
    Testing Full/Low Speed Capable Devices
    ·	Full or Low speed devices must be connected behind a high speed USB 2.0 hub in order to be tested.
    
    USB20CV Warnings
    At the present time, there is no plan to change any warnings to failures.
    
    Uninstalling USB Command Verifier
    ·	Use the Add/Remove Programs control panel applet to remove USB20CV.
    
    Known Issues
    ·     CV crashes intermittently during or after running the Report Descriptor Test in the HID test suite.
    Work-around: There is no reliable work-around at this time.  The following actions have sometimes been effective:
    detaching and reattaching Device Under Test..  
    re-running the tests: if CV crashes after the test completes, there may be output files (either HTML or a BAK) with full test results.
    
    Bug reports
    ·	Send all bug reports to TechAdmin@usb.org <mailto:TechAdmin@usb.org>.
    
    Recent Changes
    Version 1.4.15.0
    Stability fixes for UVC and HID tests.
    Version 1.4.14.0
    Relax requirements for BOS descriptor test: capability type can now be any value.
    Version 1.4.13.0
    At startup, CV now prompts user to choose a host controller, even if there is only one xHCI host controller on the system.
    Version 1.4.12.0
    Added consistency check to MSC test suite: Command Set test now fails if READ CAPACITY(16) values for block size and block count are not consistent with READ CAPACITY(10).
    Version 1.4.11.0
    CV actively determines how many configurations a device supports.  It no longer depends on the value given in the device descriptor.
    Version 1.4.10.2
    CV now saves log files to the user's documents directory.
    UVC tests no longer fail if descriptors contain H.264 simulcast formats.
    Added sensors to HID Usage Tables.
    Version 1.4.10.1
    Compliance test spec for UVC 1.5 added.
    Fixed bug where CV intermittently crashes at test suite start-up.
    Version 1.4.10.0
    Driver updated to be more compatible with Windows 8.
    Version 1.4.9.7
    CV now functions correctly with 800x600 monitors.
    Fixed driver signature for 64-bit drivers.
    Version 1.4.9.6
    UVC - Fixed bug where White Temperature Balance Auto test would time out under certain circumstances.
    Version 1.4.9.5
    UVC - Fixed bug H.264 Commit would commit blank probe/commit structure, no matter what the intended values..
    Version 1.4.9.4
    UVC - Fixed bug in White Balance Temperature Auto Control test.
    Version 1.4.9.3
    UVC - Fixed bug where Frame-based Format Descriptor test and Frame-based Frame.Descriptor test failed if there were multiple frame-based formats in the same interface.
    Version 1.4.9.2
    Enumeration update - fixed a bug that caused devices to receive SetConfiguration(value) more than once.  Device should how receive only 1 SetConfiguration() request unless the software is changing the configuration value.
    UVC - Fixed bug where descriptor tests failed when streaming interface had multiple formats.
    

メモ

  • 起動時に出てくるホストコントローラの選択はデバイスマネージャのデバイスのプロパティの"場所"で確認できる。

関連