Project Home
Project Home
Project Information
Project Info
wiki4067: Nto640TiOmapL137EvmTrunkReleasenotes (Version 5)

Release Notes for the QNX Neutrino 6.4.0 BSP for TI OMAP-L137 EVM#

1.System Requirements#

Target Requirements
  1. QNX Neutrino RTOS 6.4.0
  2. Board version: TI OMAP-L137 EVM
  3. L137 processor
  5. 4 MB SPI flash

Host Requirements

  1. QNX Momentics 6.4.0
  2. Terminal emulation program (Qtalk, Momentics IDE Terminal, tip, HyperTerminal, etc.)
  3. RS-232 serial port and serial cable, or a USB-to-serial cable
  4. Ethernet link

2.Getting Started#

2.1 Building the BSP#

You can build a BSP OS image from the source code or the binary components contained in a BSP package. For instructions about building a BSP OS image, please refer to the chapter Working with a BSP in the Building Embedded Systems manual.

2.2 Connect your Hardware#

Connect the serial cable to the serial port of the OMAP L137 EVM board to the first serial port of your host machine. There is 1 serial port on OMAP L137 EVM board. Use the one which is near the boundary of the board. Usually you should see some Uboot output on the console when you connect cable to the correct port. If you have a Neutrino host with a serial mouse, you may have to move the mouse to the second serial port on your host, because some terminal programs require the first serial port.

The correct terminal settings of the program handling serial connection should be:

baudrate 115200
data 8 bit
parity none
stop 1bit
flow control none

2.3 Setup you environment#

1. Power on your target. You should see the u-boot output on your console. 2. Conenct an ethernet cable to any of the 2 PHY port available on the back side of the board.

3. Boot the IFS image#

You can use TFTP download (the default) or serial download to transfer an OS image to the board, as described below.

3.1 Boot via tftp#

This method requires that you put the raw image generated by BSP (by default at $BSP_ROOT/images/ifs-omapl137.raw) to a TFTP server. This server must be reachable via board and preferably should be on the same LAN. As soon as u-boot starts, press any key so that u-boot stops and doesnt boot the prebuild linux kernel. Configure u-boot parameters as follows:

=> setenv ipaddr
=> setenv serverip
=> setenv bootfile ifs-omapl137.raw
=> setenv loadaddr 0xC0008000
=> setenv bootcmd 'tftpboot $loadaddr $bootfile; go $loadaddr'
=> setenv bootdelay 2
=> saveenv
Saving Environment to SPI Flash...
Erasing SPI flash...Writing to SPI flash...done
=> boot

At this point, you should see output similar to this when it finishes downloading:

## Starting application at 0xC0008000 ...
Welcome to QNX Neutrino on a TI OMAP L137 Platform

Congratulations! QNX 6.4.0 kernel is running on your system. You can test the OS simply by executing any shell builtin command or any command residing within the OS image (e.g. ls). Once the initial image is running, you can update the OS image using the network and flash drivers. Still the network and flash drivers need to be supported for the TI OMAP L137 EVM board.

4. Driver Command Summary#

Component Buildfile Command Required Binaries Required Libraries Source Location
Startup startup-p2020rdb -v -c0xFFE00000 -t50000000 -D0xffe04500 startup-p2020rdb libstartup.a src/hardware/startup/boards/p2020rdb
Serial devc-ser8250 -e -c600000000 -b115200 0xffe04500,25
waitfor /dev/ser1
reopen /dev/ser1
devc-ser8250 none src/hardware/devc
I2C i2c-dm6446 -a0x1 -i15 -p0x01c22000 -f24000000 -l0x1000 --b10000 --u0 (for controller 1)
i2c-dm6446 -a0x2 -i51 -p0x01e28000 -f24000000 -l0x1000 --b10000 --u1 (for controller 2)
i2c-dm6446 libi2c-master.a src/hardware/i2c/dm6446
Network io-pkt-v4-hc -dmpcsec -p tcpip-v6 ipsec -dmpc85xx mac=00112233AABB,emu_phy=0 io-pkt-v4-hc
ifconfig /src/hardware/devnp
SPI spi-master -d dm644x base=0x01c41000,irq=20,clock=150000000,edma=0,en0def=1,spicntrlr=omapl13x spi-master /src/hardware/spi/dm644x


To start network driver without encryption, run:

io-pkt-v4-hc -dmpcsec -p tcpip-v6 ipsec -dmpc85xx mac=00112233AABB,emu_phy=0

you should see following output when you run ifconfig

# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet netmask 0xff000000
tsec0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        capabilities tx=0
        address: 00:11:22:33:aa:bb
        media: Ethernet none
tsec1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        capabilities tx=0
        address: 00:11:22:33:aa:bc
        media: Ethernet none
tsec2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        capabilities tx=0
        address: 00:11:22:33:aa:bd
        media: Ethernet none

To bring a network interface up, type following command

ifconfig tsec0 up

Here is the IP address assign to your target and 24 is the netmask bits (i.e. The LEDs of the RJ45 ports corresponding to an enabled interface shall glow periodically. This can be used to identify the correct port corresponding to each tsec.

5. Known Issues for This BSP#