Developer Resources: Board support packages; Foundry27 projects; Forums

QNX Technical Articles

QNX® Momentics® 6.3.0 TI OMAP 5912 OSK BSP 1.0.0 Release Notes

QNX® Momentics® 6.3.0

Date of this edition: December 22, 2004

Target OS: QNX^® Neutrino^® 6.3.0 SP1

Host OS: Microsoft Windows XP SP1 or SP2; Microsoft Windows 2000 SP4; Sun Solaris 7/8; QNX^® Neutrino^® 6.3.0 SP1; Linux (Red Hat 8/9)

You need to have installed the QNX Momentics 6.3.0 SP1 before installing this BSP.
For information on installing this BSP, see the installation note.
If you install SP1, you should also install the latest version of the QNX Momentics Character Driver Development Kit (DDK), if you installed an earlier version of it. Significant changes have been made to this DDK; please see the Character DDK Release Notes.
For the most up-to-date version of these release notes, log into your myQNX account, and then go to the Download Center area of www.qnx.com.

What's in this BSP?
Location of source and documentation
Fixed issues
Known issues for this BSP
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.

What's in this BSP?

This BSP contains:

Binary components
Source code
Documentation.

The source code requires a BSP Source License.

Binary components

IPL
Startup
Serial driver
I2C driver
Audio driver
USB init utility
USB support (included with OS)
Graphics driver
Link library
DSP manager
Network driver (included with OS)
EIDE driver (included with OS).

Source code

IPL
Startup
Serial driver
Audio driver
Graphics driver
I2C driver
DSP manager
USB init utility
Network driver
Flash driver.

In order to run the audio driver, you'll need to use the DSP manager to download a DSP image to the OSK board. This DSP image is only available from Texas Instruments. The DSP image must match the Link library version 1.11 provided with this BSP. Please contact your Texas Instruments sales team to obtain it.

The flash filesystem library is included in the separately available Flash Filesystem & Embedding Technology Development Kit (TDK).

Documentation

TI OMAP 5912 OSK BSP readme (HTML)

Each BSP guide contains board-specific information and instructions on building an OS image for that particular board.

The procedure for building BSPs has changed since QNX Momentics 6.2.1. For instance, you must now run the . ./setenv.sh script before compiling your BSP source. If you fail to run this shell script prior to building the BSP, you can overwrite existing binaries or libs that are installed in $QNX_TARGET. For details, see the chapter "Working with a BSP" in the Building Embedded Systems manual (in the Documentation Roadmap page under the QNX Neutrino RTOS section).

Location of source and documentation

When you install BSPs, you'll find the source code and documentation in the following locations:

Windows hosts

Component	Location
Source code	`$QNX_TARGET\usr\src\archives\qnx\`
Documentation	`$QNX_TARGET\usr\help\product\bsp_index.html`
Release notes	`$QNX_TARGET\etc\readme\bsp`

QNX Neutrino, Linux, and Solaris hosts

Component	Location
Source code	`$QNX_TARGET/usr/src/archives/qnx/`
Documentation	`$QNX_TARGET/usr/help/product/bsp_index.html`
Release notes	`$QNX_TARGET/etc/readme/bsp`

To extract the source from the archive, use any application that supports the ZIP format (e.g. WinZIP). For more information, see the chapter "Working with a BSP" in the Building Embedded Systems manual.
The "roadmap" page (e.g. from the Windows XP start menu: Release notes-->All Programs-->QNX Momentics 6.3.0-->Documentation) contains links to the various HTML booksets that accompany the OS: System Architecture, Building Embedded Systems, Programmer's Guide, Library Reference, Utilities Reference, etc.

Binaries, buildfiles, IPLs, and other files

Depending on the particular BSP and type of driver, you'll find the files in these locations:

Windows hosts

File	Location
Buildfile	`$QNX_TARGET\cpu\boot\build`
IPL and/or startup	`$QNX_TARGET\cpu\boot\sys`
"`bin`" drivers (serial, flash, block, PCI, PCMCIA, USB)	`$QNX_TARGET\cpu\bin`
"`dll`" drivers (audio, graphics, network)	`$QNX_TARGET\cpu\lib\dll`

QNX Neutrino, Linux, and Solaris hosts

File	Location
Buildfile	`$QNX_TARGET/cpu/boot/build`
IPL and/or startup	`$QNX_TARGET/cpu/boot/sys`
"`bin`" drivers (serial, flash, block, PCI, PCMCIA, USB)	`$QNX_TARGET/cpu/bin`
"`dll`" drivers (audio, graphics, network)	`$QNX_TARGET/cpu/lib/dll`

Fixed issues

The BSP documentation is up-to-date for USB and I2C. (Ref# 20756)

Known issues for this BSP

In Microsoft Windows, certain programs (e.g. Norton Ghost) add directories inside double quotation marks (e.g. ...;"c:\Program Files\Norton Ghost\";...) to your PATH environment variable. This causes the Cygwin spawn() function to fail, which in turn causes cp to fail when called by ln-w. (Ref# 20046)
Workaround: Modify your PATH environment variable and remove any quotation marks.
In those instances where the the ROM monitor's MAC address is different from the one you pass in when running io-net, the host can cache the ROM monitor's address. This can result in a loss of connectivity.
Workaround: If you need to specify a MAC address to io-net, we recommend that you use the same MAC address that the ROM monitor uses. This will ensure that if the host caches the ROM monitor's MAC address, you'll still be able to communicate with the target. Otherwise you might need to delete the target's arp entry on your host.
Simply uncommenting the io-graphics line in the buildfile isn't enough to run Photon on the target; this line shows how to run the graphics driver only. For more information on embedding Photon on your board, see the Photon in Embedded Systems appendix of the Photon Programmer's Guide.
To test or evaluate Photon on your target before embedding it you could make the Photon environment accessible to the target by simply mounting your host environment into the target. You'll need to use an NFS or CIFS client on the target depending on the type of server running on your host platform. This example shows how to create a basic Photon configuration using an NFS client.
1. Uncomment the following sections from the build file: network, usb and graphics
2. Add the following at the end of the network section:
```
      fs-nfs3 10.0.0.1:$QNX_TARGET/cpu/ /
              10.0.0.1:$QNX_TARGET/etc /etc
              10.0.0.1:$QNX_TARGET/usr/photon /usr/photon &
      waitfor /usr/bin
      waitfor /usr/photon
      waitfor /etc

      Where 10.0.0.1 is the server IP address
    
```
  The first three lines of the fs-nfs command comprise one command.
3. You can now run the Photon drivers.
  To run the graphics driver:
```
      /usr/photon/bin/Photon &
      waitfor /dev/photon
      /usr/photon/bin/io-graphics -d...
     
```
  (See the "Devices supported" chapter in the BSP documentation for details on the graphics driver options).
  To use a usb mouse and keyboard:
```
      /sbin/io-hid -dusb
      /usr/photon/bin/devi-hid kbd mouse &
   
```
If you specify the -d and -p options for io-graphics, you must put the -d option before the -p, or else io-graphics fails. (Ref# 22670)
The ROM monitor version (UBoot) that comes with the board initializes the CPU frequency to 96MHz, but it should be 192MHz. To avoid timing issues, be sure to get the latest version of the UBoot ROM Monitor. (Ref# 22446)
The IPL sets the frequency to 192MHz.
Pressing the reset button will not reset the board properly. This is a bug in the ROM monitor. (Ref# 22447)
Workaround: Use the IPL instead, or power down the board then power up again.
The TCP/IP stack obtains a timer from the process manager. This timer starts at 0. If the TCP/IP stack and a TCP/IP application that tries to connect to a remote host start executing too soon, the TCP/IP stack may apply a time of 0 seconds to ARP cache entry structures. If this occurs, you may end up with a permanent ARP entry (i.e. one that never times out). You can also end up with permanent, incomplete ARP entries that never time out, and that the TCP/IP stack doesn't attempt to resolve. If this happens, your host won't be able to communicate with one or (possibly) more remote hosts (i.e. the ones the TCP/IP application in the OS image is trying to reach).
You can check for permanent ARP entries by running the arp -an command and examining the output. The only permanent entries listed should be for the IP addresses assigned to your host's interfaces; there shouldn't be any permanent, incomplete entries. If you find a permanent entry that isn't for the IP address of an interface on your host, and you didn't explicitly create a permanent entry, then you could be encountering this problem. (Ref# 21395)
Workaround: In the buildfile for your OS image, delay the start of the TCP/IP stack or the first TCP/IP application by at least one second, by using the sleep command (e.g. sleep 1) or some other delay mechanism.

Please check the version of these release notes on the website for the most up-to-date information.

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 QNX Momentics guide or visit our website, www.qnx.com.