VIA WCE X86 USB UHCI Driver Installation Guide 8/16/2000 Copyright (C) 2000 VIA Technologies, INC. 1. Release note This package release is version 1.1, which enables the USB UHCI host controller within VIA's south bridge chips for Windows CE. The package operates on any Windows CE X86-based platform using VIA's chipsets, such as VT82C686A, VT82C596B, VT82C586B, and forthcoming south bridge chips with integrated USB controller. The driver works properly with Microsoft Windows CE 2.12 & 3.00, and it should also work for later versions of Windows CE. 2. Revision note Features supported but different from Version 1.0 are described below: (1) Add WinCE 3.00 support to the driver. 3. File descriptions The package contains 7 files as described below: 08/14/00 05:15p 190,031 \DEBUG\VIAUHCI.DLL drv debug version 08/14/00 05:15p 151,366 \DEBUG\VIAUHCI.MAP MAP file 08/14/00 05:15p 446,464 \DEBUG\VIAUHCI.PDB PDB file 08/14/00 04:56p 32,848 \RETAIL\VIAUHCI.DLL drv retail version 08/15/00 06:39p 351 PLATFORM.BIB sample BIB file 08/15/00 06:44p 742 PLATFORM.REG sample REG file ReadMe.txt this readme file 4. The following step-by-step instructions assume your X86-based target platform is VIACEPC with the Windows CE 3.00 MAXALL configuration adopted. Make sure an IRQ is allocated to the integrated USB UHCI controller through proper BIOS settings. A USB peripheral, such as a keyboard (Microsoft's recommended) or a mouse, is required for initial testing. Do not plug any USB device to your target platform at this time. 5. Make a binary image Refer to "VIA WCE X86 Driver Installation Migration Guide for Microsoft Windows CE Platform Builder 3.00" to create platform VIACEPC and a Maxall binary image. Download the image to your target platform and confirm the success of the build. 6. Copy binary to the current release directory under \Wince300 For a retail build, copy the following file: viauhci.dll For a debug build, copy the following three files: viauhci.dll viauhci.pdb viauhci.map 7. Modify bib file in the current release directory under \Wince300 Locate the Platform.bib file and modify the IMGUSB section as follows: IF ODO_NOUSB ! IF IMGUSB IF CEPC_UHCI VIAuhci.dll $(_FLATRELEASEDIR)\VIAuhci.dll NK SH ENDIF IF CEPC_OHCI ohci.dll $(_FLATRELEASEDIR)\ohci.dll NK SH ENDIF usbd.dll $(_FLATRELEASEDIR)\usbd.dll NK SH usbhid.dll $(_FLATRELEASEDIR)\usbhid.dll NK SH ENDIF ENDIF A sample Platform.bib file is included for your reference. 8. Modify reg file in the current release directory under \Wince300 Locate the Platform.reg file, modify the IMGUSB section as follows: IF ODO_NOUSB ! IF IMGUSB IF CEPC_OHCI ; USB - OHCI driver [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\OHCI] "Prefix"="HCD" "Dll"="ohci.dll" "Index"=dword:1 "Order"=dword:1 IF CEPC_USB_USE_EXISTING "UseExistingSettings"=dword:1 ENDIF IF CEPC_USB_USE_EXISTING ! "UseExistingSettings"=dword:0 ENDIF "Irq"=dword:0F "MemBase"=dword:FFBFE000 ENDIF IF CEPC_UHCI ; USB - UHCI driver [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\UHCI] "Prefix"="HCD" "Dll"="VIAUhci.dll" "Index"=dword:1 "Order"=dword:1 IF CEPC_USB_USE_EXISTING "UseExistingSettings"=dword:1 ENDIF IF CEPC_USB_USE_EXISTING ! "UseExistingSettings"=dword:0 ENDIF "Irq"=dword:0A "MemBase"=dword:D801 ENDIF ENDIF ENDIF A sample Platform.reg file is included for your reference. 9. Add the environment variable Choose Settings from the Platform menu. Select the Environment to define three variables and set their values as follows: set IMGUSB=1 set CEPC_UHCI=1 set CEPC_USB_USE_EXISTING=1 10. Choose "Make Image" from the Build menu to make a new OS image to include the UHCI driver. Then download the binary image to your target platform. 11. Basic testing (1) Plug a USB mouse to your target platform. Move the mouse around, to ensure the USB UHCI driver is installed successfully. (2) Plug a USB keyboard to your target platform. Have a few key strokes, to ensure the USB UHCI driver is installed successfully. 12. Trouble shooting (1) If the USB mouse or keyboard does not work, adjust the BIOS settings on your target platform and confirm an IRQ is allocated to the USB controller. Download the binary image to your platform and test it again. (2) A USB keyboard with an extension port for a PS/2 mouse may not work properly and have the following error message: !CHid::HidNewDevice - Error setting up new HID device This is caused by the default USB HID driver, which may result in USB HID device failures. Refer to "VIA WCE X86 USB HID Driver Installation Guide" for using an enhanced HID driver to resolve this problem. (3) In case you encounter any other problem, first connect the debug port in your target Windows CE platform to a serial port in your PC-based NT development platform, e.g. with communication parameters {38400, n, 8, 1}. Make a debug build binary image and download it to your target platform. Dump related debug messages and then contact VIA's representatives for further technical assistance. 13. Quality assurance: The driver has been tested with test programs "usbload" and "usbdrv" shipped along with the DDTK of Windows CE 3.00 & 2.12. It has also been tested with the USB client driver, the HID class driver, and the USBD driver layer to verify that all the entry points required by USB are present and well-exported. This release passed all the tests and worked properly with VIA's existing mass-production south bridges such as VT82C686A, VT82C596B, and VT82C586B, and some forthcoming chips.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.