OMAP35x Wireless Connectivity Getting Started Guide

How to start working with the EVM - Step by Step

The following guidelines assume that you already have some experience working with the OMAP 35x EVM. First time EVM users should refer to the EVM Getting started Guide

To get started with the WLAN/BT daughter card, follow 4 simple steps:

Step 1. Build environment guide (How to compile the package)

Step 2. Loading the images

Step 3. Performing WLAN RF Calibration

Step 4. HW setting

Step 5. Tools (terminal emulator, TFTP server and client)

Step 6. WLAN and BT drivers installation

Step 7. Basic connection to WLAN AP

Step 8. Setting the WLAN MAC address

Step 9. Experience Demo of some WLAN and Blutooth scenarios

Build environment guide

• for beta release instructions please use the following <Build enviroment guide of beta release>
• for beta 2 release instructions please use the following <Build enviroment guide of beta 2 release>
• for GA release instructions please use the following <Build enviroment guide of GA release>

Loading the images

• Connect the EVM to a PC via ethernet cable, set the the IP address of the PC and the EVM in the same subnet, for example set the PC address to 192.168.1.100 and EVM ethernet IP address to 192.168.1.10
  

• After plugging the OMAP35x EVM to the power supply, connecting the serial cable to UART1/2, configuring your terminal to listen on the connected serial port, and swithing on SW2 of the EVM, hit any key to stop in the U-BOOT menu. You will see the following:

Texas Instruments X-Loader 1.42
Starting OS Bootloader...
No OOB scheme defined for oobsize 0
OneNAND:  0 kB
256 MiB

U-Boot 2008.10 (Sep 14 2009 - 13:40:58)

OMAP35X-Family-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 EVM board + LPDDR/NAND
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot: 15 
OMAP3_EVM # 
OMAP3_EVM # 

This section assumes knowledge on how to use the TFTP tool, if not then please first refer to section <Tools (terminal emulator, TFTP server and client)> and <WLAN and BT drivers installation>
The TFTP server export folder should have the following necessary binaries copied:

1. u-boot.bin – U-boot image from PSP release
2. uImage – Linux kernel image, from WL1271 package.
3. rootfs.jffs2 – Root file system from PSP release.
4. vXX.XX.XX.XX-WLx.x.x.x.tar.bz2 – WLAN and Bluetooth binaries from WL1271 package.
   

Comment: In the below example vXX.XX.XX.XX-WLx.x.x.x.tar.bz2 is v2.01.03.11-WL6.1.3.1.tar.bz2 to reflect the beta release however that name is changed between releases, for example for beta 3 it will be v3.00.01.06-WL6.1.6.0.3

Loding the u-boot.bin & rootfs.jffs2

Download PSP-SDK package from the below locations and install it to a host PC where TFTP server is running.
Copy pre-built binaries of U-boot (u-boot.bin) and root file system (rootfs.jffs2) from PSP-SDK.

version 02.01.03.11

The download location of the PSP package is PSP_02.01.03.11

version 03.00.01.06

The download location of the PSP package is PSP_03.00.01.06

Setting up Ethernet Address of the EVM

Perform the following commands at the u-boot prompt;

setenv ipaddr 192.168.1.10 
setenv serverip 192.168.1.100

Flashing the U-boot

Perform the following commands at the u-boot prompt;

mw.b 0x80000000 0xFF 0x100000
tftp 0x80000000 u-boot.bin
nand erase 0x80000 0x1C0000
nandecc sw
nand write.i 0x80000000 0x80000 0x1C0000

Flashing the Kernel Image

Perform the following commands at the u-boot prompt;

mw.b 0x81600000 0xff 0x300000
nand erase 280000 300000
nand erase clean 280000 300000
tftpboot 0x81600000 uImage
nandecc sw
nand write.i 0x81600000 280000 300000

Flashing the rootfs File Sytem

Perform the following commands at the u-boot prompt;

mw.b 0x81600000 0xff 0x6050000
nand erase 780000 f870000
nand erase clean 780000 f870000
tftpboot 0x81600000 rootfs.jffs2
nandecc sw
nand write.i 0x81600000 780000 6050000

Setting up U-boot parameters

Perform the following commands at the u-boot prompt;

setenv bootcmd 'nand read.i 0x80000000 280000 300000; bootm 0x80000000'
setenv bootargs 'mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw
rootfstype=jffs2'
sa
re (Restart the board)

Wait until the kernel completes booting up. At the end, the kernel logo appears, and you will be requested to login. At the login command write "root":

Arago 2009.09 omap3evm ttyS0

omap3evm login: JFFS2 notice: (514) check_node_data: wrong data CRC in data node
 at 0x05c45fbc: read 0x1c628876, calculated 0xd2a597f7.

 _____                    _____           _         _   
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_ 
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|  
              |___|                    |___|            

Arago Project http://arago-project.org omap3evm ttyS0

Arago 2009.09 omap3evm ttyS0

omap3evm login: root
root@omap3evm:~#

Loading the WLAN and the Bluetooth images

• Verify that the EVM ethernet port is configured to the correct IP address, use the command "ifconfig" to check the ethernet port configuration.

 
root@omap3evm:~/demo# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:C2:7E:8D:D9  
          inet addr:10.1.101.199  Bcast:10.1.101.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1581 (1.5 KiB)  TX bytes:0 (0.0 B)
          Interrupt:80 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

• If needed configure the EVM Ethernet port to the correct IP address by using the "ifconfig" command.

root@omap3evm:~/demo# ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up

• Open the TFTP utility in the PC and download the image and install it to EVM by using the

following commands;

root@omap3evm:~# mkdir demo
root@omap3evm:~# cd demo
root@omap3evm:~/demo# tftp -g -r v2.01.03.11-WL6.1.3.1.tar.bz2 192.168.1.100

• The imange name can be vary upon image release version.

• After loading the image, verify that it exsist in the directory (use "ls" command) and then uncompress the tar file using these comands.

root@omap3evm:~/demo# ls
v2.01.03.11-WL6.1.3.1.tar.bz2
root@omap3evm:~/demo# tar -jxvf v2.01.03.11-WL6.1.3.1.tar.bz2 

• The folder will include all images and scripts, and looks like the following:

root@omap3evm:~/demo# ls
BT_FTP_storage                 install.sh
BT_firmware                    iptables-1.4.3.2
Readme.txt                     tools
bluetooth                      v2.01.03.11-WL6.1.3.1.tar.bz2
bluetooth_scripts              wlan
gallery                        wlan_scripts

• Next install the drivers by going to the main folder (in this example "demo") and run the install.sh script:

root@omap3evm:~/demo/gallery# cd ..
root@omap3evm:~/demo# ls
BT_FTP_storage                 install.sh
BT_firmware                    iptables-1.4.3.2
Readme.txt                     tools
bluetooth                      v2.01.03.11-WL6.1.3.1.tar.bz2
bluetooth_scripts              wlan
gallery                        wlan_scripts

root@omap3evm:~/demo# ./install.sh 

This script installs TI-MISTRAL's WL1271 (WLAN and Bluetooth) packages on OMAP35
30 EVM
.
..
...
....
/home/root/demo/bluetooth          --> Bluetooth Binaries
/home/root/demo/wlan               --> WLAN Binaries
/home/root/demo/bluetooth_scripts  --> Bluetooth Scripts
/home/root/demo/wlan_scripts       --> WLAN Scripts
/home/root/demo/iptables-1.4.3.2   --> Iptable Utilities
/home/root/demo/iptables-1.4.3.2/WebBrowse.sh
/home/root/demo/BT_FTP_storage    --> BT FTP Storage files
/home/root/demo/tools             --> Wlan Tools (iperf, etc ...)
/home/root/demo/gallery           --> Gallery files
WL1271- Package installation completed
Please reboot the board before starting WLAN and BT

root@omap3evm:~/demo# 

• After performing the RF calibration process listed at the below section

and confirming the EVM is working properly. It's recomended to remove the zipped version image file from the EVM
using the following Linux command:

root@omap3evm:~/demo #rm v2.01.03.11-WL6.1.3.1.tar.bz2

return to main menu

Installing Linux Kernel Modules

Execute the following commands on the EVM to download the new kernel modules;

root@omap3evm:~# cd /

root@omap3evm:/# tftp -g -r libmodules.tar.gz <IP address of the tftp server>

root@omap3evm:/# ls

root@omap3evm:/# tar -xf libmodules.tar.gz

Performing WLAN RF Calibration

the first time were the EVM35xx and the WL1271 daughterboard is being used, the TX Bit procedure have to be done, it will create an nvs_map.bin file that containes the specifc WL1271 daughterboard calibration parameters.
follow the steps to perform the Tx BIP procedure:
1. in case there is no Antenna connect a 50 Ohm termination on the RF connector.
2. Download the WLAN driver and bring up the CLI
3 .Wake up the device by typing the folowing command in the CLI

/ w p 1 l 2 f 2 

4. Run the following TX BIP commands:

/ t r h 0 7 
/ t b b 375 128 0 
/ t b t 1 0 0 0 0 0 0 0

5. reset the Board after NVS FILE generation is completed.


return to main menu

HW setting

This WL1271 daughter card Setup Guide is used to quickly verify jumper settings and to ensure proper installation onto the OMAP35x EVM main board. For more details refer to the Getting Started Guide inside the WL6 SDK package contained in the DVSDK DVD 1.

Instructions on how to install WL1271 on the Main OMAP35xx EVM board

Verify jumper settings and LEDs

It is recommanded to place the EVM upside down in order to see the LEDs on the WL1271 daugther card

return to main menu

Tools (Terminal Emulator, TFTP server and client)

Tera Term

A serial port terminal program should be used to communicate with the OMAP35x EVM board’s serial port console. This tool is needed to run the WLAN and BT demos. TeraTerm is the recommended terminal emulator for Windows. It can be downloaded from the Tera Term web site

After running Tera Term use the Setup->Serial Port menu command to set up the following parameters:

Bits per second: 115200
Data bits: 8
Parity: None
Stop bits: 1
Flow control: none

It is also recommended to increase the Tera Term scroll buffer to 1000 lines using the Setup->Window menu command.

PumpKIN

PumpKIN is an open source free TFTP server and client. It is needed in order to download the WLAN/BT image into the EVM. It can be found at the following URL:pumpkin web site or direct download from load pumpkin-2.7.2.exe

Setup the TFTP Server

This section will describe setting up the TFTP server using a Windows host. You may also use a Linux TFTP server but that process is not described here.

To setup PumpKIN follow these steps: 1) Start the PumpKIN executable. The first time it is started it should show a Window. Subsequent Starts may only show in the system tray. You may open the window from the right click menu of the system tray icon.

return to main menu

WLAN and BT drivers installation

The following section describes how to load Bluetooth and WLAN images to the EVM. First, save the new BT and WLAN package on your local PC and use a TFTP application such as PumpKIN to download the images to the EVM. The procedure that follows describes how to download images using the PumpKIN TFTP application. To download images using the PumpKIN TFTP application:

1) Run the PumpKIN TFTP application.



2) Configure the TFTP directory for the BT and WLAN package folder location, as shown below:




3) Connect the Ethernet port of your EVM to the Ethernet port of your PC.
4) Connect a serial cable from your PC to Port 1 of the EVM.
5) Open a terminal application (Hyper Terminal, Tera-Term and so on).
6) Configure the IP address to your PC. For example, 192.168.1.100.
7) Configure the IP address to the EVM on the same subnet.

For example:
/ # ifconfig eth0 192.168.1.100 netmask 255.255.255.0

Run the following command from the Linux shell in order to get the package from your PC to the EVM:
tftp –g –r <name of the new package> <IP of your local PC>

For example:
/ # tftp -g -r BT-WLAN-Package.tar 192.168.1.100
Now, the package should be on your EVM.:

8) The package is compressed, so it must be extracted using the following command::
Tar –xvf <name of the new package>:

For example::
/ # tar -xvf BT-WLAN-Package.tar:
Now, you have the WLAN and BT files on your EVM.:


return to main menu

Basic connection to WLAN AP

Follow these steps to use the CLI in order to connect to a non secured WLAN AP

Step 1. WLAN driver bring up - type the folowing commands: cd /home/root/REV_D_WLAN1271/ ~/REV_D_WLAN1271 # insmod sdio.ko ~/REV_D_WLAN1271 # insmod bmtrace.ko ~/REV_D_WLAN1271 # insmod tiwlan_drv.ko ~/REV_D_WLAN1271 # ./tiwlan_loader ~/REV_D_WLAN1271 # ifconfig tiwlan0 10.1.100.56 netmask 255.255.255.0 up folowing there are some printouts on the scrin that ends with the following: CHIP VERSION... set 1273 chip top registers Working on a 1273 PG 2.0 board. Starting to process NVS... NVS found, EEPROM Image addr=0xc727c200, EEPROM Len=0x0x14c Chip ID is 0x4030111. FEM Type 1 Starting to download firmware... Starting to download firmware... Starting to download firmware... Starting to download firmware... Starting to download firmware... Finished downloading firmware. Firmware running. -------------------------------------------------------------------- -------------------------------------------------------------------- Driver Version  : WiLink_Driver_6.1.3.01.5 Driver Version  : WiLink_Driver_6.1.3.01.5 Firmware Version: Rev 6.1.3.01.5 Firmware Version: Rev 6.1.3.01.5 Station ID  : 08-00-28-12-44-66 Station ID  : 08-00-28-12-44-66 -------------------------------------------------------------------- -------------------------------------------------------------------- Step 2. Connect to non secured AP using CLI commands ~/REV_D_WLAN1271 #./wpa_supplicant -Dwext -itiwlan0 -c wpa_supplicant.txt & ~/REV_D_WLAN1271 # ./wlan_cu Connection established with supplicant user_main, start \> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit c .../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/ c N 31 Trying to associate with SSID 'N' OK ************ NEW CONNECTION ************ ************ NEW CONNECTION ************ -- SSID = N -- SSID = N -- BSSID = 0-23-5e-17-3e-d0 -- BSSID = 0-23-5e-17-3e-d0 **************************************** **************************************** Associated with 00:23:5e:17:3e:d0 CTRL-EVENT-CONNECTED - Connection to 00:23:5e:17:3e:d0 completed (auth) [id=30 id_str=] .../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/ Step 3. Prepare for transfer data over the WLAN media Exit the CLI application in order to start WLAN traffic / q / ~/REV_D_WLAN1271 # ~/REV_D_WLAN1271 # ~/REV_D_WLAN1271 # Step 4. Configure the EVM WLAN port ip address ifconfig tiwlan0 10.1.100.56 Verify EVM WLAN port ip address ifconfig / ~/REV_D_WLAN1271 # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:576 (576.0 B) TX bytes:576 (576.0 B) tiwlan0 Link encap:Ethernet HWaddr 08:00:28:12:44:66 inet addr:10.1.100.56 Bcast:10.1.100.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1230 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:72191 (70.4 KiB) TX bytes:0 (0.0 B) ~/REV_D_WLAN1271 # ~/REV_D_WLAN1271 # Step 5. Perform Ping test (send Ping to the AP address) ping -c4 10.1.100.3 / PING 10.1.100.3 (10.1.100.3): 56 data bytes 64 bytes from 10.1.100.3: seq=0 ttl=128 time=82.154 ms 64 bytes from 10.1.100.3: seq=1 ttl=128 time=22.065 ms 64 bytes from 10.1.100.3: seq=2 ttl=128 time=65.826 ms 64 bytes from 10.1.100.3: seq=3 ttl=128 time=109.986 ms Connect to non secured network

Setting the WLAN MAC address

The wireless MAC address is kept as part of the nvs.bin file which is created during the BIP procedure, however each EVM will have same default MAC address, which should be modified and be unique per EVM which share the same wireless network.
Following section describes how to modify the EVM wireless MAC address.

Hardware setup

Connect the EVM to the PC via ethernet cable configure the EVM and the PC to be in the same network, in that example configure the PC IP address is 192.168.1.100 and the EVM is 192.168.1.10 and verify the connection with ping command

wlan# ifconfig eth0 192.168.1.10
wlan# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:C2:7E:8D:2A
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1457 (1.4 KiB)  TX bytes:0 (0.0 B)
          Interrupt:80

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan# ping 192.168.1.100
PING 192.168.1.100 (192.168.1.100): 56 data bytes
64 bytes from 192.168.1.100: seq=0 ttl=128 time=0.702 ms
64 bytes from 192.168.1.100: seq=1 ttl=128 time=0.488 ms
64 bytes from 192.168.1.100: seq=2 ttl=128 time=0.824 ms

Step to modify the MAC address will be as follows:

1. Create the nvs_map.bin file (that only once)
2. Upload the nvs_map.bin file from the EVM to a PC via tftp protocol,
3. Edit the MAC address portion in the nvs_map.bin file
4. Return the modified nvs_map.bin file from the PC back to the EVM
5. Reboot the EVM and start working with new wirless MAC address

follow the steps below to modify the MAC address:
Upload the nvs file from the EVM to the PC

• Open the TFTP server on the PC
• type the folowing command in the EVM screen

tftp -p <IP address of PC> -l <file to load from EVM to PC>
tftp -p 192.168.1.100 -l nvs_map.bin

Edit the nvs_map.bin file using any editor that can edit binary file
the nvs_map.bin file looks like the following:



the MAC address feild in the nvs_map.bin is defined as follows:

nvs_map.bin address offset	MAC address
0x3 - 0x6	Local station MAC address LSB
0xA - 0xD	Local station MAC address MSB

The MAC LSB and MSB MAC address respectivally defined in the first line (offset 000000) of the nvs_map.bin as followes:
000000 01 6D 54 66 66 32 28 01 71 54 00 08 00 00 00 00

in that example the MAC address is as follows:

• the MSB part of the MAC address is: 00 00 80 00
  
• the LSB part of the MAC address is: 28 32 66 66
  

the way to verify that the MAC address had change correctly can be achived by connecting the EVM to an AP and to verify the connection Status as folowes:

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, po
Wer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
c
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
s
==========================
Status   : running
MAC      : 08.00.28.32.66.66
SSID     : s_ap
BSSID    : 00.26.ca.b6.47.d0
Channel  : 1
==========================

MAC address information

MAC address is in the form of: 00 00 80 00 28 32 66 66, that is any combination of 8 words, and for testing only its up to te user to define a unique MAC address for each WLAN entity in the network.
however for real system one must use MAC address that can be bought by ieee, please refer to <ieee MAC address tutorial>

return to main menu

Reference

HOME