This chapter includes:
The following table may help you find information quickly:
|For information about:||See this chapter:|
|The character I/O system||Character I/O Architecture|
|The 8250 serial driver||8250 serial driver|
|Functions and data structures provided by the io-char library||Character I/O Library|
To use this guide, you need to have:
The Character DDK package can be downloaded from Foundry27.
The latest source code can also be downloaded at Foundry27:BSPs and Drivers Source code .
|This part of Foundry27 is now deprecated and is no longer being developed.|
You can compile the DDK from the IDE or 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.
The following example indicates how you create a directory and unzip the archive file:
# cd ~ # mkdir ddk_install_dir # cd ddk_install_dir # unzip /path_to_ddks/ddk-device_type.zip # make
Then you should get binaries and libraries in ddk_install_dir/install .
The top-level directory structure for the DDK looks like this:
|Historically, you had to run:
to set up the environment variable of the installation directory's make. This method is no longer required, as all the directories in /src have been set up to install their binaries and libraries to ddk_install_dir/install.
Additionally, on Windows hosts you'll need to run the Bash shell (bash.exe) before you run the make command.
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 /install 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.
Throughout this manual, we use certain typographical conventions to distinguish technical terms. In general, the conventions we use conform to those found in IEEE POSIX publications. The following table summarizes our conventions:
|Code examples||if( stream == NULL )|
|File and pathnames||/dev/null|
|Keyboard input||something you type|
|Programming data types||unsigned short|
|Programming literals||0xFF, "message string"|
We use an arrow (→) in directions for accessing menu items, like this:
You'll find the Other... menu item under.
We use notes, cautions, and warnings to highlight important messages:
|Notes point out something important or useful.|
|Cautions tell you about commands or procedures that may have unwanted or undesirable side effects.|
|Warnings tell you about commands or procedures that could be dangerous to your files, your hardware, or even yourself.|
In our documentation, we use a forward slash (/) as a delimiter in all pathnames, including those pointing to Windows files.
We also generally follow POSIX/UNIX filesystem conventions.
To obtain technical support for any QNX product, visit the Support area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.
Copyright © 2002–2018, QNX Software Systems Limited, a subsidiary of BlackBerry Limited. All rights reserved.