QNX Technical Articles
QNX® Momentics® 6.3.0 Intel IXDP2800 BSP 1.0.0 Release Notes
Date of this edition: December 01, 2004
Target OS: QNX® Neutrino® 6.3.0
Host OS: Microsoft Windows XP SP1 or SP2; Microsoft Windows 2000 SP4; Linux (Red Hat 8/9)
Boards supported: Intel IXDP2800 revision B1
| NOTE: |
|
Contents
- What's in this BSP?
- Location of source and documentation
- Known issues for this BSP
- Technical support
| NOTE: | 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.
| NOTE: | The source code requires a BSP Source License. |
Binary components
- Startup
- PCI server
- Serial driver
- Network driver (included with OS).
Source code
- Startup
- PCI server
- Serial driver
- Network driver.
Documentation
- Intel IXDP2800 BSP readme (HTML)
| NOTE: | 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 and documentation in the following locations:
Windows hosts
| Component | Location |
|---|---|
| Source code | $QNX_TARGET\usr\src\archives\qnx\ixdp2800.zip |
| Documentation | $QNX_TARGET\usr\help\product\bsp_intel_ixdp2800 |
| Release notes | $QNX_TARGET\etc\readme\bsp |
Linux hosts
| Component | Location |
|---|---|
| Source code | $QNX_TARGET/usr/src/archives/qnx/ixdp2800.zip |
| Documentation | $QNX_TARGET/usr/help/product/bsp_intel_ixdp2800 |
| Release notes | $QNX_TARGET/etc/readme/bsp |
| NOTE: |
|
Binaries, buildfiles, IPLs, and other files
You'll find these files in these locations:
Windows hosts
| File | Location |
|---|---|
| Buildfile | $QNX_TARGET\armbe\boot\build |
| IPL and/or startup | $QNX_TARGET\armbe\boot\sys |
| "bin" drivers (serial, flash, block, PCI, PCMCIA, USB) | $QNX_TARGET\armbe\bin |
| "dll" drivers (audio, graphics, network) | $QNX_TARGET\armbe\lib\dll |
Linux 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
| NOTE: | Please check the version of these release notes on the website for the most up-to-date information. |
- The ROM Monitor assigns special meaning to files that end with .bin. It seems to ignore the address specified on the command line, so the image isn't bootable. To work around this problem, the boot image file generated by this BSP ends in -bin, instead of the usual .bin.
- The Egress and Ingress processors must both be up and running QNX Neutrino before you start the PCI server on one processor. Otherwise, the ROM monitor will lock up on the other one.
- When connecting the network driver to a switch, make sure to let the driver autonegotiate the speed and duplex. If forced, the driver might not work with the switch; it works with a hub. (Ref# 21982)
- The following warning is generated when you compile the PCI server:
hardware/pci/ixp2400/ixp2400.c: In function `ixp2400_read_cnfg': hardware/pci/ixp2400/ixp2400.c:365: warning: variable `addrp' might be clobbered by `longjmp' or `vfork'
The warning is benign, since the signal handler that could cause the problem isn't installed. (Ref# 22215)
- If you install the source code for a BSP on a Windows platform
(Windows 2000 or XP), and you don't install it on the C
drive, then the BSP will fail to build using the command-line instructions
given in the Working with a BSP chapter of
Building Embedded Systems.
The tools can't find the ixdp2800.build file.
(Ref# 21924)
If you install the BSP on the C drive, building the BSP from the command line succeeds. Building a BSP in the IDE works no matter where you install the BSP.
Workaround: Do one of the following:
- Before building the BSP, do the following:
- Start a bash shell.
- Go to the directory that holds the BSP source ($QNX_TARGET/usr/src/archives/qnx/BSP_name)
- Enter the following command:
cp install\armbe\boot\build\ixdp2800.build images\ixdp2800.buildThis command copies the ixdp2800.build file into the correct directory, and lets you build the BSP, as described in the documentation.
- If you've tried to build the BSP, and the build fails, do the following
to recover and generate the BSP OS image:
- Start a bash shell.
- Go to the directory that holds the BSP source ($QNX_TARGET/usr/src/archives/qnx/BSP_name).
- Enter the following command:
cp install\armbe\boot\build\ixdp2800.build images\ixdp2800.buildThis copies the ixdp2800.build file into the correct directory.
- Enter the following commands to build the BSP image:
cd images make
- Before building the BSP, do the following:
- 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.
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.