Board-specific information
QNX SDP8.0Building Embedded SystemsConfigurationDeveloper
When you modify an existing buildfile to support a new target board, you must update the board-specific information.
Most of the processor- and platform-specific code for
QNX OS systems is in the kernel and startup program,
so only minimal changes are needed to adapt a buildfile written for one board to
work with another board. For your new target board, you need to specify its:
- processor
- startup program
- serial device
Specifying the processor
The buildfile's virtual attribute specifies the processor, the
bootstrap loader, whether the image is compressed, and the operating system
(see
Buildfile syntaxin this chapter). To specify a different processor, simply update this attribute's value. For example, for an ARM little-endian, version 8 CPU, you could change the attribute to:
[virtual=aarch64le,elf]
Specifying the startup program
QNX BSPs include a startup program for the board for which the BSP has been written.
If you are using a board for which no QNX BSP currently exists, you can start with a
BSP for a similar board and modify the startup program (as well as other BSP
components, as needed). Be sure to include the correct startup program name in your
buildfile. For example:
[virtual=aarch64le,elf] .boot = {
startup-honeycomb_lx2 -W
PATH=/proc/boot:/sbin:/bin:/usr/bin:/usr/sbin:/usr/libexec
LD_LIBRARY_PATH=/proc/boot:/lib:/usr/lib:/lib/dll:/lib/dll/pci
procnto-smp-instr -v
}
For more details, see the chapter Startup Programs,
and startup-* options
in the QNX OS Utilities Reference.
Specifying the serial device
If there is a QNX BSP for your board, then the BSP probably includes most (if not all) drivers you will need. If you don't have a QNX BSP for your board, you may need to modify existing QNX drivers so they will work with your board. For more information, see the devc-* entries in the QNX OS Utilities Reference.
Page updated: