Board Support Packages (BSPs)

If you are rebuilding a QNX Apps and Media target image, you will need to download and build the QNX BSP for your target platform.

A BSP typically includes an Initial Program Loader (IPL), a startup program, a default buildfile, networking support, board-specific device drivers, system managers, utilities, and so on. To learn more about BSPs, see "Working with a BSP" in the Building Embedded Systems guide.

Note: If you haven't modified the BSP, you can use the prebuilt binaries provided by QNX.

Building a BSP (command line)

After you have installed QNX SDP on your host system, you can download platform-specific BSPs from the QNX website. You can then either unzip the archive and build it on the command line, or import it into the IDE and unzip and build it there.

These instructions are for building a BSP from the command line on either a Linux or Windows host system. You may also want to refer to the BSP User Guide for the BSP for your target platform. These guides provide details about switch settings, drivers commands, and so on.

Note: Unless otherwise specified, these instructions assume a Linux host. If you are working on Windows host run the commands in the bash shell.

To build a BSP for QNX SDP 6.6:

  1. Set your environment variables, as instructed in "Set environment variables for image creation".
  2. Download a QNX SDP 6.6 BSP from the QNX website at and save it to a new directory in the SDP host environment (the archive unzips to the current directory).

    For example, you can use the following directory structure:


    The BSP file will be named like this:

    where board_name is the name of the board, xxxxxx is the SVN ID for the BSP, and yy is a unique ID for the BSP.

  3. Navigate to the directory where you saved the BSP and extract the BSP archive file:

    unzip bsp_filename
  4. Change to the root directory of the unzipped BSP, then make and install the BSP:

    make install
  5. To use the newly generated BSP binaries, copy bsp_base_dir/install to $QNX_DEPLOYMENT_WORKSPACE/target/boards/board_name.

For information about the BSP directory structure and where to find key files, see "BSP directory structure".

Permissions on a Windows host

When running on a Windows host, mkifs can't get the execute(x), setuid (set user ID), or setgid (set group ID) permissions from the file, when modifying .build files. Use the perms attribute to specify these permissions explicitly. You might also have to use the uid and gid attributes to set the ownership correctly. To determine whether a utility needs to have the setuid or setgid permission set, see the utility's entry in the QNX SDP Utilities Reference.