QP/C  7.1.3
Real-Time Embedded Framework
Loading...
Searching...
No Matches
Ports

General Comments

The QP/C framework can be easily adapted to various operating systems, processor architectures, and compilers. Adapting the QP/C software is called porting and the QP/C framework has been designed from the ground up to make porting easy.

The QP/C distribution contains many QP/C ports, which are organized into the three categories:

  • PC-Lint-Plus (generic C compiler) QP/C "port" to the PC-Lint Plus static analysis tool (a "compiler")
  • Native Ports adapt QP/C to run on bare-metal processors "natively", using one of the built-in kernels (QV, QK, or QXK)
  • 3rd-Party RTOS Ports adapt QP/C to run on top of a 3rd-Party Real-Time Operating System (RTOS)
  • 3rd-Party OS Ports adapt QP/C to run on top of a 3rd-Party Operating System (OS), such as Windows or Linux.

Port Code Structure

Starting with QP/C release 5.4.0, all available ports are bundled into the QP/C download, as opposed to being distributed as separate QP Development Kits (QDKs). The main benefit is of this approach is that it greatly reduces chances of mistakes in combining the mainline QP/C code with various QDKs. The downside is that the QP/C distribution becomes quite large and that ports cannot be added or updated independently from the QP/C baseline code.

All ports are located in sub-directories of the ports top-level folder, with the hierarchical organization outlined below:


qpc/ // QP/C installation directory
+---ports/ // ports directory
| |
| [1]--arm-cm/ // ports for ARM Cortex-M
| | +---qk/ // ports for preemptive QK kernel
| | | +---armclang/ // port with ARM-Clang (Compiler Version 6) toolchain
| | | +---gnu/ // port with GNU-ARM toolchain
| | | +---iar/ // port with IAR toolchain
| | +---qv/ // ports for cooperative QV kernel
| | \---qxk/ // ports for dual-mode QXK kernel
| |
| [2]--freertos/ // ports for FreeRTOS (3rd-party RTOS)
| |
| [3]--win32/ // port to Win32 (multithreaded)
| | +---Debug/ // Debug build configuration for VC++ toolset
| | +---Release/ // Release build configuration for VC++ toolset
| | +---QSpy/ // Spy build configuration for VC++ toolset
| | +---dbg/ // Debug build configuration for GNU toolset
| | +---rel/ // Release build configuration for GNU toolset
| | \---spy/ // Spy build configuration for GNU toolset
| |
| [4]--win32-qv/ // port to Win32 (single-threaded)
| |
| [5]--posix/ // port to POSIX (multithreaded)
| |
| [6]--posix-qv/ // port to POSIX (single-threaded)

[1] Native Ports are located in sub-directories named after the CPU architecture, such as arm-cm for ARM Cortex-M. Under that directory, the sub-directories qk and qv contain ports for the QK and QV kernels, respectively.

[2] Ports for 3rd-party RTOS are located in sub-directories named after the RTOS, such as uc-os2 for uc-os2 RTOS. Under that directory, the sub-directories, such as arm-cm, contain examples for the specified CPU architecture, such as ARM Cortex-M here.

[3] Ports for 3rd-party OS are located in sub-directories named after the OS, such as win32 for the Win32 API (Windows OS). (NOTE: The builds for desktop operating systems, such as Windows or Linux contain the pre-build QP libraries for the Debug, Release, and Spy build configurations).

Note
Because the QP distribution contains all ports, the number of sub-directories and files in the ports folder may seem daunting. However, knowing the structure of the ports folder, you can simply delete the sub-directories that are not interesting to you.