A QNX target image combines the contents of a hardware-specific BSP with the QNX Neutrino RTOS and other components, such as resource managers, services, device drivers, and applications.
When the startup code has completed its tasks, execution transfers to the QNX OS kernel and a process manager (procnto). These components aren't hardware-specific, so they don't need to be included in a BSP. They are simply part of a generic QNX Neutrino installation.
If your system needs persistent storage, you run a driver for each each filesystem you use. QNX supplies several classes of filesystems, including embedded flash filesystems (EFS), embedded transaction filesystems (ETFS), block filesystems, and network filesystems.
If no driver is available for a particular filesystem on your board, you can modify an existing driver. For information about writing device drivers, see Writing a Resource Manager.
The System Launch and Monitor (SLM) service can be used to complete the startup process after the startup code has finished and the OS kernel and procnto are running. If a component isn't required for the initial startup, you can take the component binary out of the IFS and manage its launch with the SLM. This approach allows you both reduce the size of the IFS, and make it easier to modifying your startup sequence.
The SLM service can launch complex applications consisting of many processes that must be started in a specific order. It is controlled by a set of XML configuration files, so you can change the order in which components are started without modifying the startup scripts. For more information, see slm in the Utilities Reference).