QNX SDP 8.0.3 Release Notes

QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.3. These release notes describe the key features of this new release and the notable improvements since the previous release, and provide installation instructions.


Date of this edition: August 14, 2025

Target hardware

This product can run on x86_64 hardware platforms and AArch64 platforms that support the ARMv8.0 or v8.2 instruction sets.

Development Host Operating Systems (OSs)

You must install QNX SDP 8.0.3 onto a development host with one of the following 64-bit operating systems:

  • Microsoft Windows 11, or Windows 10
  • Ubuntu Desktop 24.04 LTS, Ubuntu Desktop 22.04 LTS, or Red Hat Enterprise Linux 9
Note:
  • QNX SDP isn't supported on host systems that use ARM processors.
  • QNX SDP isn't supported on macOS anymore.

Contents

What's new in QNX SDP?

Component Feature Details
Kernel AMD virtualization extensions The procnto binary now supports virtualization extensions on AMD processors, which allows future versions of QNX Hypervisor to run on AMD targets. The same procnto binary supports virtualization extensions on other x86 (e.g., Intel) processors and AArch64 processors.
Kernel Offlining and Onlining Scheduling Dynamic Processor State Management:
  • The SchedCtl() commands SCHED_PROCESSOR_ONLINE and SCHED_PROCESSOR_OFFLINE.
  • TimerDelegate() and TimerDelegate_r() functions.
  • The SchedSet() scheduling policy SCHED_OFFLINING (and the PROCMGR_AID_RUNSTATE ability needed to set it)
Networking High-performance networking stack

The new devs-ure.so driver supports RealTek RTL8152/RTL8153/RTL8153B/RTL8156/RTL8156B USB to Ethernet controllers.
Networking High-performance networking stack The io-sock resource manager threads no longer inherit their priority from the client making the request.
Networking High-performance networking stack The following sysctl variables and tunables are new:
  • qnx.dtb_path — for driver development purposes, allows you to configure io-sock to read the DTB (device tree blob) from a specified path instead of the asinfo (Address Space Information) section of the system page.
  • qnx.pool.* variables and tunables — allow you to read and set io-sock resource manager thread pool information.
  • dev.iface_name.iface_no.iflib.rxtx_in_ist — allows you to specify where packet processing for the specified interface is done.
  • qnx.priority — replaces qnx.ist_prio, qnx.taskq_prio, and qnx.timer_prio.
Networking High-performance networking stack

The miibus framework provided with io-sock now supports Clause 45 PHY drivers.
Networking High-performance networking stack

The bind(), connect(), and sendto() functions now support relative paths for UNIX domain sockets.
Networking High-performance networking stack

Paths to UNIX domain sockets must now be in a writable Power-Safe, Linux Ext2, or Flash FileSystem version 3 (FFS3) filesystem.
Networking High-performance networking stack The FreeBSD version that QNX OS networking is based on has been updated from 13.4 to 13.5.
Networking High-performance networking stack The io-sock networking stack now supports the Point-to-Point Protocol, provided via the ppp utility ported from FreeBSD.
Filesystems UDS Support for Unix Domain Sockets (UDSs) has been added for Power-Safe filesystems, meaning socket files can be created.
Filesystems QNX Filesystem for Safety

The new QNX Filesystem for Safety is a read-only, integrity-protected filesystem solution. Currently, it is an experimental feature.

Host Tools mkqnximage

The mkqnximage utility now supports the creation of an image for use on a physical (non-virtual) target (e.g., Raspberry Pi).
Host Tools SVE, SVE2 Support for Scalable Vector Extension (SVE):
  • Allows userspace to use Arm C language extensions (ACLE).​
  • Use of GCC 12 which supports SVE and SVE2.
  • Certification of -march=armv8.2-a+sve GCC option.
Host Tools rust (host) Added support for compiling applications written in the Rust language. The following crates are supported with Rust compiler (1.85):
  • core
  • alloc
  • backtrace
  • std

Installing QNX SDP

To use QNX SDP 8.0.3, you need to have QNX Software Center 2.0.4 or later. For information about installing and opening this other product, refer to the Install and launch the QNX Software Center chapter in the QNX Software Center User's Guide.

To install the QNX SDP 8.0.3 packages as a new baseline product, open the QNX Software Center and click Add Installation on the left to launch the New Installation Wizard. In the first dialog, scroll to QNX Software Development Platform 8.0 and select QNX Software Development Platform 8.0.3. Follow the prompts (e.g., the Next and Install buttons) to perform the installation. Select any of the options from the Update Policy dropdown. For more information, refer to the Install the QNX Software Development Platform chapter in the QNX Software Center User's Guide.

To update your existing QNX SDP 8.0.2 installation to version 8.0.3, use the provided patch set. To install the patch set, open the QNX Software Center, select the installation you want to update in the Active Installation dropdown on the Welcome page and click Install New Packages. The QNX SDP 8.0.3 patch set is found under Available -> QNX Software Development Platform - Minor Release -> Patch Set.

Select the QNX OS 8.0.3 and QNX Tool Suite package and then follow the prompts to perform the installation.
Warning:
When applying the patch set to an existing installation, QNX Software Center displays a set of warnings indicating that several packages have already been installed. This behavior is expected. You can ignore the warnings and click Next to continue with the installation.

Once installed, the patch set is found under Installed -> QNX Software Development Platform -> Software Development Platform.

To access the contents of the package, right-click QNX OS and QNX Tool Suite, choose Properties, then click Package Contents. Some of the packages may contain no files but instead references to contained packages (or subpackages), in which case the contents page will display a note saying so. To access the list of subpackages, right-click the package, choose Properties, then click Package Dependencies. Because the baseline OS product has many inter-package dependencies, sometimes you have to go through multiple levels of subpackages to access the included files.

Note:
For more information related to QNX SDP 8.0.3 updates, refer to the QNX SDP 8.0.3 Product Updates Release Notes prior to installing those updates.
Note:
Some packages in this release include experimental files. The maturity level of individual files is displayed in the Status column in the package contents table. The individual files in a package can have different maturity levels.

You can also obtain the maturity statuses of files by generating a manifest report. For more information, refer to the Manifest Reports & File Lookup chapter of the QNX Software Center User's Guide.

Each package has its maturity level. You can learn this by right-clicking the package, choosing Properties, then clicking General Information. In the Legal and Regulatory Information panel, there's a Status field. For details about the possible values of this field, refer to the Package status section in the Deploy licenses to users topic in the QNX Software Center User's Guide.

Debug information for shipped binaries

The QNX SDP target binaries are generated with debug information (-g), with the debug form of the binary stored in a separate binaryName.sym file. The non-sym form is stripped of the debug and .ident information (use -s works only on files containing the .ident section).

Most target packages include debug information (.sym files). The binaries and their .sym files are linked, so gdb understands where to find the symbol data. There's no need to store .sym files for the binaries on a target.

If the debug symbols are especially large, there might be a separate debug package in the QNX Software Center. To install debug symbols in this case, select your installation from the toolbar, then go to the Advanced tab. Click Edit Installation Properties. In the property dialog that opens, ensure that the Install debug symbols checkbox is checked (this box is checked by default). Click OK.

If you decide to not install the debug information but later want it, you can right-click a package and choose Install debug symbols.

Experimental items

CAUTION:
Experimental software is primarily provided for customers and the community to try out, and to get an idea of what might be coming in the future. For information about the use of experimental software, refer to the Commercial Software License Agreement (CSLA) or Partner Software License Agreement (PSLA) in the Licensing area of our website: https://www.qnx.com/legal/licensing/.

Some experimental items are implemented in the packages of the baseline product. This means these items are installed when you install QNX SDP and, hence, there's nothing else you must do to be able to use them. Other experimental items are contained in their own packages that aren't installed when you install QNX SDP. To locate and install these packages so you can use the items they contain, go to the Available tab in QNX Software Center and search for part or all of the package name. Then, click the package in the search results and then the Install button in the bottom right corner.

The table that follows lists the experimental items by functional area and indicates whether each one is contained in an additional package that must be installed separately.

Functional area Item description Additional package
BSP & Drivers Added Dynamic Interrupt Manager (DIM) None
Networking Texas Instruments Jacinto 7 network drivers (devs-cpsw-j721e.so, devs-cpsw-j784s4.so, devs-cpsw-j721s2.so) None
Networking Texas Instruments Sitara network driver (devs-cpsw-am62x.so) None
Networking Marvell Network PHY driver (devs-marvell_phy.so) None
Networking RT9010 network PHY driver (devs-rt9010phy.so) None
Networking DWC gmac network driver (devs-dwc.so) N/A
Networking RNDIS USB network driver (devs-urndis.so) N/A
Screen Support for the core Wayland communication library and the Weston compositor for Screen QNX SDP 8.0 Wayland/Weston
Screen Tools for using Wayland on Linux 64-bit hosts QNX SDP 8.0 Wayland host tools (Linux 64-bit)
Screen Tools for using Wayland on Windows 64-bit hosts QNX SDP 8.0 Wayland host tools (Windows 64-bit)

Fixed issues

The following issues are fixed in this update. To find a specific issue, search for a reference number on this page or use the search tool:
Description Applicable Architecture(s) Application-Level Impact System-Level Impact Reference Number

A priority inversion issue in the ring buffer which occured when the networking stack is pinned to a single CPU, has been fixed.

 AArch64, x86_64 None Rebuild with updated io-sock. 2967442

An issue that caused a process to need the BLK_ABILITY_MOUNTVFS ability when it attempted to mount any filesystem as non-root while fs-nfs3 was running, even if the mount wasn't for fs-nfs3 (e.g., mounting a secondary IFS), has been fixed.

 AArch64, x86_64 None Rebuild with updated fs-nfs3. 2975496
Enabling ALLMULTI (receive all multicast packets) for the devs-smsc.so driver now correctly configures the MAC filters for ALLMULTI mode. Also, the smsc0 interface now receives packets after setting a new MAC address, as expected. AArch64, x86_64 None Rebuild with updated devs-smsc.so. 2943676
The devs-smsc.so driver now sets the auto-negotiation flag when you set the interface link mode to media 100baseTX mediaopt full-duplex or lower, as expected. AArch64, x86_64 None Rebuild with updated devs-smsc.so. 2950494
An issue with the debugger being unable to backtrace the binaries built with the AARCH64 pointer authorization feature has been fixed. AArch64 None None 2978775

Licensing information

The QNX SDP licensing, packaging, and fulfillment model from the previous release has been carried forward to this release. That is, QNX SDP will be available in the QNX Download Center and QNX Software Center as a new product baseline. Additionally, the license agreements will include a few enhancements for clarifications but otherwise will remain unchanged.

Getting started with the documentation

The QNX SDP 8.0 documentation is found on our public website at https://www.qnx.com/developers/docs/8.0/com.qnx.doc.qnxsdp.nav/topic/bookset.html.

This roadmap page contains links to the various booksets that accompany the QNX OS. For a short tutorial that will help you set up a QNX OS target and run a simple program, refer to the Quickstart Guide. Then you can access the other key documents (QNX OS System Architecture, Programmer's Guide, C Library Reference, and more) to learn about how the QNX OS is designed and how to write programs that run on it.

Technical support

To obtain technical support for any QNX product, visit the Support area on our website: https://blackberry.qnx.com/en/support. You'll find a range of support options.

For product experience and roadmap information, please contact QNX Product Management.

Page updated: