wiki4067: Nto640TiOmapL137EvmTrunkReleasenotes (Version 8) | ||||||||||||||||||||||||||||||||||||||||
Release Notes for the QNX Neutrino 6.4.0 BSP for TI OMAP-L137 EVM#1.System Requirements#Target Requirements
Host Requirements
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:
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 10.90.74.214 => setenv serverip 10.90.74.42 => 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#
Serial#To start the Serial driver, run the following command: devc-ser8250 -e -F -S -b115200 -c150000000/16 0x01d0d000^2,61 Network#To start network driver, run: io-pkt-v4 -ddm644x-l1xx phy=2 -ptcpip Note : Here the phy=2 indicates which ethernet port on the OMAPL137 board you are connecting to, the ethernet port next to the serial interface on the board corresponds to phy = 2, and the next to that one corresponds to phy = 1. you should see following output when you run ifconfig # ifconfig en0 en0: flags=80008802<BROADCAST,SIMPLEX,MULTICAST,SHIM> mtu 1500 address: 00:0e:99:02:f9:4e media: Ethernet 100baseTX status: active To bring the network interface up, type following command ifconfig en0 10.90.74.246/24 up Here 10.90.74.246 is the IP address assigned to your target and 24 is the netmask bits (i.e. 255.255.255.0) The LEDs of the RJ45 port corresponding to the enabled interface shall glow periodically. This can be used to identify the correct port, port 1 (phy 1) or port 2 (phy 2). SPI#To start spi driver for spi0 interface, run: spi-master -d dm644x base=0x01c41000,irq=20,clock=150000000,edma=0,en0def=1,spicntrlr=omapl13x you can see a file /dev/spi0 after the above step. To start spi driver for spi1 interface, run: spi-master -u1 -d dm644x base=0x01E12000,irq=56,clock=150000000,edma=0,en0def=1,spicntrlr=omapl13x you can see a file /dev/spi1 after the above step. For reading the on-board spi-flash you need to use /dev/spi0. 5. Known Issues for This BSP# |
||||||||||||||||||||||||||||||||||||||||