NOTICE: The Processors Wiki will End-of-Life on January 15, 2021. It is recommended to download any files or other content you may need that are hosted on processors.wiki.ti.com. The site is now set to read only.

OMAPL138 Wireless Connectivity Demo

From Texas Instruments Wiki
Jump to: navigation, search

Description[edit]

  • This section walks through basic Wireless LAN demo scenarios.
  • The WLAN is operational through the CLI that is running over Terminal
  • Bluetooth is not functional
  • GUI is not functional with that release


Prerequisite[edit]

It is assumed that the hardware and the software are already installed, otherwise please refer to the <AM18 Getting started guide>
In addition make sure that a Calibration is performed before the first time working with WLAN on that platform. For Calibration procedure please refer to the following links: <AM18x Calibration process>
Turn on the EVM and log on as "root".

Demo Menu[edit]


Step 1. Power on
Step 2. Demo scenarios
Step 3. Operate the WLAN Menu from CLI
Step 4. connect to non secured WiFi network
Step 5. connect to secured WiFi network - WPA
Step 6. connect to secured WiFi network - WPA2
Step 7. Getting IP address
Step 8. WLAN PING test
Step 9. WLAN Throughput test


Demo scenarios[edit]

Below are the Bluetooth and WLAN scenarios that are supported in this demo

senario description
Connect to non secured WiFi network Non secured WiFi network
Connect to secured WiFi network WPA WiFi network
Connect to secured WiFi network WPA2 WiFi network



Hardware Setup[edit]


To run this demo you need the following:

  1. another PC connected to your Access Point with an Ethernet cable
  2. Connect PC via serial port in order to run the CLI (Commands Line Interface) to run WLAN commands)
  3. the Flat cable in the Picture below is used for Bluetooth therefore not needed for OMAPL138


PING BLK1.jpg

Power on[edit]


connect the EVM to terminal using the serial port, and then turn on the Power.

Booting with TI UBL
Device OPP (300MHz, 1.2V)

U-Boot 2009.11 (Mar 13 2011 - 15:08:49)

I2C:   ready
DRAM:  64 MB
MMC:   davinci: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
ARM Clock : 300000000 Hz
DDR Clock : 132000000 Hz
Net:   Ethernet PHY: GENERIC @ 0x00

Hit any key to stop autoboot:  3  2  1  0 
reading boot.scr

248 bytes read
## Executing script at c0600000
reading uImage

2187068 bytes read
## Booting kernel from Legacy Image at c0700000 ...
   Image Name:   Arago/2.6.32+2.6.33-rc4-psp03.20
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2187004 Bytes =  2.1 MB
   Load Address: c0008000
   Entry Point:  c0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.33-rc4 (sdk@nemo) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 PREEMPT Sun Mar 13 15:12:17 CDT 2011
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: DaVinci DA850/OMAP-L138/AM18xx EVM
Memory policy: ECC disabled, Data cache writeback
DaVinci da850/omap-l138/am18xx variant 0x1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 24320
Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw ip=off mem=32M@0xc0000000 mem=64M@0xc4000000 rootwait
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 32MB 64MB = 96MB total
Memory: 92704KB available (4164K code, 320K data, 148K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:245
Console: colour dummy device 80x30
Calibrating delay loop... 149.50 BogoMIPS (lpj=747520)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
DaVinci: 144 gpio irqs
regulator: core version 0.5
NET: Registered protocol family 16
da850_evm_init: mmcsd2 registration failed: -1bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
regulator: VDCDC1: 3200 <--> 3300 mV at 3300 mV 
regulator: VDCDC2: 1750 <--> 3300 mV at 3300 mV 
regulator: VDCDC3: 950 <--> 1375 mV at 1200 mV 
regulator: LDO1: 1800 mV 
regulator: LDO2: 1150 <--> 1300 mV at 1200 mV 
pca953x 1-0020: failed reading register
i2c-gpio i2c-gpio.1: using pins 20 (SDA) and 21 (SCL)
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Switching to clocksource timer0_1
musb_hdrc: version 6.0, cppi4.1-dma, host, debug=0
Waiting for USB PHY clock good...
musb_hdrc: USB Host mode controller at fee00000 using DMA, IRQ 58
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
EMAC: MII PHY configured, RMII PHY will not be functional
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 181
io scheduler noop registered (default)
da8xx_lcdc da8xx_lcdc.0: GLCD: Found Sharp_LK043T1DG01 panel
Console: switching to colour frame buffer device 60x34
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c42000 (irq = 25) is a AR7
serial8250.0: ttyS1 at MMIO 0x1d0c000 (irq = 53) is a AR7
serial8250.0: ttyS2 at MMIO 0x1d0d000 (irq = 61) is a AR7
console [ttyS2] enabled
brd: module loaded
ahci ahci: forcing PORTS_IMPL to 0x1
ahci ahci: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
ahci ahci: flags: ncq sntf pm led clo only pmp pio slum part ccc 
scsi0 : ahci
ata1: SATA max UDMA/133 irq 67
spi_davinci spi_davinci.1: DaVinci SPI driver in EDMA mode
Using RX channel = 18 , TX channel = 19 and event queue = 1
m25p80 spi1.0: m25p64 (8192 Kbytes)
Creating 4 MTD partitions on "m25p80":
0x000000000000-0x000000040000 : "U-Boot"
0x000000040000-0x000000050000 : "U-Boot Environment"
0x000000050000-0x0000007f0000 : "Linux"
0x0000007f0000-0x000000800000 : "MAC Address"
Read MAC addr from EEPROM: 00:08:ee:04:63:3d
spi_davinci spi_davinci.1: Controller at 0xfef0e000 
console [netcon0] enabled
netconsole: network logging started
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci ohci.0: DA8xx OHCI
ohci ohci.0: new USB bus registered, assigned bus number 2
ohci ohci.0: irq 59, io mem 0x01e25000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
input: TPS6507x Touchscreen as /devices/platform/i2c-gpio.1/i2c-1/1-0048/input/input0
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
omap_rtc: RTC power up reset detected
omap_rtc: already running
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
watchdog watchdog: heartbeat 60 sec
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCILL protocol initialized
cpuidle: using governor ladder
cpuidle: using governor menu
davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
davinci_mmc davinci_mmc.1: Using DMA, 4-bit mode
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.21.
usbcore: registered new interface driver snd-usb-audio
No device for DAI tlv320aic3x
asoc: tlv320aic3x <-> davinci-i2s mapping ok
ata1: SATA link down (SStatus 0 SControl 300)
ALSA device list:
  #0: DA850/OMAP-L138 EVM (tlv320aic3x)
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Clocks: disable unused emac
Clocks: disable unused aemif
Clocks: disable unused spi0
mmc0: new SDHC card at address e359
mmcblk0: mmc0:e359 SD04G 3.69 GiB 
regulator_init_complete: incomplete constraints, leaving LDO2 on
regulator_init_complete: incomplete constraints, leaving LDO1 on
regulator_init_complete: incomplete constraints, leaving VDCDC3 on
regulator_init_complete: incomplete constraints, leaving VDCDC2 on
regulator_init_complete: incomplete constraints, leaving VDCDC1 on
 mmcblk0: p1 p2
emac-mii: probed
omap_rtc omap_rtc: setting system clock to 2011-03-24 15:41:31 UTC (1300981291)
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 148K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udev: starting version 141
Remounting root file system...
Caching udev devnodes
Populating dev cachemv: cannot rename '/tmp/devices': No such file or directory
NET: Registered protocol family 10
logger: mount: mount point /proc/bus/usb does not exist
ALSA: Restoring mixer settings...
Configuring network interfaces... eth0: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=1:00, id=7c0f1)
ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.13.2) started
Sending discover...
PHY: 1:00 - Link is Up - 100/Full
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending discover...
No lease, forking to background
done.
Setting up IP spoofing protection: rp_filter.
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Starting Dropbear SSH server: dropbear.
Starting telnet daemon.
Starting syslogd/klogd: done
Starting thttpd.
CMEMK module: built on Mar 13 2011 at 15:29:13
  Reference Linux version 2.6.33
  File /sdk/build/DVSDK_4_02/4_02_00_04/arago-install/arago-tmp/work/da850-omapl138-evm-none-linux-gnueabi/ti-linuxutils-1_2_26_01_02-r52d/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
CMEM Range Overlaps Kernel Physical - allowing overlap
CMEM phys_start (0xc2000000) overlaps kernel (0xc0000000 -> 0xc6000000)
allocated heap buffer 0xc9000000 of size 0x1200000
heap fallback enabled - will try heap if pool buffer is not available
cmemk initialized
DSPLINK Module (1.65.00.02) created on Date: Mar 13 2011 Time: 15:31:24

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

Arago Project http://arago-project.org arago ttyS2

Arago 2011.02 arago ttyS2

Press "root" to login

arago login: root

The Wireless LAN folder is located in /usr/share/wl1271-demos. Go to the folder by typing: "cd /usr/share/wl1271-demos " Type "ls -l" to view all files in the wlan folder

root@am180x-evm:/usr/share/wl1271-demos/wlan# ls -l
-rwxr-xr-x    1 root     root         1938 Dec 13  2010 install-wlan.sh 

To start the wlan driver, please call install-wlan.sh script

 
root@arago:~# cd /usr/share/wl1271-demos/wlan/
root@arago:/usr/share/wl1271-demos/wlan# ./install-wlan.sh 
Installing WL1271-WLAN kernel modules...
TI WiLink 1271 SDIO: Driver loaded
  Success
TIWLAN: driver init
TIWLAN: 1398.242491: 
Zoom2 use external board configuration as well
wifi_probe: got wlan irq 207
wifi_probe: got wlan irq trigger falling flag
  Success
Loading firmware...
Success
Bringing-up the WLAN interface...
pInitParams->RoamingScanning_2_4G_enable 0 
mmc1: card claims to support voltages below the defined range. These will be ignored.
mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
mmc1: new SDIO card at address 0001
TIWLAN: Found TI/WLAN SDIO controller (vendor 0x97, device 0x4076, class 0x0)
TIWLAN: 1399.475619: CHIP VERSION... set 1273 chip top registers
TIWLAN: 1399.504982: Working on a 1273 PG 2.0 board.
TIWLAN: 1399.509964: Starting to process NVS...
TIWLAN: 1399.524189: No Nvs, Setting default MAC address
TIWLAN: 1399.529370: pHwInit->uEEPROMCurLen: 1c
TIWLAN: 1399.533703: ERROR: If you are not calibating the device, you will soon get errors !!!
TIWLAN: 1399.566083: Chip ID is 0x4030111.
TIWLAN: 1399.616013: FEM Type 1 
TIWLAN: 1399.733855: Firmware successfully downloaded.
TIWLAN: 1399.740092: FW download OK...
TIWLAN: 1399.757256: Firmware successfully downloaded.
TIWLAN: 1399.762250: FW download OK...
TIWLAN: 1399.768651: Firmware successfully downloaded.
TIWLAN: 1399.773645: FW download OK...
TIWLAN: 1399.783682: Firmware successfully downloaded.
TIWLAN: 1399.789909: FW download OK...
TIWLAN: 1399.797700: Firmware successfully downloaded.
TIWLAN: 1399.802696: FW download OK...
TIWLAN: 1399.809803: Finished downloading firmware.
TIWLAN: 1399.816097: Firmware running.
TIWLAN: 1399.836729: Firmware successfully downloaded.
TIWLAN: 1399.841726: FW download OK...
TIWLAN: 1399.859518: 
TIWLAN: 1399.865146: --------------------------------------------------------------------
TIWLAN: 1399.873213: Driver Version  : WiLink_Driver_6.1.0.0.144
TIWLAN: 1399.884126: Firmware Version: Rev 6.1.0.0.335
TIWLAN: 1399.889133: Station ID      : 08-00-28-12-34-56
TIWLAN: 1399.905097: --------------------------------------------------------------------
TIWLAN: 1399.924101: 
ADDRCONF(NETDEV_UP): tiwlan0: link is not ready
Success
Starting wpa_supplicant...
TIWLAN: 1399.968035: Interrogate TX/RX parameters
Success

Operate the WLAN Menu from CLI[edit]

in order to operate the WLAN menu (CLI) please run "wlan_cu" application from /usr/share/wl1271-demos/wlan folder

 
root@arago:/usr/share/wl1271-demos/wlan# wlroot@arago:/usr/share/wl1271-demos/wlan# 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

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit

connect to non secured WiFi network[edit]

Scan for WiFi networks

/
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
a
.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
s
Application scan started

Verify the Access point that were discovered during the Scan operation

.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
/
\> 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/
b
BssId List: Num=2
         MAC        Privacy Rssi  Mode    Channel    SSID
 00.0f.f7.0c.e8.f0     0    -45  Infra      1        ecs123
*00.21.d8.49.c7.40     0    -62  Infra     11        ecs

Connect to Access point

c ecs
126
OK
TIWLAN: 1203.029260: ************ NEW CONNECTION ************
TIWLAN: 1203.034868: -- SSID  = ecs 
TIWLAN: 1203.040156: -- BSSID = 0-21-d8-49-c7-40
TIWLAN: 1203.044621: ****************************************

Verify the connection

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
b
BssId List: Num=2
         MAC        Privacy Rssi  Mode    Channel    SSID
 00.0f.f7.0c.e8.f0     0    -45  Infra      1        ecs123
*00.21.d8.49.c7.40     0    -62  Infra     11        ecs
s
==========================
Status   : CONNECTED
MAC      : 08.00.28.12.34.56
SSID     : ecs
BSSID    : 00.21.d8.49.c7.40
Channel  : 11
==========================

connect to secured WiFi network - WPA[edit]

Perform Scanning for WiFi networks (to Discover Access Points)

/
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
a
.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
s
Application scan started

Verify the Access points that were discovered during Scan

.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
/
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit

\> 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/
b
BssId List: Num=2
         MAC        Privacy Rssi  Mode    Channel    SSID
 00.0f.f7.0c.e8.f0     0    -45  Infra      1        ecs123
 00.21.d8.49.c7.40     1    -61  Infra     11        ecs

Please note that the Access Point "ecs" supports Security, that can be seen by Privacy field = 1
next step is to define the Security mode

/ privacy authen 4
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting privacy authentication to 4
/ privacy encrypt 2
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting privacy encryption to 2
/ privacy eap 13
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting EapType to 13
/ privacy key 0
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting KeyType to 0
/ privacy Psk psk12345
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting PSKPassphrase to psk12345

Connect to the Access point

/ c c ecs
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
127
/ c sOK
TIWLAN: 1690.131264: ************ NEW CONNECTION ************
TIWLAN: 1690.136874: -- SSID  = ecs 
TIWLAN: 1690.142531: -- BSSID = 0-21-d8-49-c7-40
TIWLAN: 1690.146998: ****************************************

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
==========================
Status   : CONNECTED
MAC      : 08.00.28.12.34.56
SSID     : ecs
BSSID    : 00.21.d8.49.c7.40
Channel  : 11
==========================

Verify connection to Access Point

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
b
BssId List: Num=2
         MAC        Privacy Rssi  Mode    Channel    SSID
 00.0f.f7.0c.e8.f0     0    -45  Infra      1        ecs123
*00.21.d8.49.c7.40     1    -61  Infra     11        ecs

connect to secured WiFi network - WPA2[edit]

Scan for WiFi networks (Access Points)

/
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
a
.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
s
Application scan started

Verify the list of Access points were discovered during the Scan operation

.../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/
/
\> 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/
b
BssId List: Num=3
         MAC        Privacy Rssi  Mode    Channel    SSID
 00.0f.f7.0c.e8.f0     0    -45  Infra      1        ecs123
 00.21.d8.49.c7.40     1    -61  Infra     11        ecs
 00.26.18.c6.f7.4c     0    -91  Infra     11        ASUS

Configure the Security Settings of the Access Point that we want to connect to

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
/ privacy authen 7
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting privacy authentication to 7
/ privacy encrypt 3
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting privacy encryption to 3
/ privacy eap 13
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting EapType to 13
/ privacy key 0
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting KeyType to 0
/ privacy Psk psk12345
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Privacy> Authentication, Eap, encRyption, Keytype, Mixedmode, aNywpamode, Credentials, pskPassphrase, cerTificate, Supplicant/, Wep/
Setting PSKPassphrase to psk12345

Connect to the Access Point

/ c c ecs
\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
128
/ c sOK
TIWLAN: 1776.796898: ************ NEW CONNECTION ************
TIWLAN: 1776.805806: -- SSID  = ecs 
TIWLAN: 1776.810485: -- BSSID = 0-21-d8-49-c7-40
TIWLAN: 1776.814952: ****************************************

Verify connection

\> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit
.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
==========================
Status   : CONNECTED
MAC      : 08.00.28.12.34.56
SSID     : ecs
BSSID    : 00.21.d8.49.c7.40
Channel  : 11
==========================



Getting IP address[edit]

first step is to exit the CLI, do that by pewssing ctrl+c

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/
TiCon_Signal - got signal Ctrl+c ... exiting

Getting IP from Access Point - DHCP[edit]

To get the IP from the DHCP Server follow the below given step

root@am180x-evm:/usr/share/wl1271-demos/wlan# udhcpc -i tiwlan0
udhcpc (v1.13.2) started
Sending discover...
Sending select for 192.168.13.146...
Lease of 192.168.13.146 obtained, lease time 14400
adding dns 192.168.10.51
adding dns 192.168.10.54
root@am180x-evm:/usr/share/wl1271-demos/wlan#

Static IP - To set the IP statically[edit]

root@am180x-evm:/usr/share/wl1271-demos/wlan# ifconfig tiwlan0 192.168.13.146



WLAN PING test[edit]

This section assumes that the EVM is already connected to the Access Point, otherwise return to < return to Menu> to start the WLAN driver and connect to a non-secured WLAN network.

Running the demo[edit]

Configure the EVM WLAN IP address, and make sure that the EVM Ethernet port and WLAN port will not share the same IP subnet address.

root@am180x-evm:/usr/share/wl1271-demos/wlan# ifconfig tiwlan0 192.168.13.11 netmask 255.255.255.0 up 

verify that the WLAN port (tiwlan0) IP address is configured correctly

root@am180x-evm:/usr/share/wl1271-demos/wlan# ifconfig
eth0      Link encap:Ethernet  HWaddr 86:AF:AE:74:24:C9
          UP BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:33

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          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)

tiwlan0   Link encap:Ethernet  HWaddr 08:00:28:12:34:56
          inet addr:192.168.13.11  Bcast:192.168.13.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:28ff:fe12:3456/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:253 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:32383 (31.6 KiB)  TX bytes:468 (468.0 B) 


Configure the IP address of the Laptop that is connected to the Access Point via the Ethernet cable to be in the same subnet as the EVM WLAN port. In this example, we configure it to 192.168.13.68, and the gateway IP address is not important for this test

Network setting2.jpg

then use the Ping command to ping the PC that is connected to the Access Point

root@am180x-evm:/usr/share/wl1271-demos/wlan# ping 192.168.13.68
PING 192.168.13.68 (192.168.13.68): 56 data bytes
64 bytes from 192.168.13.68: seq=0 ttl=128 time=64.925 ms
64 bytes from 192.168.13.68: seq=1 ttl=128 time=2.698 ms
64 bytes from 192.168.13.68: seq=2 ttl=128 time=2.560 ms

--- 192.168.13.68 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 2.560/23.394/64.925 ms
root@am180x-evm:/usr/share/wl1271-demos/wlan# 


Similarly, we can ping to the EVM from the PC connected to the Access Point via Ethernet:

Ping.jpg

WLAN Throughput test[edit]

Hardware Setup[edit]

To run this demo you need another PC connected to the Access Point with an Ethernet cable, as shown below. To measure the throughput use the iPerf tool, and in this example we use only UDP downstream - i.e. UDP packets from the PC connected to the Access Point to the EVM.
PING BLK1.jpg This section assumes that the EVM connected to the Access Point, otherwise return to < return to Menu> to start the WLAN driver and connect to a non-secured WLAN network.

Iperf tool[edit]

In order to measure the throughout we are going to use the iPerf tool that is already installed on the EVM, and a graphical version of the iPerf tool called "IPerf" which runs on the PC side.

Running the demo[edit]

root@am180x-evm:/usr/share/wl1271-demos/wlan# ifconfig tiwlan0 192.168.13.11 netmask 255.255.255.0 up

Verify that the WLAN port (tiwlan0)IP address is configured correctly

root@am180x-evm:/usr/share/wl1271-demos/wlan# ifconfig
eth0      Link encap:Ethernet  HWaddr 86:AF:AE:74:24:C9
          UP BROADCAST MULTICAST  MTU:1500  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:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:33

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          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)

tiwlan0   Link encap:Ethernet  HWaddr 08:00:28:12:34:56
          inet addr:192.168.13.11  Bcast:192.168.13.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:28ff:fe12:3456/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:253 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:32383 (31.6 KiB)  TX bytes:468 (468.0 B) 


Configure the IP address of the Laptop that is connected to the Access Point via the Ethernet cable to be in the same sub net as the EVM WLAN port. In this example, we configure it to 192.168.13.68, and the gateway IP address is not important for this test.

Network setting2.jpg


Then use the iperf command to run iperf server on the EVM. In this example, we expect to receive UDP packets at port 7000 and print the results on the screen every one second

root@am180x-evm:/usr/share/wl1271-demos/wlan# iperf -s -i1 -p7000 -u

As a response to the previous command, we will see that iperf has started and ready to receive UDP packets

------------------------------------------------------------
Server listening on UDP port 7000
Receiving 1470 byte datagrams
UDP buffer size:   106 KByte (default)
------------------------------------------------------------ 


Now operate the iPerf client on the PC that will send Packets to EVM via the wireless medium. Configure iperf to:

  • Client
  • UDP
  • port 7000 (same as server configuration on the EVM)
  • send packets to server ip:192.168.13.11 which is the EVM IP address
  • UDP Bandwidth 30 MBytes/sec


After starting the iPerf client in the PC side, you may see the Server on the EVM starts receiving frames. In this example the throughput is about 13.5Mbits/sec. Note that you would expect to have a higher throughput if you were working in a clean environment like an RF chamber.

root@am180x-evm:/usr/share/wl1271-demos/wlan# iperf -s -i1 -p7000 -u
------------------------------------------------------------
Server listening on UDP port 7000
Receiving 1470 byte datagrams
UDP buffer size:   106 KByte (default)
------------------------------------------------------------
[  3] local 192.168.13.11 port 7000 connected with 192.168.13.68 port 43593  
[ ID] Interval  Transfer  Bandwidth   Jitter   Lost/Total Datagrams 
[  3] 0.0-300.2 sec  482 MBytes  13.5 Mbits/sec 0.769 ms 421160/765306 (55%)


WLAN Throughput Results[edit]

The WLAN throughput results are obtained by following the instructions given under Running the demo.


Windows PC as a server

D:\iperf-1_7_0-win32>iperf.exe -s -i1 -p7000 -u
------------------------------------------------------------
Server listening on UDP port 7000
Receiving 1470 byte datagrams
UDP buffer size: 8.00 KByte (default)
------------------------------------------------------------
[1928] local 192.168.0.130 port 7000 connected with 192.168.0.133 port 50440
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total Datagrams
[1928]  0.0- 1.0 sec  1.88 MBytes  15.7 Mbits/sec  0.841 ms 1852404883/ 1369 (1.4e+008%)
[1928]  1.0- 2.0 sec  1.76 MBytes  14.7 Mbits/sec  0.832 ms   85/ 1337 (6.4%)
[1928]  2.0- 3.0 sec  1.85 MBytes  15.5 Mbits/sec  1.109 ms   21/ 1342 (1.6%)
[1928]  3.0- 4.0 sec  1.86 MBytes  15.6 Mbits/sec  1.023 ms   44/ 1373 (3.2%)
[1928]  4.0- 5.0 sec  1.86 MBytes  15.6 Mbits/sec  1.227 ms   38/ 1366 (2.8%)
[1928]  5.0- 6.0 sec  1.83 MBytes  15.3 Mbits/sec  0.950 ms    2/ 1307 (0.15%)
[1928]  6.0- 7.0 sec  1.77 MBytes  14.9 Mbits/sec  1.127 ms  137/ 1400 (9.8%)
[1928]  7.0- 8.0 sec  1.78 MBytes  15.0 Mbits/sec  1.946 ms   14/ 1287 (1.1%)
[1928]  8.0- 9.0 sec  1.81 MBytes  15.2 Mbits/sec  1.430 ms    0/ 1289 (0%)
[1928]  9.0-10.0 sec  1.83 MBytes  15.3 Mbits/sec  1.504 ms   42/ 1344 (3.1%)
[1928]  0.0-10.0 sec  18.3 MBytes  15.3 Mbits/sec  1.081 ms  413/13437 (3.1%)
[1928]  0.0-10.0 sec  1 datagrams received out-of-order 

OMAPL138 EVM as client

root@arago:/usr/share/wl1271-demos/wlan# ./iperf -c 192.168.0.130 -p7000 -u -b 100m
------------------------------------------------------------
Client connecting to 192.168.0.130, UDP port 7000
Sending 1470 byte datagrams
UDP buffer size:  108 KByte (default)
------------------------------------------------------------
[  3] local 192.168.0.133 port 50440 connected with 192.168.0.130 port 7000
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-10.0 sec  18.9 MBytes  15.8 Mbits/sec
[  3] Sent 13453 datagrams
[  3] Server Report:
[  3]  0.0-10.0 sec  18.3 MBytes  15.3 Mbits/sec  1.080 ms  414/13437 (3.1%)
[  3]  0.0-10.0 sec  1 datagrams received out-of-order

HomepageIcon.jpgHOME

E2e.jpg {{
  1. switchcategory:MultiCore=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article OMAPL138 Wireless Connectivity Demo here.

Keystone=
  • For technical support on MultiCore devices, please post your questions in the C6000 MultiCore Forum
  • For questions related to the BIOS MultiCore SDK (MCSDK), please use the BIOS Forum

Please post only comments related to the article OMAPL138 Wireless Connectivity Demo here.

C2000=For technical support on the C2000 please post your questions on The C2000 Forum. Please post only comments about the article OMAPL138 Wireless Connectivity Demo here. DaVinci=For technical support on DaVincoplease post your questions on The DaVinci Forum. Please post only comments about the article OMAPL138 Wireless Connectivity Demo here. MSP430=For technical support on MSP430 please post your questions on The MSP430 Forum. Please post only comments about the article OMAPL138 Wireless Connectivity Demo here. OMAP35x=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article OMAPL138 Wireless Connectivity Demo here. OMAPL1=For technical support on OMAP please post your questions on The OMAP Forum. Please post only comments about the article OMAPL138 Wireless Connectivity Demo here. MAVRK=For technical support on MAVRK please post your questions on The MAVRK Toolbox Forum. Please post only comments about the article OMAPL138 Wireless Connectivity Demo here. For technical support please post your questions at http://e2e.ti.com. Please post only comments about the article OMAPL138 Wireless Connectivity Demo here.

}}

Hyperlink blue.png Links

Amplifiers & Linear
Audio
Broadband RF/IF & Digital Radio
Clocks & Timers
Data Converters

DLP & MEMS
High-Reliability
Interface
Logic
Power Management

Processors

Switches & Multiplexers
Temperature Sensors & Control ICs
Wireless Connectivity