QNX Technical Articles
QNX® Momentics® 6.3.2 Freescale CDS MPC85xx BSP 1.0.0 Release Notes
Date of this edition: September 05, 2007
Target OS: This BSP is compatible with targets that are running QNX® Neutrino® 6.3.2.
Host OS: In order to install this BSP, you must have installed QNX Momentics 6.3.2 on one of the following hosts:
- Microsoft Windows Vista, XP SP2, or 2000 SP4
- QNX® Neutrino® 6.3.2
- Linux Red Hat Enterprise Workstation 4 or 5, Red Hat Fedora Core 6 or 7, Ubuntu 6.0.6 LTS or 7.0.4, or SUSE 10
Boards supported: Freescale CDS MPC8555
 |
|
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
Binary components
- Startup
- PCI server
- Serial driver
- Network driver
Source code
- Startup
- PCI server
- Serial driver
- Network driver
- Flash driver
Documentation
- Freescale CDS MPC85xx Board Support Package readme (HTML)
|
Each BSP guide contains board-specific information and instructions on building an OS image for that particular board. |
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 and 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
- When you import this BSP into the IDE, the mpc8540.be variant of the serial driver is
renamed by the IDE to o.be. This causes the IDE to only
build devc-ser8250 instead of devc-ser8250-mpc8540.
The buildfile will not build because it looks for devc-ser8250-mpc8540.
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-freescale-cdsmpc85xx_devc-ser8250 serial driver by clicking on the + sign. Then, expand ser8250, then ppc. Rename the o.be variant to mpc8540.be by right-clicking on it and selecting Rename. Rebuild the entire project to compile devc-ser8250-mpc8540 and to rebuild the OS image.
- Unplugging the network cable results in an "Unknown" media speed on reinsertion. The driver is still fully functional in this state. (Ref# 21992)
- 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.
|
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.