QNX Technical Articles
QNX® Momentics® 6.3.0 IBM PPC405 BSP 1.0.0 Release Notes
Date of this edition: March 31, 2005
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)
Boards supported: IBM 405GP, IBM NPe405H, IBM 405EP, IBM 405GPr
|
Contents
- 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
- Serial driver
- Network driver
- PCI server.
Source code
- IPL
- Startup
- Serial driver
- Network driver
- PCI server.
Documentation
- IBM PPC405 BSP guide (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. 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 |
|
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
- The IPL supports only the IBM PPC405GP (Walnut) board.
- On the IBM NPe405H, you must specify the following IRQ settings when
plugging any PCI card into the board:
- PCI Slot0: IRQ 27
- PCI Slot1: IRQ 26
- PCI Slot2: IRQ 25
- PCI Slot3: IRQ 24
where PCI Slot3 is the nearest slot to the power connector on the NPe405H. For example, if you insert a 3Com el900 Ethernet card into PCI slot0, you need to start the network driver like this:
io-net -del900 irq=27 -ptcpip
- 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.
- To build the BSP from the command line, you need to extract the source code from the zip file. In Microsoft Windows, make sure you place the source code in a directory that doesn't contain any spaces in its name.
- 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.
- 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.
- When you install several BSPs that share common files, you'll be prompted to overwrite the existing files. We recommend that you backup the existing files before you overwrite them. Uninstalling any BSP that shares that file will currently remove the common file. You'll need to restore the backup after you uninstall any BSP that shared the file(s). (Ref# 22922)
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.