Home
Developer Resources
Technical Articles

QNX Technical Articles

QNX® Momentics® 6.3.2 Renesas Lanbic BSP 1.1.0

QNX® Momentics® 6.3.2 Renesas Lanbic BSP 1.1.0 Release Notes

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

Note:
  • For information on installing this BSP, see the installation note.
  • You should also install the QNX Momentics Character Driver Development Kit (DDK) version 6.3.0 SP1, if you have 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

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
  • Serial driver
  • Network driver (included with the OS)
  • USB (included with the OS)
  • ATAPI
  • Graphics
  • Audio drivers (AC97 and I2S)
  • i2c driver
  • SPI driver

Source code

  • IPL
  • Startup
  • Serial driver
  • Network driver
  • Flash driver
  • Graphics
  • Audio drivers (AC97 and I2S)
  • i2c driver
  • SPI driver

Documentation

  • Renesas Lanbic 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.).

Known issues for this BSP


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

  • This BSP contains a driver, devc-sersci, which will overwrite the version included in other SH4 BSPs. You should back this version up before installing (Ref# 22922).
  • 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.

  • Simply uncommenting the io-graphics line in the buildfile isn't enough to run Photon on the target; this line shows how to run the graphics driver only. For more information on embedding Photon on your board, see the Photon in Embedded Systems appendix of the Photon Programmer's Guide.

    To test or evaluate Photon on your target before embedding it you could make the Photon environment accessible to the target by simply mounting your host environment into the target. You'll need to use an NFS or CIFS client on the target depending on the type of server running on your host platform. This example shows how to create a basic Photon configuration using an NFS client.

    1. Uncomment the following sections from the build file: network, usb and graphics
    2. Add the following at the end of the network section:
           fs-nfs3 10.0.0.1:$QNX_TARGET/cpu/ /
                   10.0.0.1:$QNX_TARGET/etc /etc
                   10.0.0.1:$QNX_TARGET/usr/photon /usr/photon &
           waitfor /usr/bin
           waitfor /usr/photon
           waitfor /etc
      
           Where 10.0.0.1 is the server IP address
         

      Note: The first three lines of the fs-nfs command comprise one command.

    3. You can now run the Photon drivers.

      To run the graphics driver:

            /usr/photon/bin/Photon &
            waitfor /dev/photon
            /usr/photon/bin/io-graphics -d...
           
      (See the "Devices supported" chapter in the BSP documentation for details on the graphics driver options).

      If your board doesn't have a specific Input driver (See the "Devices supported" chapter in the BSP documentation for details) but it has USB support, to use a USB mouse and keyboard you could run:

            /sbin/io-hid -dusb
            /usr/photon/bin/devi-hid kbd mouse &
         
      Otherwise run the Input driver as described in the BSP documentation.

  • If you specify the -d and -p options for io-graphics, you must put the -d option before the -p, or else io-graphics fails. (Ref# 22670)
  • 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)

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.