QNX Technical Articles

Date of this edition: September 06, 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 PQ2FADS ZU and VR (8270, 8272, 8280)

---

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, go to our website (www.qnx.com), log into your myQNX account, and then go to the Download area.

---

Contents

• What's in this BSP?
  • Binary components
  • Source code
  • Documentation
• 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

• IPL
• Startup
• PCI server
• Serial driver
• Network driver

Source code

• IPL
• Startup
• PCI server
• Serial driver
• Network driver
• Flash driver

Documentation

• Freescale PQ2FADS 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

QNX Neutrino, Linux, and Solaris hosts

Known issues for this BSP

---

If you've developed a custom BSP based on MPC 82xx processors (i.e. 8260, 8266, 8270, 8280, 8272) you'll need to add the following two functions in init_hwinfo.c: hwi_add_device(HWI_ITEM_BUS_UNKNOWN, HWI_ITEM_DEVCLASS_SERIAL, "PQ2FADS", 0); hwi_add_inputclk(ppc8260_brgclk, 16); This will put the BRG clock into the system page. The Serial driver will look for the tag "PQ2FADS" and grab the correct BRG clock. All MPC82xx-based BSPs, released post 6.3.0 by QSS, are already modified as described above.

---

• 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.

• Some PCI cards may not work at a 66 MHz PCI clock frequency. Drivers may crash as a result. (Ref# 22964)

  Workaround: Refer to the board documentation to change the PCI clock frequency to 33 MHz.

• The mkefs command for Windows doesn't handle redirection properly. (Ref# 19065)

  Workaround: In the images/make_flash_img directory, change the following code:

  mkefs ../src/hardware/ipl/boards/pq2fads/pq2fads.efs
  ipl-ifs-efs-pq2fads.bin

  to:

  mkefs ../src/hardware/ipl/boards/pq2fads/pq2fads.efs efs-pq2fads
  cat efs-pq2fads >> ipl-ifs-efs-pq2fads.bin
  rm -f efs-pq2fads

• In order to build the IPL for the MPC8272ADS board, you have to pass "make MPU=8272" on the command line.
• The settings described in the documentation for the MPC8272ADS are too aggressive for the PCI chipset. Therefore the PCI server may not work properly, depending on the PCI card that you use. However these settings are fine for the onboard Ethernet controller.

  Workaround: In order to get the PCI chipset and the onboard Ethernet controller to function at the same time, you need to lower the CPM clock by using the following settings:

  Switch	Setting
  SW2, 1	0 (ON) position to boot from the flash SIMM
  SW5, MODCKH0 - MODCKH3	(OFF/OFF/ON/OFF) position
  SW5, MODCK1 - MODCK3	(ON/ON/ON) position

---

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.