windriver安装

http://www.jungo.com/st/support/documentation/windriver/11.6.0/wdpci_manual.mhtml/wd_install_process.html#wd_install_linux

3.2. WinDriver Installation Process

3.2.1. Windows WinDriver Installation Instructions

	Driver installation on Windows requires administrator privileges.

1. Run the WinDriver installation — WD1160.EXE — and follow the installation instructions.
2. At the end of the installation, you may be prompted to reboot your computer.

The WinDriver installation 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 [4] 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. This variable is also used in the sample Kernel PlugIn projects and makefiles. If the installation fails with an ERROR_FILE_NOT_FOUND error, inspect the Windows registry to see if the RunOnce key exists in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion. This registry key is required by Windows Plug?-?and?-?Play in order to properly install drivers using INF files. If the RunOnce key is missing, create it; then try installing the INF file again.

The following steps are for registered users only:

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

3. Start DriverWizard: Start | Programs | WinDriver | DriverWizard.
4. Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo.
5. Click the Activate License button.
6. To register source code that you developed during the evaluation period, refer to the documentation of WDC_DriverOpen() [B.3.2]. When using the low?-?level WD_xxx API instead of the WDC_xxx API [B.2] (which is used by default), refer to the documentation of WD_License() in the WinDriver PCI Low?-?Level API Reference.

3.2.2. Windows CE WinDriver Installation Instructions

3.2.2.1. Installing WinDriver CE when Building New CE-?Based Platforms

The following instructions apply to platform developers who build Windows CE kernel images using Windows CE Platform Builder or using MS Visual Studio 2005/2008 with the appropriate Windows CE plugin. The instructions use the notation 'Windows CE IDE' to refer to either of these platforms. We recommend that you read Microsoft's documentation and understand the Windows CE and device driver integration procedure before you perform the installation.

1. Modify the project registry file — WinDriver\samples\wince_install\project_wd.reg — to add an entry for your target device.
2. Compile your Windows CE platform (Sysgen stage).
3. Integrate the driver into your platform:
   1. Run the Windows CE IDE and open your platform.
   2. Select Open Release Directory from the Build menu.
   3. Copy the WinDriver CE kernel file — WinDriver\redist\\windrvr6.dll — to the %_FLATRELEASEDIR% subdirectory on the target development platform (should be the current directory in the new command window).
   4. Append the contents of WinDriver\samples\wince_install\project_wd.reg to the %_FLATRELEASEDIR%\project.reg registry file.

   5. Copy the contents of the WinDriver\samples\wince_install\project_wd.bib file to the FILES section of the binary image builder file — %_FLATRELEASEDIR%\project.bib. Then uncomment the line that matches the target platform (see the "TODO" comments in the copied text).

      	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 boot disk. If you prefer to have the file windrvr6.dll loaded on demand via the CESH/PPSH services, you do not need to perform this step until you build a permanent kernel.

4. Select Make Run-Time Image from the Build menu, and name the new image NK.BIN.
5. Download your new kernel to the target platform and initialize it either by selecting Attach Device from the Target menu, or by using a boot disk. For Windows CE 4.x, the menu is called Download/Initialize rather than Attach Device.
6. Restart your target CE platform. The WinDriver CE kernel will automatically load.
7. Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly (see Section 3.4.2, which describes how to check your installation).

3.2.2.2. Installing WinDriver CE when Developing Applications for Windows CE Computers

	Unless otherwise specified, 'Windows CE' references in this section include all supported Windows CE platforms, including Windows Mobile.

The following instructions apply to driver developers who do not build the Windows CE kernel, but only download their drivers, built using MS eMbedded Visual C?+?+ or MS Visual Studio 2005/2008 to a ready-made Windows CE platform.

1. Run the WinDriver installation — WD1160CE.EXE — on your host Windows PC, and complete the installation.
2. Copy WinDriver's kernel module — windrvr6.dll — from the WinDriver?\?redist\WINCE\ directory on the Windows host development PC to the Windows directory on your target Windows CE platform.
3. 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?+?+ or MS Visual Studio 2005/2008. 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 many versions of Windows CE, 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 CE 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 PC.
4. 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).
5. Compile and run the sample programs to make sure that WinDriver CE is loaded and is functioning correctly (see Section 3.4, which describes how to check your installation).

3.2.2.3. Windows CE Installation Note

The WinDriver installation on the host Windows 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 [4] 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 toolkit on the same host PC, the installation will override the value of the WD_BASEDIR variable from the Windows CE installation.

3.2.3. Linux WinDriver Installation Instructions

3.2.3.1. Preparing the System for Installation

In Linux, kernel modules must be compiled with the same header files that the kernel itself was compiled with. Since WinDriver installs kernel modules, it must compile with the header files of the Linux kernel during the installation process.

Therefore, before you install WinDriver for Linux, verify that the Linux source code and the file version.h are installed on your machine:

Install the Linux kernel source code:

• If you have yet to install Linux, install it, including the kernel source code, by following the instructions for your Linux distribution.
• If Linux is already installed on your machine, check whether the Linux source code was installed. You can do this by looking for 'linux' in the /usr/src directory. If the source code is not installed, either install it, or reinstall Linux with the source code, by following the instructions for your Linux distribution.

Install version.h:

• The file version.h is created when you first compile the Linux kernel source code. Some distributions provide a compiled kernel without the file version.h. Look under /usr/src/linux/include/linux to see whether you have this file. If you do not, follow these steps:
  1. Become super user:
     $ su
  2. Change directory to the Linux source directory:
     # cd /usr/src/linux
  3. Type:
     # make xconfig
  4. Save the configuration by choosing Save and Exit.
  5. Type:
     # make dep
  6. Exit super user mode:
     # exit

To run GUI WinDriver applications (e.g., DriverWizard [4]; Debug Monitor [6.2]) you must also have version 5.0 of the libstdc++ library — libstdc++.so.5. If you do not have this file, install it from the relevant RPM in your Linux distribution (e.g., compat-libstdc++).

Before proceeding with the installation, you must also make sure that you have a linux symbolic link. If you do not, create one by typing
/usr/src$ ln -s /linux
For example, for the Linux 2.4 kernel type
/usr/src$ ln -s linux-2.4/ linux

3.2.3.2. Installation

1. On your development Linux machine, change directory to your preferred installation directory, for example to your home directory:
   $ cd ~

   	The path to the installation directory must not contain any spaces.

2. Extract the WinDriver distribution file — WD1160LN.tgz or WD1160LNx86_64.tgz —
   $ tar xvzf /WD1160LN[x86_64].tgz

   For example, to extract WD1160LN.tgz run this command:
   $ tar xvzf ~/WD1160LN.tgz

3. Change directory to your WinDriver redist directory (the tar automatically creates a WinDriver directory):
   $ cd /redist
4. Install WinDriver:
   1. /redist$ ./configure --disable-usb-support

      The configuration script creates a makefile based on the running kernel. You may select to use another installed kernel source, by executing the script with the --with-kernel-source= option, where is the full path to the kernel source directory — e.g., /usr/src/linux. If the Linux kernel version is 2.6.26 or higher, the configuration script generates makefiles that use kbuild to compile the kernel modules. You can force the use of kbuild on earlier versions of Linux, by executing the configuration script with the --enable-kbuild flag.

      	For a full list of the configuration script options, use the --help option: ./configure --help

   2. /redist$ make
   3. Become super user:
      /redist$ su
   4. Install the driver:
      /redist# make install
5. Create a symbolic link so that you can easily launch the DriverWizard GUI:
   $ ln -s /wizard/wdwizard /usr/bin/wdwizard
6. Change the read and execute permissions on the file wdwizard so that ordinary users can access this program.
7. 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. Due to security reasons, by default the device file is created with permissions only for the root user. 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
   
8. 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 [4] code, and is also used to determine the default directory for saving your generated DriverWizard projects. 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.
9. Exit super user mode:
   # exit
10. You can now start using WinDriver to access your hardware and generate your driver code!

	Use the WinDriver/util/wdreg script to load the WinDriver kernel module [13.3].

The following steps are for registered users only:

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

12. Start DriverWizard:
    $ /wizard/wdwizard
13. Select the Register WinDriver option from the File menu, and insert the license string you received from Jungo.
14. Click the Activate License button.
15. To register source code that you developed during the evaluation period, refer to the documentation of WDC_DriverOpen() [B.3.2]. When using the low?-?level WD_xxx API instead of the WDC_xxx API [B.2] (which is used by default), refer to the documentation of WD_License() in the WinDriver PCI Low?-?Level API Reference.

3.2.3.3. Restricting Hardware Access on Linux

Since /dev/windrvr6 gives direct hardware access to user programs, it may compromise kernel stability on multi-user Linux systems. Please restrict access to 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 application (wdwizard).

© Jungo Connectivity Ltd.

CONFIDENTIAL