QNX Technical Articles
QNX CAR™ platform 2.0 Reference Release: Release Notes
Date of this Edition: February 12, 2013
These notes accompany the QNX CAR platform 2.0 Reference Release.
What's in this release?
The following packages are available as part of the QNX CAR platform 2.0 RR. You can obtain these packages from the QNX Download Center.
QNX CAR platform 2.0 RR – Linux Hosts
- A single installer for the QNX CAR application platform and the QNX CAR development platform for Linux hosts.
QNX CAR platform 2.0 RR – Windows Hosts
- A single installer for the QNX CAR application platform and the QNX CAR development platform for Windows hosts.
QNX CAR Interface for Apple iPod 2.0 RR
- An optional package that provides support for the control of iPods.
QNX CAR Multimedia Codec for WMA9 2.0 RR
- An optional package that that provides a software decoder for Microsoft Windows Media Audio 9 format files and streams.
Known issues
This release contains known issues in the following areas. Not all items listed are bugs or problems.
Note: We're actively investigating all known issues.
Known issues: Installing and uninstalling
- The manifest files included in the installation include some errors. On Windows,
the checksum listed for the target/qnx6/usr/include/qconfig.mk
file is incorrect. The correct checksum is: 11112 1645626833. On Linux, the
following files listed in the manifest are not actually installed:
- host/linux/x86/usr/bin/ntoarm-c++ — 266424 3928282770
- host/linux/x86/usr/bin/ntoarm-c++-4.6.3 — 266424 3928282770
- host/linux/x86/usr/bin/ntoarm-cpp — 266072 2459408295
- host/linux/x86/usr/bin/ntoarm-cpp-4.6.3 — 266072 2459408295
- For information on installing the development environment, see the QNX CAR platform 2.0 RR installation notes for your host system.
- Ensure that you close all instances of the QNX CAR platform before uninstalling. (Ref# 260491)
- On Windows XP, the default path for the workspace directory contains spaces,
causing problems with some command-line utilities. (Ref# 255721)
Workaround: Change the default workspace directory to another path that doesn't contain spaces.
- On 64-bit Ubuntu 12.04, the installer fails to find the Java path. (Ref#
226222) Workaround: Run the following command and install the missing libraries prior to launching the installer:
sudo apt-get install ia32-libs
- If you install the QNX CAR platform on a host with an existing installation of QNX SDP 6.5.0, you will be presented with a dialog that asks if you want to reuse the same QNX_CONFIGURATION directory. Choosing "Yes" requires administration privileges to update the existing configuration directory. Choosing "No" causes the installer to use the QNX CAR2 development platform configuration settings. (Ref# 260840)
- On Linux, the installer doesn't create any shortcuts. Symbolic links are created for the root user. Nonroot users must start the IDE by specifying the full path to the qde executable. (Ref# 226648)
- On Windows 7, the installer might not display the license activation dialog. If the installer doesn't launch the license activation program and your license key requires activation, follow the instructions that are listed in the summary panel at the end of the installation. (Ref# 250676)
- The disk space requirement quoted in the Linux installer is incorrect. The correct information is listed in the installation note. (Ref# 259685)
- You have to run the Linux installer from the directory that it's in, otherwise it will fail. (Ref# 261028)
- You need to set QNX_CONFIGURATION before running addLicense. See the instructions in the installation note for your host platform. (Ref# 262816)
- On Linux, if you earlier installed the QNX Software Development Platform and you used the same
QNX_CONFIGURATION directory when you installed
the QNX CAR platform, and you then uninstall QNX SDP, its uninstaller
removes that directory, including the licenses, licensing binaries, and so on for the
QNX CAR platform. (Ref# 264895)
Workaround: Don't uninstall QNX SDP while the QNX CAR platform is still installed, or back up the directory identified by QNX_CONFIGURATION, uninstall QNX SDP, and then restore the directory.
Known issues: General
- If the path to target/boards/<platform>/ifs is too
long, mkifs returns an error stating that the arguments are
too long. (Ref# 200543)
Workaround: Link /tmp/target to the target directory and run the makeimage command from the tmp/target/boards/<platform>/ifs location.
- If you switch themes frequently, memory usage will increase significantly. Switching themes 20 times consumes on the order of 50 MB of memory. After five to ten minutes the memory will return. This is unlikely to occur during normal usage. (Ref# 251103)
- With some PandaBoard Rev. A3 boards, Lilliput touchscreen displays may show flickering and tearing while playing video. This issue affects only boards with yellow border around the HDMI port. (Ref# 255818)
- To ensure the databases are backed up to save settings between sessions, always shut down the system either by running the reboot script at the terminal or by using the Shutdown application on the display. If you run the shutdown script at the terminal, the database won't be backed up and the settings won't be saved. (Ref# 258441)
- Applications with IDs longer than 48 characters can't be started because the
Launcher can't create the associated directory in //accounts/1000/appdata/.
(Ref# 190345)
Workaround: Ensure the app ID is less than 48 characters long.
- If the system time is not set, the Home Screen might not start up properly.
(Ref# 216622)
Workaround: Run the reboot script to set the system time.
- Some apps might flicker when loading. (Ref# 238728)
- In the Personalization screen, names that include the backslash character ("\") and other special characters don't display correctly in the status bar. (Ref# 267213)
- On the Settings screen, if you hold the Personalization button for longer than two seconds, the system won't open the Personalization screen. (Ref# 267218)
- In the Personalization screen, if you change the default name without closing the virtual keyboard and then change the theme, duplicate dialogs will be displayed. (Ref# 267219)
Known issues: Automatic speech recognition
- Vlingo might return unexpected strings in response to voice commands, causing
ASR not to behave correctly. (Ref# 160497) Workaround: Add the strings returned by Vlingo to the asr-car.cfg file. To see what Vlingo is returning, run
sloginfo -wm30 | grep "parse utterance"
Known issues: Bluetooth
- If you connect a BlackBerry Bold 9900 phone, disconnect using the phone's
interface, and then reconnect, only the HFP service will reconnect (MAP and PBAP
will not be connected). (Ref# 242743)
Workaround: Always disconnect the phone using the HMI.
- If you change the setting for CAR
BLUETOOTH NAME, the new name will not show on the connected device. (Ref#
256756)
Workaround: Reboot the QNX CAR system.
- If you receive emails while MAP is synchronizing, there is a chance that MAP
synchronization will fail (address book and HFP will still work). If you
experience this condition, and you then disconnect and try to reconnect, the
pairing will get stuck. Approximate failure rates:(Ref # 259590)
- one email received during synchronization will cause failure approximately 20% of the time
- ten emails received during synchronization will cause failure approximately 50% of the time
- Emails from a paired BlackBerry Bold 9700 phone might not display correctly if they contain embedded HTML or images. (Ref# 260465)
- Pictures for contacts in connected phones might not appear in the Address book. (Ref# 211851)
- SPP can't be disconnected from the HMI. (Ref# 236550)
Workaround: Disconnect using the phone.
- If you start synchronizing the contacts from a connected phone, then disconnect it before the synchronization completes, then connect another phone, you could see partial contact information from both phones. (Ref# 240581)
- If you connect multiple devices, then disconnect one, the available device list in the Preferred Device screen might not refresh properly. (Ref# 244039)
Known issues: Browser
- There are currently no certification dialogs available in the browser application. If you go to a website that requires verification of an SSL certificate, the browser application will hang. (Ref# 259702)
- Browser geolocation is not supported. (Ref# 208430)
Known issues: Compiler, tools, and utilities
- Due to known issues with System Builder, we recommend you use the mktar utility to build your software images. (Ref# 257415)
- Watch points are not supported for ARM. (Ref# 259564)
- To debug core files, use the C/C++ QNX Postmortem Debugging option in the launch configuration dialog of the QNX Momentics IDE. This option is not currently mentioned in the QNX Momentics Help. (Ref #250509)
- If you use the Memory Analysis tool with the control thread enabled, no
information will be returned for bins, bands, or usage. (Ref# 252156)
Workaround: Disable the control thread.
- The Code Coverage tool might not show any information for C++ shared libraries. In addition, executables being examined with the Code Coverage tool might crash. (Ref# 259211)
- The mktar image building utility doesn't work correctly on
Red Hat Enterprise Linux 5 or CentOS 5, because the included version of Python
(2.4) is insufficient. (Ref# 222276, 231786)
Workaround: Install Python version 6 or higher.
- On Linux, after you import and build a BSP in the System Builder, the files in
the prebuilt directory lose their executable bit. (Ref#
252984)
Workaround: Change the permissions to add the executable bit before you add the files to the IFS image.
- If you want to build any of the following example projects, you must select the
ARM build variant (otherwise, they will fail):
- QNX Example Project - Detecting Runtime Errors
- QNX Example Project - Inspecting Allocations and Memory Leaks
- QNX Example Neutrino Mutex Project
- QNX Example Neutrino Resource Manager Project
- QNX Example Neutrino Threads Project
- Disconnecting from an executable while it is being debugged will cause it to
terminate. (Ref# 259773)
Workaround: Select . Under Termination, clear the check box labeled Terminate GDB when last process exits.
- Shortcut keys don't work as expected in the IDE. Shortcut keys might not trigger the assigned functionality, new shortcut keys
might not appear in the right-click menus, and conflicting key assignments might not be reported.
Workaround: Use the menu commands to perform operations in the IDE.
- The text in the IDE hover help is truncated. (Ref# 259496)
Workaround: Look up the function in the Neutrino Library Reference.
- When debugging, the Modules view doesn't show information for a shared library loaded as a DLL. (Ref# 259581)
Workaround: Click to update the Modules view.
- When debugging, the Modules view doesn't show information for the executable being debugged. (Ref# 259524)
- The Add Global Variables button in the Variables view
isn't functional. (Ref# 259784)
Workaround: Add global variables using the Expressions View.
- The SVN plugin is not included with the QNX Momentics IDE. (Ref# 247220)
Workaround:
- In the QNX Momentics IDE, select .
- Click Add and enter the URL http://download.eclipse.org/releases/indigo/ in the Location field. Enter a name, for example "Eclipse Indigo", and click OK.
- Wait for the list of plugins to populate. This may take several minutes
- Expand the Collaboration category and select Subversive SVN Team Provider
- Click Next and install the plugin.
- When prompted, restart the IDE.
- When prompted, install the SVN Kit plugin with the highest version number (and other plugins selected by default, such as the Subversive SVN Connectors plugin)
- When prompted, restart the IDE.
- Setting the refresh interval to a large number (for example, 999999999) causes the information in the System Summary view to refresh constantly. (Ref# 252137)
Workaround: Choose a smaller amount of time (tens of seconds) for the refresh interval.
- Setting the compiler/linker to use PIE causes the following compile error: "crt1S.o not found". PIE is not supported. (Ref# 258681)
- Managed Make C++ projects that are compiled as C++ GNU with exceptions fail to run. (Ref# 259430)
- Breakpoint thread filtering does not function properly. (Ref# 263994)
Known issues: Documentation
- For the latest product documentation, including corrections and additional content, see the online documentation on the QNX website.
- In the QNX Momentics IDE help, the Getting Ready section of the Getting Started Guide says to "obtain the install image from TBD". For installation instructions, see QNX CAR platform 2.0 RR -- Installation Instructions on Foundry 27. (Ref# 257225)
- The IDE User's Guide in the QNX Momentics IDE help refers to Profiles that aren't applicable to this release, specifically C/C++ Developer (CDT), QNX Developer, and QNX System Developer. The online verion of the documentation has been corrected. (Ref# 257413)
- From the Welcome page of the IDE, if you select , you will be presented with a "Topic not found" error. (Ref# 263565)
Known issues: HTML5 and WebWorks
- JNext dependencies available on the installed system might not be found by the
WebWorks application, even when the directory settings are correct.(Ref# 232959)
Workaround: Move the JNext plugins to the <appname>/native/plugins/jnext/ directory.
Known issues: iPod
- Only iPod iOS v5.1 was tested in this release. (Ref# 267777)
- If an iPod is connected to a hub on the USB host port (EHCI) on a PandaBoard,
network connectivity can be lost due to conflicts with the SMSC driver. (Ref#
244798)
Workaround: Use a type "A" USB cable to connect the hub to the USB OTG port.
- Audio files without ID3 tags are not synchronized with the database. This is an expected limitation when working with iPods that have operating systems older than iOS 5. (Ref# 147194)
- Album art is not available for iPods that have operating systems older than iOS 5. (Ref# 267838)
- The song duration that is displayed might not be correct. (Ref# 244784)
- To enable iPod album art, uncomment the following lines in the /etc/system/config/md.conf
file:
#[plugin] #dll=mm-mdp-ipod.so
(Ref# 267751)
Known issues: Multimedia
- If you seek back to an earlier video while playing a playlist of videos, the playback might not resume correctly. (Ref# 263180)
- While playing the QNX CAR Jeep video, if you set the playback speed to anything other than 1000 (normal speed), playback might stop. (Ref# 263209)
Known issues: Navigation system
- If you modify
/apps/Navigator.testDev_Navigator__a4514a37/native/js/tablist.json
to set type to be local_oop (Out of Process),
the eb-navigation process crashes on bootup. (Ref# 250885)
Workaround: Do not set type to local_oop. However, you can still set other tabs as Out of Process, which will still significantly help performance.
- EB navigation's memory consumption might increase significantly during long navigation sessions. (Ref# 237301)
Known issues: RealVNC
- If you disconnected the phone from the USB hub while a RealVNC session is in
progress, the automotiveViewer will hang. (Ref# 260480)
Workaround: End the RealVNC session before disconnecting the phone. Reboot the car system if it hangs.
- Currently there is no way to activate the Home,
Back, and Menu buttons on a device
connected via VNC. (Ref# 260484)
Workaround: Press the appropriate button on the phone itself.
Known issues: Sabre Lite i.MX6
- The Settings app isn't available for the Freescale Sabre Lite i.MX6 board. (Ref# 260801)
- Software Update doesn't work on the Sabre Lite i.MX6 board, and has been disabled. (Ref# 260833, 264163)
- Some Sabre Lite i.MX6 version 1.0 boards experience GPU lockup with GLES apps and the EB navigation app. (Ref# 258810)
- On the Sabre Lite i.MX6 board, if you run the HTML Gears demo, and then play a video, some of the Gears graphics might show through the multimedia app screen. (Ref# 267327)
- Running the EB navigation app on Sabre Lite i.MX6 version 1.2 boards may cause the kernel to crash or the EB navigation app to core dump. (Ref# 268790, 268796)
- In some instances, rebooting the QNX CAR system after a crash on Sabre Lite i.MX6 version 1.2 boards
results in a black screen and nonfunctional graphics applications.
Workaround: Reboot again, using the shutdown command to reset the board. Sometimes multiple reboots are required.
Supported media devices and file formats
The QNX CAR platform 2.0 RR currently supports the device types, filesystems, codecs, and video formats listed in this section.
- Device types
-
- USB
- SD
- iPod
- DLNA/uPNP
- Filesystems
-
- DOS FAT16/32
- Power-Safe filesystem (fs-qnx6.so)
- QNX 4
- MAC
- EXT 2
- iPod
- ISO-9660, including Joliet (for peripheral devices, such as optical drive CDs or DVDs)
- UDF 2.00 and 2.01 (for peripheral devices, such as optical drive CDs or DVDs)
- Codecs/containers
-
- AAC
- MP3
- WMA
- WAV
- Vorbis
- ASF
- MP4
- MP3
- OGG
- FLV
- Video formats
-
- MP4
- H.264
- MPEG1/2
- DIVX/XVID
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.
You can also view the forums on our community portal host, Foundry 27, http://community.qnx.com. There are forums for specific topics, including the QNX Neutrino RTOS, development tools, networking, Board Support Packages, and so on.
Where can I get more information?
The latest documentation for the QNX CAR application platform 2.0 RR is available in the Infocenter.
This live online documentation includes:
- The Getting Started Guide and the Architecture Guide, which provide overview information and steps to get your first projects up and running.
- Information about customizing or building your own human-machine interface (HMI).
- API references, including documentation about the Persistent Publish/Subscribe (PPS) objects on the system.
- Guides and references for the QNX Neutrino RTOS.
For additional information and updates, check the QNX CAR platform 2.0 Reference Release project home page on our community portal host, Foundry 27.