QNX® Momentics® 6.3.0 SP2 TI Jacinto BSP 1.0.0 Release Notes

Date of this edition: May 06, 2008

Target OS: This BSP is compatible with targets that are running QNX^® Neutrino^® 6.3.0 SP2 or later

Host OS: In order to install this BSP, you must have installed QNX Momentics 6.3.0 SP2 or later on one of the following hosts:

• Microsoft Windows XP SP1 or SP2, 2000 SP4, or NT SP6a
• Sun Solaris 7, 8, or 9
• QNX^® Neutrino^® 6.3.0 or 6.3.0 SP1
• Linux Red Hat 8, 9, or Enterprise WS 3 or 4

Boards supported: TI Jacinto EVM

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

• Serial driver: devc-ser8250
• USB driver: devu-jacinto.so
• EIDE Block driver: devb-eide-dm644x
• SD block driver: devb-sd-jacinto
• CAN control ultility: canctl
• ETFS control ultility: etfsctl
• Graphic library: libdisputilS.a, libdsplink14005-clientS.a
• CAN library: libio-can.a
• I2C master library: libi2c-master.a

Source code

• IPL
• Startup
• ETFS driver
• SPI driver
• I2C driver
• CAN driver
• Audio driver
• Network driver
• Graphics driver

Documentation

• TI Jacinto 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

• If you use the SPI with DMA enabled, the ADE (and hence the MME) locks up. This conflict occurs because the prebuilt DSP/BIOS and ADE image from TI was compiled to use EDMA channel 1. (Ref# 54350)

  Workaround: When you start spi-master, don't specify the edma option.

  If you have acquired the ADE code from TI, you might be able to to resolve the conflict by modifying the EDMA channel numbers on both the DSP and ARM systems.

• Only one headphone output (p8 on the board) is currently supported.
• The graphics driver requires both the QNX Advanced Graphics TDK 2.0.1 and a TI DSP image with the TES eVRU v2.03, configured for 120/8MB. You should obtain them separately from this package.
• You need to get the DSPLink package separately from this package.
• EMIF is not implemented in U-boot. This may cause the graphics to not work properly. You should use IPL booting for graphics.
• The spi-dm644x.so shared object doesn't support the SPIENA pin. The current driver supports only the first two chip selects.
• We haven't tested the ETFS driver because of a lack of flash devices.
• If you use gcc 2.95.3 to compile this BSP, you'll see this warning, which you can ignore:

  /bsp-TI-Jacinto-1.0.0-20071115-binsrc/src/hardware/devg/jacinto/mode.c:62: warning: passing arg 1 of `disp_phys_addr' discards qualifiers from pointer target type

• If you use gcc 3.3.5, you'll see these warnings, which you can ignore:
  • /bsp-TI-Jacinto-1.0.0-20071115-binsrc/src/hardware/can/jacinto/driver.c:162: warning: comparison is always false due to limited range of data type
  • /bsp-TI-Jacinto-1.0.0-20071115-binsrc/src/hardware/devg/jacinto/mode.c:62: warning: passing arg 1 of `disp_phys_addr' discards qualifiers from pointer target type
• SPI0 is inoperable because the dra446.h header file uses the incorrect base address for SPI0. (Ref# 52270)

  Workaround: Edit dra446.h and change this line:

  #define        DRA446_SPI0_BASE                0x01C41800
    

  to this:

  #define        DRA446_SPI0_BASE                0x01C4CC00
    

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

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.