This version of this document is no longer maintained. For the latest documentation, see http://www.qnx.com/developers/docs.

About the USB DDK

In this preface, you'll find Building DDKs. This document provides information about changes to installing DDKs.

Our USB API is designed to work with either QNX Neutrino or QNX 4. Exceptions will be noted where appropriate.

This guide is organized into these main parts:

a read-this-first page indicating your system requirements and other vital information you should know before you begin
an overview describing how the OS supports USB
command-line utilities
a set of function pages describing the USB driver interface calls

The USB SDK includes source code for several USB class drivers. Each class driver is contained in its own separate archive. Look under the /ddk_working_dir/usb/src/hardware/devu/class directory on your system.

Assumptions

We assume you're familiar with the Universal Serial Bus (USB) Specification revision 2.0, especially the chapters on:

Architectural Overview
USB Data Flow Model
USB Device Framework
USB Host: Hardware and Software.

You'll need a good understanding of the concepts in those chapters in order to write USB client device drivers.

For up-to-date information on USB developments, visit www.usb.org.

Building DDKs

You can compile the DDK from the IDE or the command line.

To compile the DDK from the IDE:
Please refer to the Managing Source Code chapter, and "QNX Source Package" in the Common Wizards Reference chapter of the IDE User's Guide.

To compile the DDK from the command line:

Please refer to the release notes or the installation notes for information on the location of the DDK archives.

DDKs are simple zipped archives, with no special requirements. You must manually expand their directory structure from the archive. You can install them into whichever directory you choose, assuming you have write permissions for the chosen directory.

Historically, DDKs were placed in /usr/src/ddk_VERSION directory, e.g. /usr/src/ddk-6.2.1. This method is no longer required, as each DDK archive is completely self-contained.

The following example indicates how you create a directory and unzip the archive file:

# cd ~
# mkdir my_DDK
# cd my_DDK
# unzip /path_to_ddks/ddk-device_type.zip

The top-level directory structure for the DDK looks like this:

DDK directories

Directory structure for this DDK.

You must run:

. ./setenv.sh

before running make, or make install.

Additionally, on Windows hosts you'll need to run the Bash shell (bash.exe) before you run the . ./setenv.sh command.

If you fail to run the . ./setenv.sh shell script prior to building the DDK, you can overwrite existing binaries or libs that are installed in $QNX_TARGET.

Each time you start a new shell, run the . ./setenv.sh command. The shell needs to be initialized before you can compile the archive.

The script will be located in the same directory where you unzipped the archive file. It must be run in such a way that it modifies the current shell's environment, not a sub-shell environment.

In ksh and bash shells, All shell scripts are executed in a sub-shell by default. Therefore, it's important that you use the syntax

. <script>

which will prevent a sub-shell from being used.

Each DDK is rooted in whatever directory you copy it to. If you type make within this directory, you'll generate all of the buildable entities within that DDK no matter where you move the directory.

all binaries are placed in a scratch area within the DDK directory that mimics the layout of a target system.

When you build a DDK, everything it needs, aside from standard system headers, is pulled in from within its own directory. Nothing that's built is installed outside of the DDK's directory. The makefiles shipped with the DDKs copy the contents of the prebuilt directory into the install directory. The binaries are built from the source using include files and link libraries in the install directory.