This product comes with a few main packaging options, which install other components that are also provided as separate packages.
In this release, we provide a QNX Software Center 2.0 - Typical Configuration and QNX Software Center 2.0 - Locked Typical Configuration packages. Both packages install the necessary software components and documentation required for you to start development on your host machine, but it doesn't install the components to generate your own image or reference images. For information about what's installed in the Typical Configuration and Locked Typical Configuration packages, see “Typical Configuration installations.”
To generate your image, you must select and install a separate Hardware Support package in the QNX Software Center. You only require Hardware Support packages to build an image for the target you want to use. For more information about hardware images, see “Hardware Support packages.”
Reference images are installed separately. The reference image you install depends on the hardware target you want to work with. A reference image provides a functional image that runs on a target so that you can see reference applications run or use for developmental purposes. For more information, see “Understanding Reference Images.”
| Feature | Base package | Sensor package | Hardware Support | OpenCV support | Robot OS and Publisher Example |
|---|---|---|---|---|---|
| Codecs, GPU, and Display driver support | X | — | — | — | — |
| Sensor Framework (Camera library) | X | — | — | — | — |
| Sensor Framework (Sensor and ADAS library) | — | X | — | — | — |
| Radar and lidar interfaces (includes required drivers) | — | X | — | — | — |
| Image Generation | — | — | X (A different hardware support platform package is available for each hardware platform) | — | — |
| Robot OS | — | — | — | — | X |
| Vision processing algorithms | — | — | — | X | — |
| Reference Applications | Camera example, Camera MUX 2x2 | Sensor example, ADAS example, Publish and Subscribe Example | — | Algorithm libraries (finger count, driver monitoring, and motion detection, traffic light detection) | ROS sensor publisher example |
| Reference Applications (source package) | Camera Example, Camera MUX 2x2 | Sensor example, ADAS example | — | Algorithm libraries (finger count, driver monitoring, and motion detection) | ROS sensor publisher example |
| Third-party software | — | LZ4, Pixman, libmodbus, Cairo, VSOME/IP, Fast RTPS | Depending on the Hardware Support package, one of these
third-party softare components are installed:
|
OpenCV | Robot OS (ROS) Kinetic Kame libraries. |
| Component | Description |
|---|---|
| OpenCV |
Vision-processing software that provides APIs that you can use to implement your own algorithms. As part of installing this package, other third-party software is installed because this package depends on them. |
| Robot OS (ROS) Kinetic Kame libraries | ROS library and dependent libraries. As part of installing this package, other third-party software is installed because this package depends on them. The dependencies installed are Boost, Console Bridge, Flann, libusb, libUUID, LZ4, PCL, POCO, QHull, TinyXML, urdfdom, YAML. Note: This package must be installed separately and isn't installed as part of the Base, Sensor, OpenCV support, or any of the Hardware Support packages.
|
| FastRTPS | Library for supporting FastRTPS protocol through the use Platform-independent Publish Subscribe (PiPS). |
| libmodbus | Software library to send/receive data according to the Modbus protocol. |
| LZ4 | Reference library for the LZ4 lossless compression algorithm. |
| Pixman | Low-level library for pixel manipulation. |
| RTI DDS Pro | Data Distribution Service (DDS). This third-party software is available as a binary in the reference images, but isn't installed. To access this software, contact RTI. |
| NXP S32V APEX | Libraries for native access to vision accelerators on the NXP S32V hardware platform. |
| Video Codec for ASRock Beebox | H.264 video encoders and decoders for the Intel platforms based on Apollo Lake SoC, such as the ASRock Beebox hardware platform. |
| Video Codec for Renesas | H.264 video encoders and decoders for the Renesas H3 Starter Kit and R-Car V3M Starter Kit boards. |
| VSOME/IP | Package installed to support SOME/IP through the use Platform-independent Publish Subscribe (PiPS). |
You can install using a QNX Software Center 2.0 - Typical Configuration or QNX Software Center 2.0 - Locked Typical Configuration installation. The difference between the two installlations is that the Locked Typical Configuration installation doesn't allow the components in the installation to be updated. This is useful if you want to use the same versions of the components at the time of product release. If you don't use a locked version, the components can be updated based on the update policy you set in the QNX Software Center when you install the package. When you install a Typical Configuration (or Locked Typical Configuration), it installs the following packages:
Hardware Support packages are required to build your own reference images. The Hardware Support package you choose depends on the hardware platform you want to work with. Available are locked versions of Hardware Support packages, which do not allow components in installation to be updated. This is useful if you want to the same versions of the components at the time of release. If you don't use a locked version, the components can be updated based on the update policy you set in the QNX Software Center when you installed the package. Usually, you install the Hardware Support package that matches the hardware platform you are working with. For example, if you are developing on the Renesas R-Car H3 Starter board, you would install the corresponding Hardware Support - Renesas R-Car H3 Support package Here are the details of what installed in each of the Hardware Support packages: