Home
QNX Software Development Platform
OS Components
Building Embedded Systems
The Building Embedded Systems guide is intended for developers who are developing or building BSPs for QNX OS embedded systems.
Kernel Callouts
Kernel callouts are standalone pieces of code (or code fragments) that the kernel uses to perform hardware-specific functions. These callouts don't need to be statically linked to the kernel.
Kernel callout categories
The startup library provides kernel callouts that look after different categories of tasks. You can use these callouts as models when you write your own.
Interrupt controller
The interrupt controller interface includes kernel callouts and stubs.

QNX Momentics IDE User's Guide
QNX Software Development Platform
- Quickstart Guide
- System Architecture
  The System Architecture guide accompanies the QNX OS and is intended for both application developers and end-users.
- OS Components
  - Boot Optimization Guide
    The Boot Optimization Guide describes techniques you can use to reduce the time from your board's initial power on until you have a fully functional QNX system running on the board.
  - Building Embedded Systems
    The Building Embedded Systems guide is intended for developers who are developing or building BSPs for QNX OS embedded systems.
    - Overview
      QNX systems are built from the QNX OS standard release components, the architecture- and board-specific files provided in QNX BSPs, and customer and third-party components.
    - Working with QNX BSPs
      Before you attempt to write a new BSP or modify an existing one, it is helpful to know how to use a BSP.
    - Initial Program Loaders (IPLs)
      IPLs first set up the minimum environment needed to execute their compiled C code, then find the OS image and load it into memory, and then jump to the QNX startup code.
    - Startup Programs
      The first program to run in a bootable OS image is the startup program; it completes the system configuration, then launches the OS kernel.
    - Kernel Callouts
      Kernel callouts are standalone pieces of code (or code fragments) that the kernel uses to perform hardware-specific functions. These callouts don't need to be statically linked to the kernel.
      - Kernel callout categories
        The startup library provides kernel callouts that look after different categories of tasks. You can use these callouts as models when you write your own.
        Kernel debug
        The kernel uses the debug callouts when it needs to print out some internal debugging information or encounters a fault.
        Interrupt controller
        The interrupt controller interface includes kernel callouts and stubs.
        Timer and clock
        The kernel uses the timer callouts to work with the hardware timer (i.e., the timer/counter chip).
        System reboot
        The kernel invokes the reboot() callout to reboot the system.
        Cache control
        The cache controller circuitry in your system determines whether you need to provide a callout for the kernel to interface to the cache controller.
        Custom
        You can use the custom() callout to define a function to be invoked synchronously when a kernel call with the value __KER_SYS_CUSTOM (defined in <sys/kercalls.h>) is invoked by a process.
      - Writing a kernel callout
        If your hardware platform isn't supported by the kernel callouts in the startup library, or by any of the available board-specific kernel callouts, you will need to write your own callout.
    - System Page
      The system page contains essential information about the system, including the system page's size, information about the hardware platform (including IRQs and the CPU), the cache size, and the location of kernel callouts in memory.
    - OS Images
      OS images are files that contains the OS, your executables, and any data files that might be related to your programs.
    - OS Image Buildfiles
      You can edit OS image buildfiles to configure OS images.
    - IPL Library
      The IPL library contains a set of routines for building a custom IPL.
    - Startup Library
      The startup library contains a rich set of routines ranging from high-level functions called by main() to utility functions for performing specific startup tasks.
    - Debugging QNX Embedded Systems
      The microkernel architecture of QNX OS means that debugging QNX embedded systems can be different from debugging other embedded systems.
    - Sample Buildfiles
      This appendix contains sample buildfiles that you can modify to support your hardware platform and your implementation requirements.
    - Glossary
  - Customizing a BSP
    While QNX provides Board Support Packages (BSPs) for many common platforms and their individual variants, in some cases, you need a BSP for a board that QNX does not provide. If this is the case, you can modify a QNX BSP or develop your own.
  - High Availability Framework Developer's Guide
  - High-Performance Networking Stack (io-sock) User's Guide
    This guide contains instructions for implementing and using the QNX OS High-Performance Networking Stack and its manager, io-sock.
  - PCI Server User's Guide
  - QNX Helpers Developer's Guide
    These libraries provide QNX helpers, including helpers that assist with logging, string conversion, and number and type sizes.
  - SMMUMAN User's Guide
  - SPI Framework Technote
  - System Analysis Toolkit (SAT) User's Guide
  - Technotes
  - User's Guide
    The QNX OS User's Guide is intended for all users of a QNX OS system, from system administrators to end users.
- Graphics
- Programming
- System Security Guide
  The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX OS system and developers who want to create a QNX OS resource manager free from vulnerabilities.
- Utilities & Libraries
- Migrating to QNX OS 8.0
QNX Software in the Cloud
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX OS applications and systems.
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation and explains how to obtain technical support.

Interrupt controller

QNX SDP8.0Building Embedded SystemsConfigurationDeveloper

The interrupt controller interface includes kernel callouts and stubs.

Note: For information about interrupt sensitivity (level- and edge-), see Hardware initialization in the Startup Programs chapter.

Kernel callouts

mask(): Mask a specific interrupt vector.
unmask(): Unmask a specific interrupt vector.
config(): Discover the configuration of a specified interrupt level.

For more details about these kernel callouts, refer to the intrinfo structure in the System Page chapter.

CAUTION: Your interrupt controller initialization code should set the interrupt triggering. QNX OS uses only level-sensitivity for interrupts (see Hardware initialization in the Startup Programs chapter).

Stubs

Two code stubs are provided: id and eoi. For more information about these stubs, see interrupt_id_*() and interrupt_eoi_*() in this chapter.

For more information about interrupts, see the Interrupts chapter in Getting Started with the QNX OS, and the Handling Hardware Interrupts chapter in the Programmer's Guide.

Page updated: May 17, 2024