QNX Technical Articles

Date of this edition: July 13, 2023

Target OS: This update is compatible with targets that are running on QNX^® Neutrino^® that's based on QNX Software Development Platform 7.1.

Host OS: To install this update, you must have installed the QNX Software Development Platform 7.1 on one of the following development hosts based on x86-64 processors:

• Microsoft Windows 10 Pro 64-bit, or Windows 8.1 Pro 64-bit
• macOS version 10.14, or 10.15
• Linux Red Hat Enterprise Linux 7 64-bit, or Ubuntu Desktop 18.04 LTS 64-bit or Ubuntu Desktop 20.04 LTS 64-bit, on x86_64 processors (QNX SDP isn't supported on Linux on ARM processors)

Contents

• What's in this update?
• Installing this update
• Using this update with existing BSPs
• New features
• Fixed issues
• Technical support

Throughout this document, you may see reference numbers associated with particular issues, changes, etc. When corresponding with our Technical Support staff about a given issue, please quote the relevant reference number. You might also find the reference numbers useful for tracking issues as they become fixed.

---

This experimental software cannot be deployed in any production system. When the PCIv3 server achieves stable status, all packages will be updated and only then can the software be used in a production system.

---

What's in this update?

This update includes the following packages found under Updates -> QNX Software Development Platform or Available -> QNX Software Development Platform:

---

You can get all the PCI subsystem packages listed in the table below by installing just the QNX SDP 7.1 Connectivity - PCI Core Group package, com.qnx.qnx710.target.connectivity.pci.core.group. This doesn't include the QNX SDP 7.1 Connectivity - PCI Server Module QVM Support package, com.qnx.qnx710.target.connectivity.pci.srvrmod_qvm_support, which is optional. The hardware module packages listed in the second table are all optional, except for the QNX SDP 7.1 Connectivity - PCI HW Module x86 com.qnx.qnx710.target.connectivity.pci.hw.pci_hw_x86, which can be installed manually as required.

---

PCI Hardware Module Packages:

To see a list of the contents of a package, right-click it in the QNX Software Center, choose Properties, and then click Package Contents.

Installing this update

PCIv2 hardware modules are incompatible with the PCIv3 subsystem packages. Installing PCIv3 packages, therefore, can cause issues for those who are currently using PCIv2. If you install this update, PCIv3, you have to ensure that your hardware module is also updated to version 3 e.g., com.qnx.qnx710.target.connectivity.pci.hw.pci_hw_ti_j7_3.0.0.00061T202306212213L. PCIv2 hardware modules are runtime incompatible with the PCIv3 server.

If you wish to keep using PCIv2, then you can do one of the following:

• Do not install PCIv3 before doing the steps below.
• Move your PCIv2 binaries to a different directory.
• Create a separate SDP 7.1 installation and then install PCIv3.

Using this update with existing BSPs

You may need to update the buildfiles for the BSPs depending on how you specified the older BSP filenames. If you specified the filenames without a version, e.g., libpci.so, then you do not need to update the buildfile to use libpci.so.3. If you specified the filenames with a version, e.g., libpci.so.2.3, then you need to update the BSPs to use libpci.so.3.

If you are using a BSP that has pre-built drivers linked against libpci.so.2.3, you can continue using them with PCIv3 if you install the QNX SDP 7.1 Connectivity - PCI Shim Library package, com.qnx.qnx710.target.connectivity.pci.libshim, along with libpci.so.3 to satisfy the link dependency of the driver and allow it to run with the PCIv3 server. In this case, you have to use the shim version of libpci.so.2.3 as well as libpci.so.3 on your target and ensure your build file contains both names libpci.so.2.3 and libpci.so.

New features

• The latest class codes and capability IDs have been added to the PCI-SIG 1.13 release. (Ref# J2906602)
• The error event handling server module and its associated functionality is available for customers. (Ref# J2904860)
• Support for Samsung has been added in the PCI database. (Ref# J2878060)
• Error event server module has been added to PCIv3. (Ref# J2877177)

Fixed issues

• Hardware modules were modified to fix the issue with incorrect address calculation used to establish the MSI inbound address match value. (Ref# J2929189)
• Issue with PCI server modules attempting to operate on devices which are not part of the segment managed by the server instance has been resolved. (Ref# J2928839)
• The PINFO of capability module has been modified to show the correct descriptions. (Ref# J2927098)
• Issue with the Hardware module support function for syspage asinfo entries has been fixed. (Ref# J2919360)
• PCI-server can now detect all PCI Bridges in x86-64 i7 target in mainline. (Ref# J2913872)
• The address space attribute setting in some hardware modules has been fixed. (Ref# J2907913)
• The issue with cfgspace_map_add() not checking for non-existent entries has been resolved. (Ref# J2906092)
• The issue related to the second PCIe controller (PCIe1) in the NXP S32G SoC was resolved. (Ref# J2905737)
• The NXP S32G hardware module has been updated so that it uses common implementation of cfgspace_*() functions. (Ref# J2905701)

Technical support

For information about technical support for any QNX product, go to the Developers menu on our website (www.qnx.com). You'll find a wide range of support options, including community forums.