AM18x Wireless Connectivity Demo

Description
This section walks through basic Bluetooth and Wireless LAN demo scenarios.

Prerequisite
It is assumed that the hardware and the software are already installed, otherwise please refer to the  Please download the latest BT firmware (BTS) for WL1271 and WL1271L devices from  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:  Turn on the EVM and log on as "root".

Demo Menu
Step 1. Folder structure Step 2. Demo scenarios Step 3. Start the Bluetooth menu Step 4. Bluetooth A2DP profile Step 5. Bluetooth FTP profile Step 6. Bluetooth OPP profile Step 7. Start WLAN menu Step 8. Connect to non secured WLAN network Step 9. WLAN PING test Step 10. WLAN Throughput test Step 11. Web Browsing via WLAN

Folder structure
After powering on the board, log on, you will get into the main folder root@am180x-evm. The demo images can be installed under any arbitrary user_directory, in this example the user_directory is wl1271-demos.

To see the folder structure type 'ls -l' in the working directory: root@am180x-evm:/usr/share# ls -l wl1271-demos drwxr-xr-x   4 root     root         4096 Dec 10 07:18 wl1271-demos

To see the Demo application folder structure change directory to wl1271-demos: root@am180x-evm:/usr/share# cd wl1271-demos/ root@omap3evm:~/DEMO# ls -l root@am180x-evm:/usr/share/wl1271-demos# ls -l drwxr-xr-x   4 root     root         4096 Dec 10 07:18 bluetooth drwxr-xr-x   2 root     root         4096 Dec 10 07:18 wlan root@am180x-evm:/usr/share/wl1271-demos#  return to Menu

Demo scenarios
Below are the Bluetooth and WLAN scenarios that are supported in this demo  return to Menu

Start the Bluetooth menu
To Start the Bluetooth demo run the BT_Demo.sh script under bluetooth/scripts folder: root@am180x-evm:/usr/share/wl1271-demos# cd bluetooth/ root@am180x-evm:/usr/share/wl1271-demos/bluetooth# ls gallery scripts root@am180x-evm:/usr/share/wl1271-demos/bluetooth# cd scripts/ root@am180x-evm:/usr/share/wl1271-demos/bluetooth/scripts# ./BT_Demo.sh following is the screen capture after calling the BT_Demo.sh script

Starting BT Demo .......

/* * ################################################# *                 Cleaning BT * ################################################# */

!!!!!!!!!!! Start from the MAIN MENU !!!!!!!!!!!!!!!!!

/* * ################################################# *                 Initialize BT * ################################################# */

Gpio value is :15 WL1271: BT Enable Found a Texas Instruments' chip! Firmware file : /lib/firmware/TIInit_7.2.31.bts Loaded BTS script version 1 texas: changing baud rate to 2000000, flow control to 1 Device setup complete

+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down ====>

Menu General Description:
The BT_Demo.sh first runs the WL1271 Bluetooth init script. 'BT en' on the daughtercard should light red indicating that BT is active ready to respond to user commands. Then the MAIN MENU is displayed with the following options. There are some known issues with the command line BT scripts that are listed in the Demo errata section. Until these known issues are fixed, please avoid: (a) typing ^C or ^Z to exit instead of using menu command #10; If you mistakenly do that an EVM power cycle is required. (b) pressing the backspace key or typing extra spaces when entering commands or data in each of the demo steps. Doing that will result in error message. In this case ignore the error messages and repeat the previous step.

 return to Menu

Hardware Setup
To run this demo you need a stero BT Headphones like the Cellular Innovations HFBLU-STCL1 or any other headset that support the BT A2DP profile

Running the demo
From the BT main menu select option 1 to perform Scan ====> 1

/* * ########### BT-Scan ############# * Scan for the remote BT devices * ################################# */

Scanning ... 00:11:67:80:05:0D      HFBLU-STCL1

+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down ====>

select option 8 to pair with the BT device In this example we will connect the HFBLU-STCL1 device (which is a Bluetooth headphones) The BD_Addr of the Bluetooth device is indicated in the Scan results, for example for the "HFBLU-STCL1" device BD_Addr is 00:11:67:80:05:0D ====> 8

Help:

Important: Ensure that the remote device is in pairing/scanning mode.

Before running Pairing-Test, ensure that we have the following mandatory inputs; a. BD Address of Remote BT-Device (Use Option-1 of MAIN MENU)

1. Continue... 2. Goto MAIN MENU ====> 1

/* * ########## BT-Pair ######## * Pair to a remote BT device * ########################### */

Enter the BD Addr of remote Device to Pair

Enter the BD_Addr of the remote Bluetooth device, in that example connect to the HFBLU-STCL1 device with BD_Addr 00:11:67:80:05:0D ====> 00:11:67:80:05:0D Pairing with 00:11:67:80:05:0D, Please wait..

Pairing success ...

+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down ====>

The EVM and the BT headphones are now paired and the A2DP test can be started by selecting option 7 ====> 7

Help: Before running A2DP-Test, ensure that we have the following mandatory inputs; a. BD Address of Remote BT-Device (Use Option-1 of MAIN MENU). b. The remote A2DP device is paired with us (Use Option-8 of MAIN MENU).

1. Start Audio... 2. Stop Audio... 3. Goto MAIN MENU select option 1 to continue, if you already have the Bluetooth device BD_Adrr ====> 1

/* * ################################# A2DP ################################### * Advanced Audio Distribution Profile (A2DP) defines how the high quality * audio can be streamed from one device to another over Bluetooth connection. * ########################################################################## */

Enter the BD Address of the A2DP device Enter the Bluetooth Device BD_Addr (as in the Scan results) ====> 00:11:67:80:05:0D '/etc/asound.conf' got updated, ensure that we have paired with the device 00:11:67:80:05:0D for A2DP.

Select Any Audio File ...

The following files are available at gallery(/usr/share/wl1271-demos/bluetooth/gallery); Document.jpg            Pop.wav                  WLAN_Bluetooth_demo.wmv

Enter the Audio wav File Name ... Select Any Audio File ... The following files are available at gallery Document.jpg WLAN_Bluetooth_demo.wmv Pop.wav song_8000.wav Enter the Audio wav File Name ...

====> Pop.wav Playing WAVE '/usr/share/wl1271-demos/bluetooth/gallery/Pop.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

2. Stop Audio... 3. Goto MAIN MENU ====>

Please enjoy the music playing on the Bluetooth headphones.

The Pop.wav file in this example will play for about two minutes. Due to a know issue with the demo scripts in this release your need to wait until the music play is over before you can continue. Do not press ^C or ^Z as this will result in a system crash.

 return to Menu

Hardware Setup
Please make sure that Bluetooth in your laptop is configured to be discoverable or "available to be searched". This may require changing the security level settings on the PC Bluetooth Connection Manager.

Running the Demo
Starting from the Main Menu:

+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down select option 1 to scan for BT devices and wait for the discovered devices list to show up. ====> 1

/* * ########### BT-Scan ############# * Scan for the remote BT devices * ################################# */

Scanning ... 00:1E:37:C2:F6:12      n/a D4:88:90:D6:10:8D      Mist 00:1B:10:00:20:3A      SALMAALI 00:1B:10:00:1F:89      MistXWin 00:23:D4:E9:0B:2E      n/a

+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down ====> In this example we pair with a laptop named "Mist" with a BD_Addr of D4:88:90:D6:10:8D. You will need to find your laptop in the list and copy its BT address.

select option 8 to pair with the BT device

====> 8

Help:

Important: Ensure that the remote device is in pairing/scanning mode.

Before running Pairing-Test, ensure that we have the following mandatory inputs; a. BD Address of Remote BT-Device (Use Option-1 of MAIN MENU)

1. Continue... 2. Goto MAIN MENU

select option 1 to continue (as we already know the BD_Addr) ====> 1

/* * ########## BT-Pair ######## * Pair to a remote BT device * ########################### */

Enter the BD Addr of remote Device to Pair

Enter the laptop's BD Address (as copied from the sacn results) ====> D4:88:90:D6:10:8D Pairing with D4:88:90:D6:10:8D, Please wait..

Pairing success ...

+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down Now select option 4 to run FTP Test

====> 4

Options for FTP tests
1 - FTP from Remote Device to OMAP3EVM 2 - FTP from OMAP3EVM to remote device 3 - Goto MAIN MENU

FTP from a Remote Device to the WL1271 host
select option 1 to send the file from the laptop to the WL1271 host ====> 1

/* * ########################### BT-FTP ############################### * File Transfer Profile (FTP) provides capability to transfer files * and folders in an object store (file system) of another system. * ################################################################## */

Note: - FTP Server started, send file over BT-FTP from the remote device. There will not be any notification on EVM when data transfer completes. Please ensure that received file presents in the path /usr/share/wl1271-demos/bluetooth/gallery.

Enter Any key After FTP transfer:

The EVM is now waiting for the FTP session to start To start the FTP session from your laptop right click on the document you want to send The following Window then opens: Click "Next" and browse for the BT Devices (am1808x evm) and set Passkey: Select the option "Next" to send or receive the file Click the "Next" button to browse for the file you want to send to the EVM: Upon transfer completion a "File transfer was successful" message will show up on your PC: Below is the screen shot of the EVM terminal: Enter Any key After FTP transfer: +++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down ====>

No message will be printed on the EVM during the FTP file transfer. Upon completion of the file transfer on your PC, enter any key to go back to the main menu

The received file was saved under /usr/share/wl1271-demos/bluetooth/gallery. To verify the same exit the demo menu (selecting option #10 or #11 ). ====> 10 root@am180x-evm:/usr/share/wl1271-demos/bluetooth/scripts# root@am180x-evm:/usr/share/wl1271-demos/bluetooth/gallery# ls -l -rwxr-xr-x   1 root     root         4710 Dec 10 06:35 Document.jpg -rw-r--r--   1 root     root        10752 Dec 10 13:31 New Microsoft Word Document.doc -rwxr-xr-x   1 root     root     20878894 Dec 10 06:35 Pop.wav -rwxr-xr-x   1 root     root      4549049 Dec 10 06:35 WLAN_Bluetooth_demo.wmv root@am180x-evm:/usr/share/wl1271-demos/bluetooth/gallery#

FTP from WL1271 host to Remote Device
To transfer a file from EVM to the laptop, know the BD Address of the laptop and the channel number of the file transfer service in the laptop. The following instructions show how to obtain the channel number.

If the laptop is not paired yet with the EVM, pair it first selecting option 8 in the main menu in the same manner demonstrated in the previous demo. +++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down select option 2 to read (get) the BT capabilities of the laptop ====> 2

/* * #################### BT-Browse ################## * Browse the Device and get the device capabilities * ################################################# */

Note: Capture the following LOG for further reference

Enter the BD Addr of remote Device for browsing Enter the BD Addr of the laptop (in this example BD Addr is D4:88:90:D6:10:8D taken from the Scan Results ) ====> D4:88:90:D6:10:8D

=
======= D4:88:90:D6:10:8D ======================

Browsing D4:88:90:D6:10:8D ... Service RecHandle: 0x10000 Service Class ID List: "PnP Information" (0x1200)

Service Name: HSP PS Audio Gateway Service RecHandle: 0x10001 Service Class ID List: "Headset Audio Gateway" (0x1112) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 1 Profile Descriptor List: "Headset" (0x1108) Version: 0x0100

Service Name: HFP PS Audio Gateway Service RecHandle: 0x10002 Service Class ID List: "Handsfree Audio Gateway" (0x111f) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 2 Profile Descriptor List: "Handsfree" (0x111e) Version: 0x0105

Service Name: Dialup Networking Service RecHandle: 0x10003 Service Class ID List: "Dialup Networking" (0x1103) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 3 Profile Descriptor List: "Dialup Networking" (0x1103) Version: 0x0100

Service Name: Serial Server Service RecHandle: 0x10004 Service Class ID List: "Serial Port" (0x1101) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 4

Service Name: Object Exchange Service RecHandle: 0x10005 Service Class ID List: "OBEX Object Push" (0x1105) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 5 "OBEX" (0x0008) Profile Descriptor List: "OBEX Object Push" (0x1105) Version: 0x0100

Service Name: File Transfer Service RecHandle: 0x10006 Service Class ID List: "OBEX File Transfer" (0x1106) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 6 "OBEX" (0x0008) Profile Descriptor List: "OBEX File Transfer" (0x1106) Version: 0x0100

Service RecHandle: 0x10007 Service Class ID List: "AV Remote Target" (0x110c) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 23 "AVCTP" (0x0017) uint16: 0x100 Profile Descriptor List: "AV Remote" (0x110e) Version: 0x0100

Service Name: Advanced audio source Service RecHandle: 0x10008 Service Class ID List: "Audio Source" (0x110a) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 25 "AVDTP" (0x0019) uint16: 0x100 Profile Descriptor List: "Advanced Audio" (0x110d) Version: 0x0100

Service Name: Sim Access Service RecHandle: 0x10009 Service Class ID List: "SIM Access" (0x112d) "Generic Telephony" (0x1204) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 7 Profile Descriptor List: "SIM Access" (0x112d) Version: 0x0102

=
======================================= The above list specifies all the BT capabilities that are supported by the laptop. The relevant information for this demo is the Channel number in the File Transfer Service.

In the example above identify the section that says: "Service Name: File Transfer Service" and look for the channel number under the "Protocol Descriptor List" part. The channel number in this example is 6 as captured below.

Service Name: File Transfer Service RecHandle: 0x10006 Service Class ID List: "OBEX File Transfer" (0x1106) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 6 "OBEX" (0x0008) Profile Descriptor List: "OBEX File Transfer" (0x1106) Version: 0x0100 We now have the BD Addres and the FTP channel number of the laptop. Next step is to start the file transfer from the menu. +++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down select option 4 to start the FTP test ====> 4

Options for FTP tests
1 - FTP from Remote Device to OMAP3EVM 2 - FTP from OMAP3EVM to remote device 3 - Goto MAIN MENU select option 2 for sending file from WL1271 to remote device via FTP ====> 2

Help: Before running FTP-Test, ensure that we have the following mandatory inputs; a. BD Address of Remote BT-Device (Use Option-1 of MAIN MENU). b. Channel Number of the FTP service of that device. (Use Option-2 of MAIN MENU).

1. Continue... 2. Goto MAIN MENU ====> select option 1 to Continue ====> 1

/* * ########################## BT-FTP ################################ * File Transfer Profile (FTP) provides capability to transfer files * and folders in an object store (file system) of another system. * ################################################################## */

FTP from OMAP3EVM to remote device

Note: For this test ensure that we have BD_ADDR of remote device and CH_NUM of   this remote device for FTP service.

Enter the BD_ADDR of the remote Device for FTP test Enter the BD_ADDR of your laptop(BD Addr in this example is D4:88:90:D6:10:8D taken from the Scan Results ) ====> D4:88:90:D6:10:8D Enter the channel number of FTP service ====> Enter the channel number of FTP service (channel = 6, from the FTP service in the BT device capabilities list) ====> 6

Local File Available under "/usr/share/wl1271-demos/bluetooth/gallery"

Document.jpg                    Pop.wav New Microsoft Word Document.doc WLAN_Bluetooth_demo.wmv

Enter the local file name to be sent over FTP

Enter the file name (including full path) to be sent via FTP profile. In this case we are transferring a music file "Pop.wav" that is stored under /usr/share/wl1271-demos/bluetooth/gallery/Pop.wav ====> Pop.wav Connecting..\done Tried to connect for 572ms Sending "/usr/share/wl1271-demos/bluetooth/gallery/Pop.wav"...\ done Disconnecting..-done ]

Browse your laptop directory and verify that the file was successfully received.

 return to Menu

Hardware Setup
To run this demo you need a mobile phone that supports the BT OPP Profile or Laptop with BT connection that support OPP profile

Running the demo
From the BT main menu select option 1 to perform Scan +++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down

====> 1

/* * ########### BT-Scan ############# * Scan for the remote BT devices * ################################# */

Scanning ... 00:1E:37:C2:F6:12      n/a D4:88:90:D6:10:8D      Mist 00:1B:10:00:20:3A      SALMAALI 00:1B:10:00:1F:89      MistXWin 00:23:D4:E9:0B:2E      n/a

+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down

To transfer the file from the Remote device (Mobile Phone or laptop)to the EVM, know the BD Address of the BT remote device and the channel number of the OBEX Object Push service of the Remote Device. The following instruction shows how to obtain the channel number.

select option 2 to get the remote device capabilities, and then enter the Remote device BD Address in this example we work with Mist that has BD Address D4:88:90:D6:10:8D (see Scan results) ====> 2

/* * #################### BT-Browse ################## * Browse the Device and get the device capabilities * ################################################# */

Note: Capture the following LOG for further reference

Enter the BD Addr of remote Device for browsing

Enter the BD Addr of the remote BT device you get the capabilities from ====> D4:88:90:D6:10:8D

=
======= D4:88:90:D6:10:8D ======================

Browsing D4:88:90:D6:10:8D ... Service RecHandle: 0x10000 Service Class ID List: "PnP Information" (0x1200)

Service Name: HSP PS Audio Gateway Service RecHandle: 0x10001 Service Class ID List: "Headset Audio Gateway" (0x1112) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 1 Profile Descriptor List: "Headset" (0x1108) Version: 0x0100

Service Name: HFP PS Audio Gateway Service RecHandle: 0x10002 Service Class ID List: "Handsfree Audio Gateway" (0x111f) "Generic Audio" (0x1203) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 2 Profile Descriptor List: "Handsfree" (0x111e) Version: 0x0105

Service Name: Dialup Networking Service RecHandle: 0x10003 Service Class ID List: "Dialup Networking" (0x1103) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 3 Profile Descriptor List: "Dialup Networking" (0x1103) Version: 0x0100

Service Name: Serial Server Service RecHandle: 0x10004 Service Class ID List: "Serial Port" (0x1101) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 4

Service Name: Object Exchange Service RecHandle: 0x10005 Service Class ID List: "OBEX Object Push" (0x1105) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 5 "OBEX" (0x0008) Profile Descriptor List: "OBEX Object Push" (0x1105) Version: 0x0100

Service Name: File Transfer Service RecHandle: 0x10006 Service Class ID List: "OBEX File Transfer" (0x1106) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 6 "OBEX" (0x0008) Profile Descriptor List: "OBEX File Transfer" (0x1106) Version: 0x0100

Service RecHandle: 0x10007 Service Class ID List: "AV Remote Target" (0x110c) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 23 "AVCTP" (0x0017) uint16: 0x100 Profile Descriptor List: "AV Remote" (0x110e) Version: 0x0100

Service Name: Advanced audio source Service RecHandle: 0x10008 Service Class ID List: "Audio Source" (0x110a) Protocol Descriptor List: "L2CAP" (0x0100) PSM: 25 "AVDTP" (0x0019) uint16: 0x100 Profile Descriptor List: "Advanced Audio" (0x110d) Version: 0x0100

Service Name: Sim Access Service RecHandle: 0x10009 Service Class ID List: "SIM Access" (0x112d) "Generic Telephony" (0x1204) Protocol Descriptor List: "L2CAP" (0x0100) "RFCOMM" (0x0003) Channel: 7 Profile Descriptor List: "SIM Access" (0x112d) Version: 0x0102

=
=======================================

OBEX Object Push channel number is 5 as appears under the Service Name: Object Exchange +++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down

select option 8 to pair with the BT device In this example we connect to the BT device- Mist. The BD_Addr of the Bluetooth device is indicated in the Scan results, for example for the "Mist" device BD_Addr is D4:88:90:D6:10:8D

====> 8

Help:

Important: Ensure that the remote device is in pairing/scanning mode.

Before running Pairing-Test, ensure that we have the following mandatory inputs; a. BD Address of Remote BT-Device (Use Option-1 of MAIN MENU)

1. Continue... 2. Goto MAIN MENU

select option 1 to continue

====> 1

/* * ########## BT-Pair ######## * Pair to a remote BT device * ########################### */

Enter the BD Addr of remote Device to Pair

Type the BD_Addr of the remote Bluetooth device, in this example connect to Mist device with BD_Addr D4:88:90:D6:10:8D ====> D4:88:90:D6:10:8D Pairing with D4:88:90:D6:10:8D, Please wait..

Pairing success ...

+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down

The EVM and the Mobile phone are now paired and the OPP test can be started by selecting option 3 in the main menu

====> 3

Help: Before running OPP-Test, ensure that we have the following mandatory inputs; a. BD Address of Remote BT-Device (Use Option-1 of MAIN MENU). b. Channel Number of the OPP service of that device (Use Option-2 of MAIN MENU).

1. Continue... 2. Goto MAIN MENU select option 1 to continue, if you already have the Bluetooth device BD_Adrr ====> 1

Options for OPP test
1 - Object Push from Remote-Device to WL1271-Host 2 - Object push from WL1271-Host to Remote-Device 3 - Goto MAIN MENU

select option 1 to continue to perform the file transfer from the BT Device to the EVM ====> 1

/* * ############################### BT-OPP ################################## * Object Push Profile (OPP) is for sending objects such as pictures, * virtual business cards etc. It is called push because the transfers * are always instigated by the sender (client), not the receiver (server). * Received files will be copied to pwd - /usr/share/wl1271-demos/bluetooth/scripts * ######################################################################### */

--- Object Push from Remote-Device to WL1271-Host --- Ignore the following debug messages if you get it     "Unknown event!" /     "Link broken (this does not have to be an error)! " / "OBEX_HandleInput returned!! "

Received files will be copied to pwd -     /usr/share/wl1271-demos/bluetooth/scripts

Waiting for connection... Press "Enter" to stop the OPP server:

Unknown event! .HEADER_LENGTH = 173 put_done Skipped header 42 Filename = Aali .vcf Wrote Aali .vcf (173 bytes)

Link broken (this does not have to be an error)! OBEX_HandleInput returned!!

Now, the file was successfully sent from the BT Device to the EVM. Enter q to return to the main menu q +++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down ====>

Send file from EVM to Remote Device using OPP profile
+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down

====> 3 select option 3 for OPP testing

Options for OPP test
1 - Object Push from Remote-Device to WL1271-Host 2 - Object push from WL1271-Host to Remote-Device 3 - Goto MAIN MENU

select option 2 to transfer file from EVM to BT Device(Remote device) ====> 2

/* * ############################### BT-OPP ################################### * Object Push Profile (OPP) is for sending objects such as pictures, * virtual business cards etc. It is called push because the transfers * are always instigated by the sender (client), not the receiver (server). * ########################################################################## */

--- Object push from WL1271-Host to Remote-Device ---

Enter BD address and channel of the BT Device(Remote device) Enter the BD_ADDR of the remote Device for OPP test ====> D4:88:90:D6:10:8D Enter the channel number of OPP service for the D4:88:90:D6:10:8D ====> 5

At this point you will be requested by the BT Device to approve the file transfer from the EVM Local File Available ...

Document.jpg                    Pop.wav New Microsoft Word Document.doc WLAN_Bluetooth_demo.wmv Enter the Local file to be transferred ====> Document.jpg name=/usr/share/wl1271-demos/bluetooth/gallery/Document.jpg, size=4710 Local device 00:23:D4:E8:5D:91 Remote device D4:88:90:D6:10:8D (5) Connection established

+++++++++++++++++++++++++++++++++++++++++++++++++++++              MAIN NENU +++++++++++++++++++++++++++++++++++++++++++++++++++++   1 - BT Scan Remote Devices 2 - BT Get capabilities of Remote Device 3 - OPP Test 4 - FTP Test 5 - HID Test 6 - HSP Test 7 - A2DP Test 8 - Pair Remote Device 9 - Unpair Remote Device 10 - Exit Without BT Shut Down 11 - Exit With BT Shut Down ====>

File was sent successfully.  return to Menu

Start WLAN menu
If you are still in the BT demo menu, please exit using menu command #10 or #11.

To run the WLAN demo you need to have a WLAN access point available. We can start WLAN menu using the matrix GUI and manually

Using Matrix GUI
Click on the "settings" option on the Matrix GUI Menu Then click on the "Wi-Fi" option in the "settings" menu to bring up WLAN, wait till WLAN GUI (wpa_gui) window comes up. As a response to the above, the following are the logs on the linux terminal root@am180x-evm:/usr/share/wl1271-demos# TI WiLink 1271 SDIO: Driver loaded TIWLAN: driver init TIWLAN: 477.356387: Zoom2 use external board configuration as well wifi_probe: got wlan irq 207 wifi_probe: got wlan irq trigger falling flag 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: 478.512527: CHIP VERSION... set 1273 chip top registers TIWLAN: 478.544446: Working on a 1273 PG 2.0 board. TIWLAN: 478.571213: Starting to process NVS... TIWLAN: 478.575505: No Nvs, Setting default MAC address TIWLAN: 478.619490: pHwInit->uEEPROMCurLen: 1c TIWLAN: 478.623776: ERROR: If you are not calibating the device, you will soon get errors !!! TIWLAN: 478.680993: Chip ID is 0x4030111. TIWLAN: 478.752530: FEM Type 1 TIWLAN: 479.128189: Firmware successfully downloaded. TIWLAN: 479.160270: FW download OK... TIWLAN: 479.196589: Firmware successfully downloaded. TIWLAN: 479.219467: FW download OK... TIWLAN: 479.224611: Firmware successfully downloaded. TIWLAN: 479.249510: FW download OK... TIWLAN: 479.258056: Firmware successfully downloaded. TIWLAN: 479.280790: FW download OK... TIWLAN: 479.287605: Firmware successfully downloaded. TIWLAN: 479.310796: FW download OK... TIWLAN: 479.316573: Finished downloading firmware. TIWLAN: 479.354867: Firmware running. TIWLAN: 479.375152: Firmware successfully downloaded. TIWLAN: 479.399553: FW download OK... TIWLAN: 479.441015: TIWLAN: 479.443030: TIWLAN: 479.501027: Driver Version : WiLink_Driver_6.1.0.0.144 TIWLAN: 479.506807: Firmware Version: Rev 6.1.0.0.335 TIWLAN: 479.527062: Interrogate TX/RX parameters Station ID     : 08-00-28-12-34-56 TIWLAN: 479.542769: TIWLAN: 479.569463:

Manually
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 follow the below mentioned steps root@am180x-evm:/usr/share/wl1271-demos/wlan# ./install-wlan.sh Installing WL1271-WLAN kernel modules... TI WiLink 1271 SDIO: Driver loaded Success TIWLAN: driver init TIWLAN: 4205.087860: 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: 4206.288305: CHIP VERSION... set 1273 chip top registers TIWLAN: 4206.318407: Working on a 1273 PG 2.0 board. TIWLAN: 4206.323490: Starting to process NVS... TIWLAN: 4206.335377: No Nvs, Setting default MAC address TIWLAN: 4206.340558: pHwInit->uEEPROMCurLen: 1c TIWLAN: 4206.344894: ERROR: If you are not calibating the device, you will soon get errors !!! TIWLAN: 4206.387442: Chip ID is 0x4030111. TIWLAN: 4206.417286: FEM Type 1 TIWLAN: 4206.573256: Firmware successfully downloaded. TIWLAN: 4206.579486: FW download OK... TIWLAN: 4206.596387: Firmware successfully downloaded. TIWLAN: 4206.601381: FW download OK... TIWLAN: 4206.607858: Firmware successfully downloaded. TIWLAN: 4206.612856: FW download OK... TIWLAN: 4206.622696: Firmware successfully downloaded. TIWLAN: 4206.628926: FW download OK... TIWLAN: 4206.636674: Firmware successfully downloaded. TIWLAN: 4206.641671: FW download OK... TIWLAN: 4206.648801: Finished downloading firmware. TIWLAN: 4206.653770: Firmware running. TIWLAN: 4206.674434: Firmware successfully downloaded. TIWLAN: 4206.680644: FW download OK... TIWLAN: 4206.686395: TIWLAN: 4206.688506: TIWLAN: 4206.706489: Driver Version : WiLink_Driver_6.1.0.0.144 TIWLAN: 4206.727547: Firmware Version: Rev 6.1.0.0.335 TIWLAN: 4206.750290: Interrogate TX/RX parameters Station ID     : 08-00-28-12-34-56 TIWLAN: 4206.759719: TIWLAN: 4206.770167: ADDRCONF(NETDEV_UP): tiwlan0: link is not ready Success Starting wpa_supplicant... Success

Now you may run the application "wlan_cu"

Then to connect to the CLI type : wlan_cu root@am180x-evm:/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 The 1271 drivers are being loaded and started. The wlan command line interface application (CLI) is brought up and the WL1271 is now ready. To confrim the current version please enter from the main menu: / u u Driver version: WiLink_Driver_6.1.0.0.144_NOCCX Firmware version: Rev 6.1.0.0.335  return to Menu

Using Matrix GUI
Click on the "settings" option on the Matrix GUI Menu Then click on the "Wi-Fi" option in the "settings" menu to bring up WLAN, wait till WLAN GUI (wpa_gui) window comes up. Click on the "scan" option to get the list of available APs Select the desired AP and double click to connect, this would pop up another window(NetworkConfig) for setting up the AP. Then enter the Encryption and PSK in case of a security mode using a keyboard that can be connected to the board using an USB hub. Click on the option "Add" (Note: you have to reduce the size of NetworkConfig window to see the Add button at the bottom.) this will save the configuration of the AP. Close the ‘Scan results’ window. Now, this APs SSID can be seen in the ‘Network’ combo box. Select this SSID and then Click "connect" to connect to the AP and get the IP address (this may take few seconds), and you can now see an IP address coming up on the ‘IP address’ tab.

NOTE: In this case the 'IP settings' 'method' is set to DHCP. i.e., ‘File’ > ‘IP Settings’ > ‘Method' – 'DHCP’ As a response to the above, the following are the logs on the linux terminal TIWLAN: 959.832057: ************ NEW CONNECTION ************ TIWLAN: 959.837580: -- SSID = sdk TIWLAN: 959.859606: -- BSSID = 0-e-38-62-63-f0 TIWLAN: 959.863894: ****************************************

To configure Static IP in WLAN GUI (wpa_gui) go to ‘File’ ->‘IP Settings’ -> ‘Method – Manual’ and set IP address, Netmask and Gateway Address.

Manually
Below is the main CLI menu that shows up after running the wlan_cu script. \> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit From the CLI select option 'a' in order to get into the scan menu a .../scAn> Start, sTop, Wextstart, configApp/, configpEriodic/, configPolicy/

From the Scan Menu select option 's' to start the scan s Application scan started Scanning for access points has now started. It takes a few seconds to complete the scan and no further indication is provided upon scan completion Press "/" to return to the CLI main menu / \> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/ , dEbug/, biT/, aboUt, Quit select option 'c' to get into the Connection menu c c .../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

select option 'b' for full Bssid_list. This will show the list and the amount of Access points discovered during the scan process. b b BssId List: Num=5 MAC       Privacy Rssi  Mode    Channel    SSID 00.25.9c.bb.01.cf    0    -45  Infra      1        sdk

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

Now connect to one of the Access points listed in the Bssid_list. In this example we connect to an access point with name sdk, that has 0 in the Privacy field, indicating that this access point is non secured. c sdk 0 OK ADDRCONF(NETDEV_CHANGE): tiwlan0: link becomes ready TIWLAN: 438.197381: ************ NEW CONNECTION ************ TIWLAN: 438.205376: -- SSID = sdk TIWLAN: 438.210378: -- BSSID = 0-25-9c-bb-1-cf TIWLAN: 438.214672: ****************************************

.../Connection> Bssid_list, Connect, Disassociate, Status, Full_bssid_list, wPs/

From anywhere in the sub Menus select option '/ q' to exit from the CLI menu and return to the linux prompt \> Driver/, Connection/, Management/, Show/, Privacy/, scAn/, roaminG/, qOs/, poWer/, eVents/, Bt coexsistance/, Report/, dEbug/, biT/, aboUt, Quit q root@am180x-evm:/usr/share/wl1271-demos/wlan# 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# To set the IP statically root@am180x-evm:/usr/share/wl1271-demos/wlan# ifconfig tiwlan0 192.168.13.146  return to Menu

Hardware Setup
To run this demo you need another PC connected to your Access Point with an Ethernet cable, as shown below. 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
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

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:  return to Menu

Hardware Setup
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. 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
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
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.



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: 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
 * 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

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%)

 return to Menu

Hardware Setup


Please make sure Matrix GUI and a keyboard is available for Web Browsing

Running the Demo
To Start Web Browsing on AM18x, make sure that a WiFi access point is available and connected to the internet.

Select the option “Browser” from the main menu to start browsing which should pop up a web browser Edit the URL using a keyboard that can be connected to the board using an USB hub and browse the web.

Limitations

 * IP settings in the WLAN GUI (wpa_gui) once set to static IP cannot be reverted back to DHCP even if DHCP is selected.


 * Resolution of the screen is less so the user has to make the GUI windows in the WLAN GUI (wpa_gui) smaller in order to see the entire window.


 * The GUI doesn’t have ‘PSK key’ for WEP. The WEP keys cannot be entered by the user due to the limitation stated in the previous point (screen resolution).

 return to Menu
 * Cannot browse JPG images and video files

Demo errata
This section lists the known issues with the current Demo release  return to Menu

HOME