Redpine Signals RS9113 EVB User manual
Redpine Signals, Inc. Proprietary and Confidential
RS9113 Module Evaluation Kit
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
January 2015
Redpine Signals, Inc.
2107 N. First Street, #680
San Jose, CA 95131.
Tel: (408) 748-3385
Fax: (408) 705-2019
Email: info@redpinesignals.com
Website: www.redpinesignals.com
Redpine Signals, Inc. Proprietary and Confidential Page 2
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
Disclaimer:
The information in this document pertains to information related to Redpine Signals,
Inc. products. This information is provided as a service to our customers, and may
be used for information purposes only.
Redpine assumes no liabilities or responsibilities for errors or omissions in this
document. This document may be changed at any time at Redpine’s sole discretion
without any prior notice to anyone. Redpine is not committed to updating this
document in the future.
Copyright © 2015 Redpine Signals, Inc. All rights reserved.
Redpine Signals, Inc. Proprietary and Confidential Page 3
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
About this Document
This document covers the RS9113 Module’s Evaluation Board (EVB) and its usage for
evaluating Redpine Signals’ RS9113 based ultra-low-power, single spatial stream,
dual-band 802.11n + BT4.0 + ZigBee Convergence modules in n-Link® and
WiSeConnect® modes.
Redpine Signals, Inc. Proprietary and Confidential Page 4
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
Table Of Contents
1Overview ............................................................................. 9
2Evaluation Kit Contents ..................................................... 10
3Hardware Details ............................................................... 12
4Evaluation of n-Link® ........................................................ 14
4.1 Required Setup ................................................................... 14
4.2 Getting Started ................................................................... 14
4.3 OneBox-Mobile in Wi-Fi Only Mode ..................................... 16
4.3.1 Installation in Wi-Fi Client Mode ...................................................... 16
4.3.2 Installation in Access Point Mode ..................................................... 18
4.3.3 Installation in Wi-Fi Direct Mode ...................................................... 20
4.3.4 Checking Throughputs....................................................................20
4.4 OneBox-Mobile in Wi-Fi + Bluetooth Classic Coexistence
Mode 21
4.5 OneBox-Mobile in Wi-Fi + Bluetooth LE Coexistence Mode . 22
4.6 OneBox-Mobile in Wi-Fi + Zigbee Coexistence Mode........... 23
4.6.1 Building and Running the Sample Home Automation Switch Application 24
4.6.1.1 About the Sample Application .................................................... 24
4.6.1.2 Host API Folder Structure.......................................................... 24
4.6.1.3 Application State Machine ......................................................... 24
4.6.1.4 State Callbacks........................................................................ 25
4.6.1.5 Building and Running the Home Automation Sample Application ....25
4.7 Driver Uninstallation Procedure.......................................... 25
4.8 Driver Information.............................................................. 26
4.8.1 Driver Statistics............................................................................. 26
4.8.2 Disabling Driver Debug Prints.......................................................... 26
5Evaluation of Connect-io-n®/WiSeConnect®..................... 27
5.1 Required Setup ................................................................... 27
5.2 Getting Started ................................................................... 27
5.3 Wi-Fi Evaluation in UART Mode ........................................... 29
5.3.1 Wi-Fi Client in Personal Security Mode.............................................. 29
5.3.1.1 Wi-Fi Client Configuration ......................................................... 29
5.3.1.2 Test Procedure ........................................................................32
5.3.2 Wi-Fi Client in Enterprise Security Mode ........................................... 34
5.3.2.1 Radius Server Configuration ...................................................... 35
5.3.2.2 Access Point Configuration ........................................................ 39
5.3.2.3 Wi-Fi Client Configuration ......................................................... 40
5.3.2.4 Test Procedure ........................................................................43
5.3.3 Wi-Fi Direct Mode ..........................................................................45
5.3.3.1 Wi-Fi Configuration .................................................................. 45
5.3.3.2 Test Procedure ........................................................................49
5.3.4 Wi-Fi Access Point Mode ................................................................. 49
5.3.4.1 Access Point Configuration Through AT Commands ...................... 50
5.3.4.2 Test Procedure ........................................................................51
5.4 Configuration Over Wi-Fi .................................................... 52
5.4.1 Configuration to Connect to an Access Point......................................52
5.4.2 Configuration to Create an Access Point ........................................... 58
Redpine Signals, Inc. Proprietary and Confidential Page 5
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
6Appendix A: Headers on the EVB ....................................... 64
6.1 Headers’ Pin Orientations ................................................... 64
6.2 SPI Header Pin Description................................................. 64
6.3 SDIO Header Pin Description .............................................. 65
6.4 GPIO Header Pin Description .............................................. 65
7Appendix B: Using the Bluetooth Manager ......................... 67
8Appendix C: WiSeConnect® Firmware Upgrade ................. 70
9Appendix D: Booting USB Drive on Windows 8 and Later PCs
75
Redpine Signals, Inc. Proprietary and Confidential Page 6
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
Table of Figures
Figure 1: Evaluation Kit Contents ............................................................... 10
Figure 2: RS9113 EVB ................................................................................ 12
Figure 3: Host SPI Folder Structure............................................................ 24
Figure 4: Docklight Startup Dialog Box....................................................... 28
Figure 5: Docklight Project Settings Dialog Box ......................................... 28
Figure 6: Setup for Wi-Fi Client in Personal Security Mode......................... 29
Figure 7: Module Startup Messages............................................................ 30
Figure 8: Firmware Loading Messages ....................................................... 31
Figure 9: TCP Application Window.............................................................. 34
Figure 10: Setup for Wi-Fi Client in Enterprise Security Mode .................... 34
Figure 11: Default EAP Type ....................................................................... 36
Figure 12: TLS Section - I........................................................................... 37
Figure 13: TLS Section –II......................................................................... 37
Figure 14: TTLS Section.............................................................................. 38
Figure 15: User Addition ............................................................................ 39
Figure 16: Wireless Security Configuration of Access Point........................ 40
Figure 17: Module Startup Messages.......................................................... 41
Figure 18: Firmware Loading Messages ..................................................... 41
Figure 19: Android Phone’s Wi-Fi Direct Settings ....................................... 45
Figure 20: Command Flow in Wi-Fi Direct Mode ......................................... 48
Figure 21: Module Configured as Access Point ........................................... 52
Figure 22: Module web page ...................................................................... 53
Figure 23: Wireless Configuration page ..................................................... 55
Figure 24: Module Connected to Access Point ............................................ 56
Figure 25: Wireless Configuration Page ..................................................... 57
Figure 26: Module Configured as Access Point ........................................... 58
Figure 27: Module web page ...................................................................... 59
Figure 28: Wireless Configuration page ..................................................... 60
Figure 29: Module Connected to Access Point ............................................ 61
Figure 30: Wireless Configuration page ..................................................... 62
Figure 31: Headers’ Pin Orientations.......................................................... 64
Figure 32: Invoking Bluetooth Manager ..................................................... 67
Figure 33: Bluetooth Manager basic window .............................................. 68
Figure 34: Click on Search to inquire.......................................................... 68
Figure 35: Pairing with a Device................................................................. 69
Figure 36: Send a File to a Device .............................................................. 69
Figure 37: Terminal Settings for Teraterm ................................................. 71
Figure 38: Serial Port Settings for Teraterm............................................... 71
Figure 39: Module Startup Messages .......................................................... 72
Figure 40: Request for Firmware File ......................................................... 73
Figure 41: Firmware Transfer Progress ...................................................... 74
Figure 42: BIOS Setup Screen .................................................................... 75
Figure 43: Security Screen of BIOS ............................................................ 76
Figure 44: Disable “Secure Boot” ............................................................... 76
Figure 45: Advanced Screen of BIOS .......................................................... 77
Figure 46: System Configuration under Advanced...................................... 77
Figure 47: System Configuration ................................................................ 78
Figure 48: Disable UEFI Boot...................................................................... 78
Redpine Signals, Inc. Proprietary and Confidential Page 7
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
Redpine Signals, Inc. Proprietary and Confidential Page 8
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
Table of Tables
Table 1: SPI Header Pins ............................................................................ 64
Table 2: SDIO Header Pins ......................................................................... 65
Table 3: GPIO Header Pins ......................................................................... 66
Redpine Signals, Inc. Proprietary and Confidential Page 9
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
1Overview
The RS9113 Module Evaluation Kit (EVK) is a platform for evaluating the
RS9113 modules with multiple Host Processors/MCUs over interfaces like
SDIO, USB, USB-CDC, SPI and UART. The EVK includes sample driver,
supplicant, applications to test the following:
1) Wireless Functionality for Wi-Fi, BT 4.0 and Zigbee
2) Security modes
3) Throughputs
4) Power Consumption
5) Firmware Upgrade
The RS9113 n-Link®, WiSeConnect® module families are based on
Redpine Signals' RS9113 ultra-low-power, single spatial stream, dual-
band 802.11n + BT4.0 + ZigBee Convergence SoC. The RS9113 module
integrates a multi-threaded MAC processor with integrated analog
peripherals and support for digital peripherals, baseband digital signal
processor, analog front-end, crystal oscillator, calibration OTP memory,
dual-band RF transceiver, dual-band high-power amplifiers, baluns,
diplexers, diversity switch and Quad-SPI Flash thus providing a fully-
integrated solution for embedded wireless applications.
Redpine Signals, Inc. Proprietary and Confidential Page 10
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
2Evaluation Kit Contents
The RS9113 Module Evaluation Kit comes with the following components:
1) RS9113 Module Evaluation Board
2) USB Pen drive
3) USB-to-microUSB Cable
4) SDIO Adaptor Cable
5) SPI Adaptor Cable
Figure 1: Evaluation Kit Contents
The USB drive is bootable. It is loaded with Fedora Core 18 OS with the
OneBox-Mobile driver binaries included for evaluation of n-Link® modules
on a standard PC/Laptop platform.
The USB drive also has the release package for the Connect-io-
n®/WiSeConnect® modules which includes the firmware, documentation
and reference projects for multiple platforms.
Redpine Signals, Inc. Proprietary and Confidential Page 11
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
Redpine provides drivers for multiple OS’s and MCU platforms for the n-
Link® modules and also OS-less MCU platforms for WiSeConnect®
modules. The software provided in this kit is to enable easy and quick
evaluation on a PC. Please contact Redpine Signals’ Sales
(sales@redpinesignals.com) for availability of drivers for an OS and MCU
of your choice.
Redpine Signals, Inc. Proprietary and Confidential Page 12
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
3Hardware Details
This section describes the RS9113 EVB’s various components and
headers.
The OneBox-Mobile software for the n-Link® modules supports SDIO and
USB interfaces to connect to the Host MCU. The OneBox-Embedded
software for the WiSeConnect® modules supports UART, SPI, USB and
USB-CDC interfaces to connect to the Host MCU.
As shown in the image below, the RS9113 EVB has three USB connectors
for the USB, USB-CDC and UART connections. The UART signals of the
module are converted to USB using on-board circuit. The board also has
SDIO and SPI Headers.
Figure 2: RS9113 EVB
The board is designed to configure the module to use the interface on
which power supply is detected. This is indicated through the LEDs
mounted on the board. The SDIO and SPI interfaces require power supply
to be provided over the USB connector. Hence, for these interfaces, it is
required that the USB connection be provided first followed by the SDIO
or SPI connection.
Redpine Signals, Inc. Proprietary and Confidential Page 13
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
Follow the steps below to use the EVB with different interfaces:
1) USB, UART, USB-CDC Modes
a. Connect the USB-to-microUSB cable between a USB port of a
PC/Laptop and the micro-USB port labeled USB, UART or USB-
CDC on the EVB.
b. Verify that the LED labeled “USB”, “UART” or “USB-CDC” lights
up as per the port which is connected.
2) SDIO Mode
a. Connect the USB-to-microUSB cable between a USB port of a
PC/Laptop and the micro-USB port labeled USB on the EVB –
this connection will be used only as a power supply in this
mode.
b. Connect the 10-pin header of the SDIO Adaptor Cable to the
EVB. Insert the SDIO Adaptor into the SDIO slot of the
PC/Laptop.
c. Verify that the LED labeled “SDIO” lights up.
3) SPI Mode
a. Connect the USB-to-microUSB cable between a USB port of a
PC/Laptop and the micro-USB port labeled USB on the EVB –
this connection will be used only as a power supply in this
mode.
b. Connect the 10-pin header of the SPI Adaptor Cable to the
EVB. Connect the other wires of this connector to the SPI
signals of a Host MCU platform. The details of the Header are
given in Appendix A.
There is a 2-pin inline jumper available for measuring the current being
sourced by the module during different stages of operation. This is
labeled as “MEASURE” on the PCB. The user may connect a power meter
or an ammeter to this jumper to measure the current.
To proceed further, click on the links below as per your requirement.
1) Evaluation of n-Link® modules
2) Evaluation of WiSeConnect® modules
Redpine Signals, Inc. Proprietary and Confidential Page 14
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
4Evaluation of n-Link®
This section covers the evaluation of the n-Link® mode of the EVK using
the OneBox-Mobile drivers in the following modes:
1) Wi-Fi
a. Client
b. Access Point
c. Wi-Fi Direct
2) Wi-Fi Client and Bluetooth Classic
3) Wi-Fi Client and Bluetooth Low Energy
4) Wi-Fi Client and Zigbee
The n-Link modules support SDIO and USB as the host interfaces.
4.1 Required Setup
RS9113 EVK
PC/Laptop to program the RS9113 EVB over SDIO or USB
For evaluation of the Wi-Fi Client mode, you will require:
oWi-Fi Access Point
oA second PC/Laptop with Ethernet
For evaluation of the Wi-Fi Access Point mode, you will require:
oA second PC/Laptop with Wi-Fi
For evaluation of the Wi-Fi Direct mode, you will require:
oA device with Wi-Fi Direct capability like an Android 4.0
smartphone or a Laptop
For evaluation of the Bluetooth Classic mode, you will require a
device like a smartphone or Laptop with Bluetooth capability
For evaluation of the Zigbee mode, you will require a Zigbee
Coordinator and Zigbee-enabled Light bulb which support the
Home Automation Profile.
NOTE: The procedure explained below is common across the USB and
SDIO interfaces. Please replace “<interface>” with “USB” or “SDIO” as
per your choice.
4.2 Getting Started
Please follow the steps below to get started with the evaluation process.
1) Plug the USB drive provided in the EVK and turn on the host PC.
Interrupt the PC from booting in normal mode (default) by pressing
‘F12’ key you can see the boot menu option, from there, select the
boot device as USB storage device and click Enter.
Redpine Signals, Inc. Proprietary and Confidential Page 15
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
NOTE: If you have a Windows 8 or later PC, the booting process might
fail because of the new UEFI mode (instead of BIOS) being used in such
PCs. Disable the UEFI Boot mode (enable CSM boot mode) and Secure
Bootup mode to boot from the USB drive on such PCs. Please follow the
steps listed in Appendix D.
Once these changes are done, the original Windows 8 OS will not be
bootable till the changes are reverted.
2) You will be presented a menu with the following options:
a. Start RS9113
b. Troubleshooting
Select “Start RS9113” and click Enter.
NOTE: In some PCs the bootup might fail because of Graphics
hardware incompatibility with the Fedora Core 18 OS loaded on the
USB drive. The screen will go blank rather than showing the booting
process. In such cases, select “Troubleshooting” then attempt to boot
in the Basic Graphics Mode.
3) Wait until the booting up completes and you get the Linux screen.
4) Press “Alt+F2” and enter “gnome-terminal” in the pop-up window to
open a terminal window.
5) Enter into super user mode using the “su” command in the terminal.
Enter “redpine” as the password when prompted.
6) Follow the steps below to use the EVB with different interfaces:
a. USB Mode
i. Connect the USB-to-microUSB cable between a USB
port of a PC/Laptop and the micro-USB port labeled
USB, UART or USB-CDC on the EVB.
ii. Verify that the LED labeled “USB”, “UART” or “USB-
CDC” lights up as per the port which is connected.
b. SDIO Mode
i. Connect the USB-to-microUSB cable between a USB
port of a PC/Laptop and the micro-USB port labeled
USB on the EVB –this connection will be used only as a
power supply in this mode.
ii. Connect the 10-pin header of the SDIO Adaptor Cable
to the EVB. Insert the SDIO Adaptor into the SDIO slot
of the PC/Laptop.
iii. Verify that the LED labeled “SDIO” lights up.
7) Go to the /home/OneBox-Mobile folder and follow the instructions
listed in the sub-sections below.
8) To proceed further, click on one of the links below as per your choice.
a. OneBox-Mobile in Wi-Fi Only Mode
Redpine Signals, Inc. Proprietary and Confidential Page 16
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
b. OneBox-Mobile in Wi-Fi + Bluetooth Classic Mode
c. OneBox-Mobile in Wi-Fi + Bluetooth LE Mode
d. OneBox-Mobile in Wi-Fi + Bluetooth Zigbee Mode
4.3 OneBox-Mobile in Wi-Fi Only Mode
1) Open the common_insert.sh file present in “/home/OneBox-
Mobile/<interface>” using the gvim editor.
2) Ensure that the DRIVER_MODE and COEX_MODE as set as below
a. DRIVER_MODE = 1
b. COEX_MODE = 1
NOTE: For SDIO mode, ensure that the SDIO stack related modules are
already inserted in the kernel. Follow the steps below for this:
# cd /home/OneBox-Mobile/SDIO
# sh load_stack.sh
# lsmod
Verify that the output of the “lsmod” command lists the sdhci.ko,
sdhci_pci.ko, mmc_block.ko and mmc_core.ko modules. This is a one-
time process and need not be repeated unless the modules are explicitly
removed by the user.
4.3.1 Installation in Wi-Fi Client Mode
1) Edit the “sta_settings.conf” file in the /home/OneBox-
Mobile/<interface> folder using gvim and enter the parameters of the
Wi-Fi network as below.
a. For Open (non-Secure) mode
network={
ssid=”<SSID of Access Point>”
key_mgmt=NONE
}
b. For Open (non-Secure) mode connection to a Hidden SSID
network={
ssid=”<SSID of Access Point>”
scan_ssid=1
key_mgmt=NONE
}
c. For WEP-64 mode
network={
Redpine Signals, Inc. Proprietary and Confidential Page 17
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
ssid=”<SSID of Access Point>”
key_mgmt=NONE
wep_key0=XXXXXXXXXX
wep_tx_keyidx=X
}
The key can be input either in ASCII or Hexadecimal formats:
ASCII Format: wep_key0=”12345”
Hexadecimal Format: wep_key0=1234567890
d. For WEP-128 mode
network={
ssid=”<SSID of Access Point>”
key_mgmt=NONE
wep_key0= XXXXXXXXXXXXXXXXXXXXXXXXXX
wep_tx_keyidx=X
}
The key can be input either in ASCII or Hexadecimal formats:
ASCII Format: wep_key0=”1234567890123”
Hexadecimal Format: wep_key0=12345678901234567890123456
e. For WPA-PSK (TKIP) mode
network={
ssid=”<SSID of Access Point>”
key_mgmt=WPA-PSK
psk=<passphrase specified in the Access Point>
proto=WPA
pairwise=TKIP
group=TKIP
}
f. For WPA2-PSK (CCMP) mode
network={
ssid=”<SSID of Access Point>”
key_mgmt=WPA-PSK
psk=<passphrase specified in the Access Point>
proto=WPA2
Redpine Signals, Inc. Proprietary and Confidential Page 18
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
pairwise=CCMP
group=CCMP
}
2) Next, run the “start_sta.sh” script in the /home/OneBox-
Mobile/<interface> folder to load the driver modules and the
supplicant and connect to the Access Point specified in the
“sta_settings.conf” file.
# sh start_sta.sh
3) After issuing the above command a virtual interface with the name
“wifi0” will be created. You can view the list of interfaces using the
following command:
# ifconfig –a
4) You can check whether the connection to the Access Point is
successful by running the following command:
# iwconfig wifi0
This command gives the status of the device. If the connection is
successful, then the connected Access point SSID along with the MAC
address is displayed. If it is not connected to an Access point a
message “Not Associated” appears.
5) To view the list of Access Points scanned in each channel, you can run
the following command in the /home/OneBox-Mobile/<interface>
folder.
# ./wpa_cli –i wifi0 scan_results
6) To obtain an IP address using DHCP, start the DHCP client using the
command below.
# dhclient wifi0
4.3.2 Installation in Access Point Mode
The “start_ap.sh” script present in the /home/OneBox-Mobile/<interface>
folder needs to be run with the different configuration files provided in
the same folder to install an Access Poiint in different security modes.
# cd /home/OneBox-Mobile/<interface>
# sh start_ap.sh <conf_file>
The different configuration files (conf_file) provided are as follows:
1) Access Point in Open Mode
a. Configuration File: wpa_supplicant_open.conf
b. This starts an Access Point with the following parameters:
i. SSID: REDPINE_AP
ii. Channel 1 of 2.4GHz Band (2412 MHz)
iii. Open (non-Secure) mode
Redpine Signals, Inc. Proprietary and Confidential Page 19
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
2) Access Point in WEP-64 Mode
a. Configuration File: wpa_supplicant_wep64.conf
b. This starts an Access Point with the following parameters:
i. SSID: onebox_wep
ii. Channel 1 of 2.4GHz Band (2412 MHz)
iii. Security Mode: WEP-64
iv. WEP Key: 1234567890
v. Key Index: 0
3) Access Point in WEP-128 Mode
a. Configuration File: wpa_supplicant_wep64.conf
b. This starts an Access Point with the following parameters:
i. SSID: onebox_wep
ii. Channel 1 of 2.4GHz Band (2412 MHz)
iii. Security Mode: WEP-128
iv. WEP Key: 12345678901234567890123456
v. Key Index: 0
4) Access Point in WPA-PSK (TKIP) Mode
a. Configuration File: wpa_supplicant_tkip.conf
b. This starts an Access Point with the following parameters:
i. SSID: onebox_tkip
ii. Channel 1 of 2.4GHz Band (2412 MHz)
iii. Security Mode: WPA-PSK (TKIP)
iv. Passphrase: “12345678”
5) Access Point in WPA2-PSK (CCMP) Mode
a. Configuration File: wpa_supplicant_ccmp.conf
b. This starts an Access Point with the following parameters:
i. SSID: onebox_ccmp
ii. Channel 1 of 2.4GHz Band (2412 MHz)
iii. Security Mode: WPA2-PSK (CCMP)
iv. Passphrase: “12345678”
NOTE: All the above parameters can be modified in the respective
configuration files by the user. The values provided are only for
reference.
Redpine Signals, Inc. Proprietary and Confidential Page 20
R
RS
S9
91
11
13
3
M
Mo
od
du
ul
le
e
E
Ev
va
al
lu
ua
at
ti
io
on
n
K
Ki
it
t
U
Us
se
er
r
G
Gu
ui
id
de
e
V
Ve
er
rs
si
io
on
n
2
2.
.0
0
After running the “start_ap.sh” script a virtual interface with the name
“wifi0” will be created. You can view the list of interfaces using the
following command:
# ifconfig –a
You can check whether the Access Point has been started successfully by
running the following command:
# iwconfig wifi0
This command gives the status of the device. It displays the Access
Point’s SSID along with the MAC address and channel frequency. If the
Access Point doesn’t start, a message saying “Exiting: Driver Initialization
not completed even after waiting for xxms” is displayed.
To start a DHCP server, use the commands below.
# sh dhcp_server.sh
# dhcpd wifi0 start
4.3.3 Installation in Wi-Fi Direct Mode
The “start_p2p.sh” script present in the /home/OneBox-
Mobile/<interface> folder needs to be run to start the supplicant and
install the Wi-Fi Direct mode. The configurable parameters in the
p2p.conf file are the listen channel, operating channel and GO Intent.
After starting the supplicant the p2p_commands mentioned below should
be executed.
1) To find other P2P networks
# ./wpa_cli –i wifi0 p2p_find
2) To find other P2P devices in range
# ./wpa_cli –i wifi0 p2p_peers
3) To connect to a P2P network
# ./wpa_cli –i wifi0 p2p_connect <BSS ID> pbc
go_intent=<intent value>
4.3.4 Checking Throughputs
You can check the Transmit and Receive throughputs in UDP and TCP
modes by using the iperf application. If you wish to evaluate the
throughputs in Wi-Fi Client mode, you will need to connect a second
PC/Laptop to the Access Point. Download and install the iperf application
from https://iperf.fr/ on the second PC/Laptop.
Please note the following points for this evaluation:
1) To evaluate the module for throughput performance, it’s
recommended that you connect the second PC/Laptop to the Access
Point over Ethernet.
2) It is recommended that you choose a Wi-Fi channel which has less
interference, preferably in the 5GHz band if the EVK is for a Dual band
module, to observe optimal throughputs of the module.
Table of contents
Other Redpine Signals Motherboard manuals
