Home
Developer Resources
Technical Articles

QNX Technical Articles

QNX Platform for ADAS 1.0: Release Notes

Date of this edition: June 17, 2016

QNX Platform for ADAS 1.0 (ADAS stands for Advanced Driver Assistance System) is a platform that helps you to build advanced driver assistance systems. The QNX Platform for ADAS includes:

  • the Vision Platform (Camera Framework)
  • SOME/IP
  • binaries required for the platform

Note: For the platform, you can use third-party vision algorithms. For more information, see the installation notes.

You can install the QNX Platform for ADAS 1.0 on the following development hosts:

  • Microsoft Windows 7 Professional 32- and 64-bit, Vista Business 32- and 64-bit, XP Professional SP3 or 2000 SP4
  • Red Hat Enterprise Linux 5.4 Desktop 32- and 64-bit, Red Hat Fedora 12, Ubuntu Workstation 9.10, 11.04, and 12.04 32- and 64-bit, or openSUSE 11.2

For information on the prerequistes required to install the QNX Platform for ADAS 1.0, see the installation note.


Caution:
  • If you installed an alpha version or trial version of this software, uninstall it before installing this version.
  • Make sure that Plug and Play OS is disabled in the BIOS before you run QNX Neutrino RTOS on your target.

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.

For the most up-to-date version of these release notes, go to our website, www.qnx.com, log in to your myQNX account, and then go to the Download area.

Contents:

Baseline boot times

The following are the baseline times for a camera to get its first image buffer (video frame) when the board is powered up. These times were taken with different camera configurations using a reference image built with this product. The reference image was run on a Jacinto 6 EVM (Revision G) with a Vision board, and booting with an eMMC. The times you get many vary based on what you have built into your image and the number of processes and applications that you start when the board boots. For example, there may be additional time required to show the content on the display when additional services are started, or boot up times can be improved if services are loaded by the IFS.

Camera and configuration Time (seconds)
Single Leopard USB Camera 2.252077
Single FPD-Link III Camera connected via parallel 1.253481
Single FPD-Link III Camera connected via Vision Board 1.401765
Four FPD-Link III Camera connected via Vision Board Camera 1: 1.788707

Camera 2: 1.823498

Camera 3: 1.858433

Camera 4: 1.893994

Known issues

The QNX Platform for ADAS 1.0 contains the following known issues:

Vision Platform

The Camera Framework is provided as part of the Vision Platform.

  • Unable to start and stop viewfinder for 4x720p file cameras

    If you have four file cameras configured to play 720p resolution video and all four viewfinders have been started, when you stop one of the viewfinders, starting the viewfinder again occasionally fails.

    Workaround: Start the viewfinder a second time after a short period and it should start the second time.

    (Ref# J1518476)

SOME/IP

  • Some tests from the vsomeip test suite don't run

    The following vsomeip tests don't run on a target:
    • Test #13 big_payload_test_external
    • Test #14 client_id_test

    (Ref# J1519406, J1519417

Jacinto 6

  • USB 3.0 (Superspeed) doesn't work on the Jacinto 6 EVM board

    The Jacinto 6 EVM board doesn't have a functional USB 3.0 (Super Speed) driver available. For that reason, USB 3.0 speeds can't be obtained. This means that when you use a Leopard USB camera (with the OV10635 image sensor) connected to the USB 3.0 port (SuperSpeed USB), you aren't able to stream 720p video at 30 frames per second (fps), which requires USB 3.0 speeds. You can stream 720p at 10 fps (USB 2.0-supported speed).

    (Ref# J1461578, J1314145)

Sample applications

  • Video from file cameras isn't supported for the Surround view application

    The video played from a file camera doesn't render due to a current limitation with the algorithms provided by Texas Instruments.

    (Ref# J1532919)

Image generation

  • Generated target image missing configuration files

    When you use the default build files to generate an image, applications use the default FPD-Link III camera or file camera configurations won't work because the single_cam.conf and file_cam.conf configuration files aren't specified in the basefs.jacinto6evm.adas.config.xml in your installation. Both configuration files are available on your host, but if they aren't specified in a fileset, they won't be included as part of the generated image.

    Workaround: On your host, edit the $QNX_DPELOYMENT_WORKSPACE/ADAS/infra/boards/jacinto6evm/basefs.jacinto6evm.adas.config.xml and add the following lines between the <fileset> elements:

    ...
    ...
    <file name="etc/system/config/file_cam.conf" uid="root" gid="nto" mode="0644" />
    <file name="etc/system/config/single_cam.conf" uid="root" gid="nto" mode="0644" />
    ...
    ...

    For more information about filesets and adding content to an image, see "Filesets" and "Content files, directories, and symbolic links" sections in the Modifying Content chapter of Working with Target Images.

    (Ref# J1534034)

Getting started with the documentation

After you've installed QNX Platform for ADAS, you'll find a set of HTML documentation in the Integrated Development Environment's help system. To start the IDE on Linux, use this command:

base_directory/run-qde.sh

On Windows, use the desktop icon or run:

base_directory\run-qde.vbs

where base_directory is where you installed the software.

For the most up-to-date version of the documentation, see the QNX Product Documentation website.

For the most up-to-date version of the installation and release notes, go to our website, www.qnx.com, log in to your myQNX account, and then go to Downloads > QNX Platform for ADAS 1.0.

Building target images

The following are the additional tasks that can be done before you can build a target image.

Install Python 2.7.5 to run mksysimage

To run the mksysimage.py script to build a target image, you must install Python 2.7.5 on your host system. Python 2.7.5 is a later version than the one provided with QNX SDP 6.5.0 SP1. To run the mksysimage.py script after you install Python, run this command on your host computer:

  • On Windows: [path of your Python 2.7.5 installation]\python mksysimage.py
  • On Linux: mksysimage.py

For more information about building target images, see the Working with Target Images guide for this release.

Additional package is required to build a reference image

To build a target image with the QNX Platform for ADAS 1.0 for ARMv7 targets (e.g., Jacinto 6 EVM), you must install the Texas Instruments Codec Components for the QNX Platform for ADAS 1.0. This package contains the necessary binaries to encode and decode video. For information about how to install this package, see its installation note.

Configure the startup script to have a carveout of 130 MB of memory

To use the QNX Platform for ADAS 1.0, you require a 130 MB carveout starting at address 0xB7B00000 on the board. When you build an target image, you must modify the startup script in the IFS build file to specify a 130 MB carveout (use -r0xB7B00000,0x8200000,1) as follows:

startup-dra74x-vayu-evm -n852,668 -J -r0xB7B00000,0x8200000,1  -r0x85800000,0xFC00000,1 -r0xA0000000,0x2000000,1 r0xA2000000,0x4000000,1

In addition to modifying the IFS build file, you must also install the InfoADAS and its associated patch from Texas Instruments, the Texas Instruments Codec Components for the QNX Platform for ADAS 1.0, and the QNX Modifications to Texas Instruments InfoADAS for the QNX Platform for ADAS 1.0. For information about how to install the necessary packages on your host system, see the installation note for each package.

Building an image doesn't include sample applications

By default, the build files provided with this release don't include the sample applications that use third-party software:

  • Pedestrian detection
  • Surround view
  • Street sign and lane departure

If you want to include the sample applications in your image or have code that uses the same InfoADAS libraries and Vision SDK provided from Texas Instruments or algorithms from Itseez, you must download additional packages and follow the installation note as follows:

  • For the Pedestrian detection and Surround view applications, you require the QNX Modifications to Texas Instruments InfoADAS for the QNX Platform for ADAS 1.0 package. For information about how to install this package, see its installation note.
  • For the Street sign and lane departure application, you require the Itseez Package for the QNX Platform for ADAS 1.0. For information about this package, contact your QNX Software Systems sales representative.

After you install and build the packages, you must modify the QNX_DEPLOYMENT_WORKSPACE/infra/boards/jacinto6evm.ext/os.xml file and remove the XML comment tags (<!‑‑ and ‑‑>) from the following lines to include the filesets for those packages into the image that you build:

...
...
<include-fileset name="basefs.adas.infoadas"/>
<include-fileset name="basefs.adas.itseez"/>
...
...
<include-fileset name="rootfs.adas.itseez"/>
<include-fileset name="rootfs.adas.infoadas"/>
...
...
	    
For more information about filesets and building images, see the Working with Target Images guide for this release.

Technical support

To obtain technical support for any QNX product, visit the Support area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.

For questions about installing and using QNX SDP, see the Getting Started forum on our Foundry27 site, http://community.qnx.com. There are other forums for specific topics, including the QNX Neutrino RTOS, development tools, networking, Board Support Packages, and so on.