Developer Resources: Board support packages; Foundry27 projects; Forums

QNX Technical Articles

QNX® Momentics® 6.3.0 Intel IXDP425 BSP 1.0.1 Release Notes

QNX® Momentics® 6.3.0

Date of this edition: July 04, 2008

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
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
PCI server
Serial driver
Network drivers (devn-ixdp425.so in BSP; devn-speedo.so included with OS).

Source code

IPL
Startup
PCI server
Serial driver
Network drivers
Flash.

Documentation

Intel IXDP425 BSP guide (HTML)

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

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. 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 in $QNX_TARGET\usr\src\archives\qnx\ on Windows, and in $QNX_TARGET/usr/src/archives/qnx/ on QNX Neutrino and Linux.

You can read the documentation (including release notes) in the Integrated Development Environment's help system on all host OSs; on self-hosted QNX Neutrino systems, you can also read it in the Photon helpviewer, or you can use a web browser to display:

${QNX_TARGET}/usr/help/product/momentics/bookset.html

This “roadmap” page contains links to the various HTML booksets that accompany the OS (e.g. System Architecture, QNX Neutrino 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`
“`sbin`” drivers (serial, flash, block, PCI, PCMCIA, USB)	`$QNX_TARGET\cpu\sbin`
“`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`

Known issues for this BSP

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

On some boards, the Redboot go command might not successfully start the Neutrino image. (Ref# 44156)
Workaround: Use the exec command instead.
When you import this BSP into the IDE, the ixp2400.be variant is renamed by the IDE to o.be. This causes the IDE to only build devc-ser8250 instead of devc-ser8250-ixdp2400. The buildfile will not build because it looks for devc-ser8250-ixdp2400. This issue doesn't occur when you build the BSP from the command line.
Workaround: Once you've imported the BSP into the IDE, click on the C/C++ Projects tab to display the list of drivers. Expand the bsp-intel-ixdpxxxx_devc-ser8250 serial driver by clicking on the + sign. Then, expand “ser8250”, then “arm”. Rename the o.be variant to ixp2400.be by right-clicking on it and selecting “Rename”. Rebuild the entire project to compile devc-ser8250-ixdp2400 and to rebuild the OS image.
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.

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.