WinDriver Installation Instructions

Installing WinDriver CE when Building New CE-based Platforms:

1. Modify the project registry file to add an entry for your target device:
   • If you select to use the WinDriver component (see step 2), modify WinDriver\samples\wince_install\<TARGET_CPU>\WinDriver.reg
     (e.g., WinDriver\samples\wince_install\ARMV4I\WinDriver.reg).
   • Otherwise, modify WinDriver\samples\wince_install\project_wd.reg.
2. You can simplify the driver integration into your Windows CE platform by following the procedure described in this step before the Sysgen platform compilation stage.
   NOTE
   
   

   • The procedure described in this step is relevant only for developers who use Windows CE 4.x-5.x with Platform Builder. Developers who use Windows CE 6.x with MSDEV 2005 should skip to the next step [3].
   • This procedure provides a convenience method for integrating WinDriver into your Windows CE platform. If you select not to use this method, you will need to perform the manual integration steps described in step 4 below after the Sysgen stage.
   • The procedure described in this step also adds the WinDriver kernel module (windrvr6.dll) to your OS image. This is a necessary step if you want the WinDriver CE kernel file (windrvr6.dll) to be a permanent part of the Windows CE image (NK.BIN), which is the case if you select to transfer the file to your target platform using a floppy disk. However, if you prefer to have the file windrvr6.dll loaded on demand via the CESH/PPSH services, you need to perform the manual integration method described in step 4 instead of performing the procedure described in the present step.
   1. Run Microsoft Platform Builder and open your platform.
   2. From the File menu select Manage Catalog Items.... and then click the Import... button and select the WinDriver.cec file from the relevant WinDriver\samples\wince_install\<TARGET_CPU>\ directory (e.g., WinDriver\samples\wince_install\ARMV4I\).
      This will add a WinDriver component to the Platform Builder Catalog.
   3. In the Catalog view, right-click the mouse on the WinDriver Component node in the Third Party tree and select Add to OS design.
3. Compile your Windows CE platform (Sysgen stage).
4. If you have chosen not to perform the procedure described in step 2 above, perform the following steps after the Sysgen stage in order to manually integrate the driver into your platform.
   NOTE
   If you followed the procedure described in step 2, skip this step and go directly to step 5.
   1. Run Microsoft Platform Builder and open your platform.
   2. Select Open Build Release Directory from the Build menu.
   3. Copy the WinDriver CE kernel file — WinDriver\redist\<TARGET_CPU>\windrvr6.dll — to the %_FLATRELEASEDIR% sub-directory on the target development platform (should be the current directory in the new command window).
   4. Append the contents of the project_wd.reg file in the WinDriver\samples\wince_install\ directory to the project.reg file in the %_FLATRELEASEDIR% sub-directory.
   5. Append the contents of the project_wd.bib file in the WinDriver\samples\wince_install\ directory to the project.bib file in the %_FLATRELEASEDIR% sub-directory.

      This step is only necessary if you want the WinDriver CE kernel file (windrvr6.dll) to be a permanent part of the Windows CE image (NK.BIN), which is the case if you select to transfer the file to your target platform using a floppy disk. If you prefer to have the file windrvr6.dll loaded on demand via the CESH/PPSH services, you do not need to carry out this step until you build a permanent kernel.

5. Select Make Image from the Build menu and name the new image NK.BIN.
6. Download your new kernel to the target platform and initialize it either by selecting Download/Initialize from the Target menu or by using a floppy disk.
7. Restart your target CE platform. The WinDriver CE kernel will automatically load.
8. Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly (see the WinDriver User's Manual for an explanation on how to check your installation).

Installing WinDriver CE when Developing Applications for CE Computers:

The following instructions apply to driver developers who do not build the Windows CE kernel, but only download their drivers, built using Microsoft eMbedded Visual C++ (Windows CE 4.x — 5.x) or MSDEV .NET 2005 (Windows Mobile or Windows CE 6.x) to a ready-made Windows CE platform:

1. Insert the WinDriver CD into your Windows host CD drive.

2. Exit the automatic installation.

3. Copy WinDriver's kernel module — windrvr6.dll — from the WinDriver\redist\WINCE\<TARGET_CPU>\ directory on the Windows host development PC to the Windows\ directory on your target Windows CE platform.

4. Add WinDriver to the list of device drivers Windows CE loads on boot:
   • Modify the registry according to the entries documented in the file WinDriver\samples\wince_install\project_wd.reg. This can be done using the Windows CE Pocket Registry Editor on the hand-held CE computer or by using the Remote CE Registry Editor Tool supplied with MS eMbedded Visual C++ (Windows CE 4.x — 5.x) / MSDEV .NET 2005 (Windows Mobile or Windows CE 6.x). Note that in order to use the Remote CE Registry Editor tool you will need to have Windows CE Services installed on your Windows host platform.
   • On Windows Mobile the operating system's security scheme prevents the loading of unsigned drivers at boot time, therefore the WinDriver kernel module has to be reloaded after boot. To load WinDriver on the target Windows Mobile platform every time the OS is started, copy the WinDriver\redist\Windows_Mobile_5_ARMV4I\wdreg.exe utility to the Windows\StartUp\ directory on the target.

5. Restart your target CE computer. The WinDriver CE kernel will automatically load. You will have to do a warm reset rather than just suspend/resume (use the reset or power button on your target CE computer).
6. Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly (see the WinDriver User's Manual for an explanation on how to check your installation).

Windows CE Installation Note:

The WinDriver installation on the host Windows 7/Vista/Server 2003/XP/2000 PC defines a WD_BASEDIR environment variable, which is set to point to the location of your WinDriver directory, as selected during the installation. This variable is used during the DriverWizard code generation — it determines the default directory for saving your generated code and is used in the include paths of the generated project/make files.

Note that if you install the WinDriver Windows 7/Vista/Server 2003/XP/2000 toolkit on the same host PC, the installation will override the value of the WD_BASEDIR variable from the Windows CE installation.

1. Insert the WinDriver CD into the CD drive on your Mac OS X development machine, or copy the downloaded installation package to your preferred location.
2. Double-click the installation package — WD<version>MAC.pkg. (for example, WD10.2.0MAC.pkg) — and follow the installation instructions.

The following steps are for registered users only:

To register your copy of WinDriver with the license you received from Jungo, follow these steps:

1. Start DriverWizard, either by double-clicking /Applications/wdwizard.app, or by running the following command from a command-line prompt:
   $ /Applications/wdwizard.app/Contents/MacOSX/wdwizard
2. Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo.
3. Click the Activate License button.
4. To register source code you developed during the evaluation period, refer to the documentation of WDC_DriverOpen() in the WinDriver User's Manual. When using the low-level WD_xxx API instead of the WDC_xxx API (which is used by default), refer to the documentation of WD_License() in the WinDriver Low-Level API Reference.

1. Insert the WinDriver CD into your Linux machine's CD drive or copy the downloaded file to your preferred directory.
2. Change directory to your preferred installation directory, for example to your home directory:
   $ cd ~
3. Extract the WinDriver distribution file — WD<version>LN.tgz (for example, WD10.2.0LN.tgz):
   $ tar xvzf /<file location>/WD<version>LN.tgz

   For example:

   • From a CD:
     $ tar xvzf /mnt/cdrom/LINUX/WD<version>LN.tgz
     
   • From a downloaded file:
     $ tar xvzf /home/username/WD<version>LN.tgz
4. Change directory to your WinDriver redist/ directory (the tar automatically creates a WinDriver/ directory):
   $ cd <WinDriver directory path>/redist/
5. Install WinDriver:
   1. <WinDriver directory>/redist$./configure
      
      NOTE
      

      The configure script creates a makefile based on your specific running kernel. You may run the configure script based on another kernel source you have installed, by adding the flag --with-kernel-source=<path> to the configure script. The <path> is the full path to the kernel source directory, e.g., /usr/src/linux.
      

      If the Linux kernel is version 2.6.26 or higher, configure generates makefiles that use kbuild to compile the kernel modules. You can force the use of kbuild on earlier versions of Linux, by passing the --enable-kbuild flag to configure.

   
   
   2. <WinDriver directory>/redist$ make
   
   
   3. Become super user:
      <WinDriver directory>/redist$ su
   
   
   4. Install the driver:
      <WinDriver directory>/redist# make install
6. Create a symbolic link so that you can easily launch the DriverWizard GUI:
   $ ln -s <full path to WinDriver>/wizard/wdwizard/
     usr/bin/wdwizard
7. Change the read and execute permissions on the file wdwizard so that ordinary users can access this program.
8. Change the user and group IDs and give read/write permissions to the device file /dev/windrvr6 depending on how you wish to allow users to access hardware through the device.
   
   If you are using a Linux 2.6.x kernel that has the udev file system, change the permissions by modifying your
   /etc/udev/permissions.d/50-udev.permissions file. For example, add the following line to provide read and write permissions:
   windrvr6:root:root:0666
   
   Otherwise, use the chmod command, for example:
   chmod 666 /dev/windrvr6
9. Define a new WD_BASEDIR environment variable and set it to point to the location of your WinDriver directory, as selected during the installation. This variable is used in the make and source files of the WinDriver samples and generated DriverWizard code, and is also used to determine the default directory for saving your generated DriverWizard project. If you do not define this variable you will be instructed to do so when attempting to build the sample/generated code using the WinDriver makefiles.
   
10. You can now start using WinDriver to access your hardware and generate your driver code!

TIP!
Use the WinDriver/util/wdreg script to load the WinDriver kernel module.
To automatically load WinDriver on each boot, add the following to the target Linux boot file (/etc/rc.d/rc.local):
    <path to wdreg>/wdreg windrvr6

The following steps are for registered users only:

To register your copy of WinDriver with the license you received from Jungo, follow these steps:

1. Start DriverWizard:
   <path to WinDriver>/wizard/wdwizard
2. Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo.
3. Click the Activate License button.
4. To register source code you developed during the evaluation period:
   • For USB: Refer to the documentation of WDU_Init() in the WinDriver User's Manual.
   • For PCI: Refer to the documentation of WDC_DriverOpen() in the WinDriver User's Manual.
     
     When using the low-level WD_xxx API instead of the WDC_xxx API (which is used by default), refer to the documentation of WD_License() in the WinDriver Low-Level API Reference.

Restricting Hardware Access on Linux

CAUTION:
Since /dev/windrvr6 gives direct hardware access to user programs, it may compromise kernel stability on multi-user Linux systems. Please restrict access to the DriverWizard and the device file /dev/windrvr6 to trusted users.

For security reasons the WinDriver installation script does not automatically perform the steps of changing the permissions on /dev/windrvr6 and the DriverWizard executable (wdwizard).