QNX Technical Articles

Date of this edition: May 13, 2010

Target OS: This software is compatible with target systems running QNX^® Neutrino^® 6.4.0, 6.4.1, or 6.5.0.

Host OS: You must have already installed the QNX^® Software Development Platform 6.4.0, 6.4.1, or 6.5.0 as a self-hosted QNX Neutrino system, or on one of the following hosts:

---

A client application compiled against QNX Aviage Multimedia Suite (MME) 1.0.n must be recompiled in order to work with QNX Aviage Multimedia Suite (MME) 1.2.0. You must update all system components to QNX Aviage Multimedia Suite 1.2.0. Your environment must not contain both 1.0.n and 1.2.0 multimedia components.

---

Required software

To support USB transport connections to iPods (“one-wire” connections), you need the following patch:

• deva-ctrl-ipod.so sound driver for iPod digital audio devices (Patch ID 1154).

Required disk space and dependencies

The table below lists the minimum disk space requirements (in megabytes) for installation of the different MME components, as well as component dependencies.

Contents...

• Installing the QNX Aviage Multimedia Suite
  • Upgrades
  • On a QNX Neutrino host
  • On a Linux host
  • On a Windows host
  • Installing optional components
• Uninstalling the QNX Aviage Multimedia Suite
  • Deleting the MME database tables
  • On a QNX Neutrino host
  • On a Linux host
  • On a Windows host
  • Uninstalling optional components
• Documentation
• Technical support

For information about what's in this release, see the Release Notes. For the latest version of this Installation Note or the Release Notes, go to our website, www.qnx.com, log into your myQNX account, then go to the Download Center.

Installing the QNX Aviage Multimedia Suite

This section explains how to install the QNX Aviage Multimedia Core 1.2.0 and optional components. For detailed information about supported hosts and targets, see the release notes. For information about how to get the QNX Aviage Multimedia Suite's MME (MultiMedia Engine) up and running, see the chapter “Quickstart Guide” in Introduction to the MME.

Upgrades

If you are upgrading from an older version of the QNX Aviage Multimedia Suite, before you begin the installation you need to:

• remove the MME database tables and schema files
• uninstall the old QNX Aviage Multimedia Suite; see “Uninstalling the QNX Aviage Multimedia Suite” below

---

Before restarting the MME, you will also need to replace the QBD configuration file, qdb.cfg, as instructed in the Quickstart Guide chapter of Introduction to the MME.

---

On a QNX Neutrino host

1. Log in as root.
2. Log into your myQNX account on our website, then go to the Download Center.
3. Download the installation package, qnxaviage-mmedia-core-1.2.0-nnnnnnnnnnnn-nto.sh, where nnnnnnnnnnnn is an 12-digit build number. The package is in the form of a shell script.
4. Run chmod to make the script executable. For example:

   # chmod a+x qnxaviage-mmedia-core-1.2.0-200904231718-nto.sh

5. Run the script at the system prompt. For example, on QNX Neutrino 6.4.0 or 6.4.1, type:

   # ./qnxaviage-mmedia-core-1.2.0-200904231718-nto.sh

   On QNX Neutrino 6.5.0, invoke the installer using the legacy behavior of the head utility:

   # HEAD_LEGACY=1 ./qnxaviage-mmedia-core-1.2.0-200904231718-nto.sh

6. Follow the instructions on your screen.

On a Linux host

---

If you've installed more than one version of QNX SDP on your system so that they coexist, see “Coexistence on Linux,” below.

---

1. Log in as root.
2. Log into your myQNX account on our website, then go to the Download Center.
3. Download the installation package, qnxaviage-mmedia-core-1.2.0-nnnnnnnnnnnn-host.bin, where host is linux, and nnnnnnnnnnnn is an 12-digit build number. The package is in the form of a .bin script.
4. Run chmod to make the script executable. For example:

   # qnxaviage-mmedia-core-1.2.0-200904231718-linux.bin

5. Run the script at the system prompt. For example:

   # ./qnxaviage-mmedia-core-1.2.0-200904231718-linux.bin

6. Follow the instructions provided by InstallShield.

Ubuntu hosts

On Ubuntu hosts, you must run the installation script with the sudo command -E option in order set the correct environment for the installation. For example:

# sudo -E ./qnxaviage-mmedia-core-1.2.0-200904231718-linux.bin

Coexistence on Linux (Ref# 73411)

It's possible to have more than one version of the QNX Software Development Platform installed on your system, and it's possible to install QNX Aviage products for each version of QNX SDP. However, due to a limitation in InstallShield, you have to take some extra steps installing QNX Aviage products on Linux hosts.

When two or more versions of QNX SDP coexist on Linux, you use the following command to switch between configurations to set up the environment in the current shell:

eval `qconfig -n "installation_name_as_displayed_by_qconfig" -e`

When you launch any of the QNX Aviage installers from that shell, the environment picked up by InstallShield is whatever version of QNX SDP you installed last, not the version that you selected using the command above.

For example, if you install QNX SDP 6.4.0, then QNX 6.4.1, and you then choose 6.4.0 and try to install a QNX Aviage product on the 6.4.0 baseline, the installation location displayed by the installers isn't /opt/qnx640 (as expected), but /opt/qnx641.

In order to work around this issue, you must edit /etc/profile.

---

We recommend that you save a copy of this file before you edit it.

---

Edit /etc/profile, and find the section that looks like this:

# Begin INSTALLSHIELD Environment Variable Section
# Do not edit this section manually.
# var 0 QNX_CONFIGURATION=/etc/qnx
QNX_CONFIGURATION=/etc/qnx
export QNX_CONFIGURATION

# var 0 QNX_TARGET=/opt/qnx641/target/qnx6
QNX_TARGET=/opt/qnx641/target/qnx6
export QNX_TARGET

# var 0 MAKEFLAGS=-I/opt/qnx641/target/qnx6/usr/include
MAKEFLAGS=-I/opt/qnx641/target/qnx6/usr/include
export MAKEFLAGS

# var 1 : PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/etc/qnx/bin:/root/bin:/etc/qnx/bin:/root/bin:/opt/qnx641/host/linux/x86/usr/bin:/etc/qnx/bin
PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/etc/qnx/bin:/root/bin:/etc/qnx/bin:/root/bin:/opt/qnx641/host/linux/x86/usr/bin:/etc/qnx/bin
export PATH

# var 0 QNX_HOST=/opt/qnx641/host/linux/x86
QNX_HOST=/opt/qnx641/host/linux/x86
export QNX_HOST

# var 1 : LD_LIBRARY_PATH=echo $LD_LIBRARY_PATH:/opt/qnx640/host/linux/x86/usr/lib:/opt/qnx641/host/linux/x86/usr/lib
if [ -z "echo $LD_LIBRARY_PATH" ]
then
LD_LIBRARY_PATH=/opt/qnx640/host/linux/x86/usr/lib:/opt/qnx641/host/linux/x86/usr/lib
else
LD_LIBRARY_PATH=echo $LD_LIBRARY_PATH:/opt/qnx640/host/linux/x86/usr/lib:/opt/qnx641/host/linux/x86/usr/lib
fi
export LD_LIBRARY_PATH

# var 0 QNX_JAVAHOME=/opt/qnx641/_jvm
QNX_JAVAHOME=/opt/qnx641/_jvm
export QNX_JAVAHOME

# End INSTALLSHIELD Environment Variable Section

Ignore the “Do not edit this section manually” instruction, and change (in this example) all occurrences of the 6.4.1 installation directory (/opt/qnx641) into the directory where you installed 6.4.0. Save your changes, and then continue with the installation.

Once you've installed the QNX Aviage product, you might want to restore /etc/profile from the backup that you made.

On a Windows host

---

If you have more than one version of QNX SDP that co-exist on your system (for example, 6.3.2 and 6.4.n, where n is the 6.4. version number): Set your configuration to 6.4.n (for example, 6.4.1) — you can't install a 6.4.1 product, such as the QNX Aviage Multimedia Suite, when the active version is QNX SDP 6.3.2. If you switch your configuration, you must log out of your user session and log back in before starting an installation.

---

1. Log in as a user with system-administrator privileges.
2. Log into your myQNX account on our website, then go to the Download Center.
3. Download the installation package, qnxaviage-mmedia-core-1.2.0-nnnnnnnnnnnn-win32.exe, where nnnnnnnnnnnn is an 12-digit build number. The package is in the form of an executable (.exe) file.
4. Double-click the file in Windows Explorer or run it at the command line.
5. Follow the instructions provided by InstallShield.

   ---

   Windows XP SP2 may display a security warning the first time you install the QNX Aviage Multimedia Suite. You can verify the checksums for the installation package when you download the file from our website.

   ---

Installing optional components

To install optional components, download the appropriate installation package and follow the instructions for installing the QNX Aviage Multimedia Core 1.2.0 for the host OS, substituting the appropriate name where required, and taking note of the information below.

Please note the following when installing QNX Aviage MME 1.2.0 optional components:

• The QNX Aviage Multimedia Core package must be installed before installing any of the other QNX Aviage Multimedia Suite packages.
• QNX Aviage MME 1.2.0 optional packages on targets with both QNX SDP 6.4.0 and QNX SDP 6.4.1 may erroneously overwrite already installed packages unless the active location is expressly specified.

  Thus, if you are installing an optional component on such a system, install from the command-line, specifying the installation location for all packages installed after the MME Core 1.2.0.

  For example, on a Linux system:

  # qnxaviage-mmedia-ipod-1.2.0-build#-linux.bin -P beanProduct.installLocation="/opt/qnx641"

  Or, on a Windows system, for example:

  C:\path> qnxaviage-mmedia-ipod-1.2.0-build#-win32.bin -P beanProduct.installLocation="C:\QNX641"

  Where /opt/qnx641 and C:\QNX641 are the location of the baseline installation under which you are installing the QNX Aviage Multimedia components.

---

Installing an optional package under QNX SDP 6.4.0 when optional packages are already installed under QNX SDP 6.4.1 requires the same workaround. The installer will not display an error message if there is an error (a typo) in the command-line argument. It will simply ignore the argument. Thus, a typo in the command-line argument specifying the installation location will have the same result as not specifying the installation location, and you may erroneously overwrite an already installed package.

---

---

If you are installing the QNX Aviage Multimedia Interface for TI OMAP Codec Engine, after the installation has completed you must also launch dsp-bins/omap3530image.exe and complete the click-through license agreement to install the sample DSP image on your host.

---

Dependencies

The QNX Aviage Multimedia Interface for iPod and the QNX Aviage Multimedia Interface for PlaysForSure packages are designed for use with the QNX Aviage Multimedia Core package. If you intend to use these packages independently of the QNX Aviage Multimedia Core package, please contact your sales support team.

For a complete list of dependencies between MME packages, see “Dependencies” in the Release Notes.

Uninstalling the QNX Aviage Multimedia Suite

This section explains how to uninstall the QNX Aviage Multimedia Core 1.2.0 and optional components.

---

Always uninstall the QNX Aviage Multimedia Suite optional components before uninstalling the QNX Aviage Multimedia Core 1.2.0. Always uninstall the QNX Aviage Multimedia Interface for WMDRM10-ND before uninstalling the QNX Aviage Multimedia Interface for PlaysForSure.

---

Deleting the MME database tables

When you uninstall the QNX Aviage Multimedia Suite, you must delete the old MME database tables and schema files, for example:

# cd /db

# rm *mme* usb*

If you do not know where the MME database and schema files are stored, see your qdb.cfg file for the location of your database. This file is usually located under /db (from the root directory).

On a QNX Neutrino host

1. Log in as root.
2. Go to the directory with the QNX Aviage Multimedia Suite uninstall script; for example:

   # cd

3. Run the uninstaller script:

   # /usr/qnx640/install/mmedia-core/1.2.0/uninstall.sh

On a Linux host

1. Log in as root.
2. Go to the base_dir/_uninstall/mmedia-core/1.2.0 directory, where base_dir is the directory where QNX SDP is installed; for example:

   # cd

3. Start the QNX InstallShield application:

   # /opt/qnx640/_uninstall/mmedia-core/1.2.0/uninstaller.bin

   InstallShield will now remove the MME.

---

In the case of coexistence, if you've installed MME 1.2 on multiple baselines (for example 6.4.0 and 6.4.1), before you uninstall make sure that you select as the active configuration the baseline from which you want to remove the MME or the MME component.

---

On a Windows host

1. Log in as a user with system-administrator privileges.
2. Open the Control Panel (e.g. on Windows XP: Start-->Control Panel-->Add or Remove Programs).
3. Select the QNX MME, then click the Change/Remove button.

---

In the case of coexistence, if you've installed MME 1.2 on multiple baselines (for example 6.4.0 and 6.4.1), don't use Add or Remove Programs to uninstall MME 1.2: Make sure that you select as the active configuration the baseline from which you want to remove the MME or the MME component. Launch the uninstaller directly. For example: qnx_base_dir\_uninstall\mmedia-core\1.2.0\uninstaller.exe.

---

Uninstalling optional components

To uninstall optional components, follow the uninstall instructions for the host OS, substituting the appropriate component path and name where required.

Documentation

The documentation for this release includes:

• This Installation Note — please read it before starting your installation.
• The Release Notes — please read them before starting your installation.
• Introduction to the MME — includes “MME Architecture”, the “MME Quickstart Guide”, and “MME Frequently Asked Questions”. Follow the instructions in the “Quickstart Guide” to get started with the MME.
• The MME API Library Reference
• The MME Configuration Guide
• The MME Developer's Guide
• The MME Utilities Reference
• The MME Technotes
• The MediaFS Developer's Guide
• The QDB Developer's Guide.

Technical support

If you have any questions, comments, or problems with a QNX product, please contact Technical Support. For more information, see the How to Get Help chapter of the Welcome to the QNX Software Development Platform guide or visit our website, www.qnx.com.