5.2 Writing the Device Driver Without DriverWizard

5.2 Writing the Device Driver Without DriverWizard
	Chapter 5. Developing a Driver

There may be times when you choose to write your driver directly, without using DriverWizard. In such cases, either follow the steps outlined in this section to create a new driver project, or use one of the WinDriver samples, which most closely resembles your target driver, and modify the sample to suit your specific requirements.

5.2.1 Include the Required WinDriver Files

Include the relevant WinDriver header files in your driver project.
All header files are found under the WinDriver/include directory.
On Mac OS X, when using the WDAPI framework, the header files include path is
/Library/Frameworks/WDAPI.framework/Headers.
All WinDriver projects require the windrvr.h header file.
When using the WDC_xxx API [B.2], include the wdc_lib.h and wdc_defs. header files (these files already include windrvr.h).

Include any other header file that provides APIs that you wish to use from your code (e.g., files from the WinDriver/samples/shared directory, which provide convenient diagnostics functions.)
Include the relevant header files from your source code:
For example, to use API from the windrvr.h header file, add the following line to the code:
```
#include "windrvr.h"
```

Link your code with the WDAPI library (Windows) / framework (Mac OS X) / shared object (Linux):

For Windows 7/Vista/Server 2008/Server 2003/XP/2000: WinDriver\lib\<CPU>\wdapi1020.lib or wdapi1020_borland.lib (for Borland C++ Builder), where the <CPU> directory is either x86 (32-bit binaries for x86 platforms), amd64 (64-bit binaries for x64 platforms) or amd64\x86 (32-bit binaries for x64 platforms [A.2]
For Windows CE: WinDriver\lib\WINCE\<CPU>\wdapi1020.lib
For Mac OS X: /Library/Frameworks/WDAPI.framework
For Linux: From the WinDriver/lib directory – libwdapi1020.so or libwdapi1020_32.so (for 32-bit applications targeted at 64-bit platforms)
Note: When using libwdapi1020_32.so, first create a copy of this file in a different directory and rename it to libwdapi1020.so, then link your code with the renamed file [A.2].

You can also include the library's source files in your project instead of linking the project with the library. The C source files are located under the WinDriver/src/wdapi directory.


When linking your project with the WDAPI library/framework/shared object, you will need to distribute this binary with your driver. For Windows, get wdapi1020.dll / wdapi1020_32.dll (for 32-bit applications targeted at 64-bit platforms) from the WinDriver\redist directory. For Mac OS X, get WDAPI.framework from the OS /Library/Frameworks directory. For Linux, get libwdapi1020.so / libwdapi1020_32.so (for 32-bit applications targeted at 64-bit platforms) from the WinDriver/lib directory.

When linking your project with the WDAPI library/framework/shared object, you will need to distribute this binary with your driver.
For Windows, get wdapi1020.dll / wdapi1020_32.dll (for 32-bit applications targeted at 64-bit platforms) from the WinDriver\redist directory.
For Mac OS X, get WDAPI.framework from the OS /Library/Frameworks directory.
For Linux, get libwdapi1020.so / libwdapi1020_32.so (for 32-bit applications targeted at 64-bit platforms) from the WinDriver/lib directory.

Note: On Windows and Linux, when using the DLL/shared object file for 32-bit applications on 64-bit platforms (wdapi1020_32.dll / libwdapi1020_32.so), rename the copy of the file in the distribution package, by removing the _32 portion [A.2].
For detailed distribution instructions, refer to Chapter 14.

Add any other WinDriver source files that implement API that you which to use in your code (e.g., files from the WinDriver/samples/shared directory.)

5.2.2 Write Your Code

This section outlines the calling sequence when using the WDC_xxx API [B.2].

Call WDC_DriverOpen() [B.3.2] to open a handle to WinDriver and the WDC library, compare the version of the loaded driver with that of your driver source files, and register your WinDriver license (for registered users).
For PCI/CardBus/PCMCIA devices, call WDC_PciScanDevices() [B.3.4] WDC_PcmciaScanDevices() [B.3.7] to scan the PCI/PCMCIA bus and locate your device.
For PCI/CardBus/PCMCIA devices, call WDC_PciGetDeviceInfo() [B.3.8] WDC_PcmciaGetDeviceInfo() [B.3.9] to retrieve the resources information for your selected device.
For ISA devices, define the resources yourself within a WD_CARD structure.
Call WDC_PciDeviceOpen() [B.3.10] WDC_PcmciaDeviceOpen() [B.3.11] WDC_IsaDeviceOpen() [B.3.12] (depending on your device) and pass to the function the device's resources information. These functions return a handle to the device, which you can later use to communicate with the device using the WDC_xxx API.
Communicate with the device using the WDC_xxx API (see description in Appendix B).
To enable interrupts, call WDC_IntEnable() [B.3.46].
To register to receive notifications for Plug-and-Play and power management events, call WDC_EventRegister() [B.3.49].
When you are done, call WDC_IntDisable() [B.3.47] to disable interrupt handling (if previously enabled), call WDC_EventRegister() [B.3.49] to unregister Plug-and-Play and power management event handling (if previously registered), and then call WDC_PciDeviceClose() [B.3.13] WDC_PcmciaDeviceClose() [B.3.14] WDC_IsaDeviceClose() [B.3.15] (depending on your device) in order to close the handle to the device.
Call WDC_DriverClose() [B.3.3] to close the handles to WinDriver and the WDC library.

5.2.3 Configure and Build Your Code

After including the required files and writing your code, make sure that the required build flags and environment variables are set, then build your code.


Before building your code, verify that the `WD_BASEDIR` environment variable is set to the location of the of the WinDriver installation directory. On Windows, Windows CE, and Linux you can define the `WD_BASEDIR` environment variable globally – as explained in Chapter 3: For Windows – refer to the Windows WD_BASEDIR note in section 3.2.1; for Windows CE – refer to section 3.2.2.3; for Linux: refer to section 3.2.4.2, step 9. On Mac OS X, you need to add a `WD_BASEDIR` definition to each driver project. When generating code with DriverWizard [4], this is done automatically. To add this definition manually – open your project with Xcode, select Project Info –> Build tab –> User Defines, and add a `WD_BASEDIR` definition that points to your WinDriver installation directory.

Before building your code, verify that the WD_BASEDIR environment variable is set to the location of the of the WinDriver installation directory.
On Windows, Windows CE, and Linux you can define the WD_BASEDIR environment variable globally – as explained in Chapter 3: For Windows – refer to the Windows WD_BASEDIR note in section 3.2.1; for Windows CE – refer to section 3.2.2.3; for Linux: refer to section 3.2.4.2, step 9.
On Mac OS X, you need to add a WD_BASEDIR definition to each driver project. When generating code with DriverWizard [4], this is done automatically. To add this definition manually – open your project with Xcode, select Project Info –> Build tab –> User Defines, and add a WD_BASEDIR definition that points to your WinDriver installation directory.


Chapter 5. Developing a Driver		5.3 Developing Your Driver on Windows CE Platforms