Redpine Signals RS9113 User manual
Redpine Signals, Inc. Proprietary and Confidential
RS9113-n-Link-Module-Driver-
Installation-Guide
V
Ve
er
rs
si
io
on
n
3
3.
.0
0
October 014
Redpine Signals, Inc
.
2107 N. First Street, #6 0
San Jose, CA 95131.
Tel: (40 ) 74 -33 5
Fax: (40 ) 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-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
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 © 2009 Redpine Signals, Inc. All rights reserved.
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 3
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
Table Of Contents
1 Introduction ........................................................................ 5
1.1 Definitions, Acronyms and Abbreviations ............................. 5
Onebox Driver – Setup Requirements .................................. 6
.1 Hardware Requirements ....................................................... 6
. Software Requirements ........................................................ 6
.3 Extraction of the driver package ........................................... 6
3 Compilation Procedure on various platforms ....................... 8
4 Software Boot loader Flashing ........................................... 11
5 Software Boot Loader Upgradation .................................... 13
6 OneBox-Mobile™ in WiFi only mode ................................... 14
6.1 Loading SDIO stack modules (applicable only if SDIO
interface is selected by user) ........................................................ 14
6. Installation procedure in Client mode ................................. 14
6.3 Printing supplicant scan results .......................................... 17
6.4 Deep sleep: ......................................................................... 17
6.5 Connecting to Hidden AP .................................................... 17
6.6 Installation procedure in AccessPoint mode ....................... 18
6.7 Installation procedure in WiFi-Direct mode ........................ 0
6.7.1 Autonomous GO mode: ..................................................... 1
7 OneBox-Mobile™ Coexistence Driver in WiFi + BT Classic
mode ......................................................................................
7.1 Note: The initialization procedure mentioned below will be
applicable to both USB and SDIO interfaces.Loading SDIO stack
modules (applicable only if SDIO interface is selected by user) ....
7. Installation procedure ........................................................
8 Installation and usage of Bluetooth manager .................... 4
9 OneBox-Mobile™ Coexistence Driver in WiFi +BLE mode ... 7
9.1 Note: The initialization procedure mentioned below will be
applicable to both USB and SDIO interfaces.Loading SDIO stack
modules (applicable only if SDIO interface is selected by user) .... 7
9. Installation procedure ........................................................ 7
9.3 Advertise Mode: .................................................................. 8
9.4 Scanning Mode: .................................................................. 8
9.5 Master Mode Connected State: ............................................ 8
9.6 Slave Mode Connected State: .............................................. 8
10 OneBox-Mobile™ Coexistence Driver in WiFi+Zigbee Mode
30
10.1 Driver Installation Procedure.............................................. 30
10. Building and running the sample HA switch application ...... 30
1.
About sample application .................................................................. 30
2.
Host API folder structure ................................................................... 30
3.
Application state machine .................................................................. 31
4.
Stack callbacks ................................................................................ 31
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 4
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
5.
Building and running the HA sample switch application ......................... 32
11 Driver Un-installation Procedure ..................................... 33
1 Driver Information .......................................................... 34
1 .1 Driver statistics: ................................................................. 34
1 . Disabling prints in the driver .............................................. 34
13 Starting DHCP Server/Client ........................................... 35
14 Appendix: ........................................................................ 36
14.1 Iperf cross compilation: ...................................................... 36
14. Configuration of kernels from 3.13 to 3.16 to support the
Driver ………………………………………………………………………………….37
15 BT Porting for Android:.................................................... 39
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 5
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
1 Introduction
This document describes how to bring up the Redpine’s OneBox-Mobile
Coexistence software based on RS9113 chipset on x 6 or any embedded
platform. OneBox-Mobile Coexistence software currently supports WiFi
mode which has Access Point, Client and WiFi-Direct (P2P) modes and
Bluetooth Classic, Bluetooth Low Energy and Zigbee modes. OneBox-
Mobile Coexistence software supports the following combinations.
1) WiFi only mode
2) WiFi + Bluetooth Classic mode
3) WiFi + Bluetooth Low Energy mode
4) WiFi + Zigbee mode
Coexistence mode can be used with WiFi operating in Client mode only.
1.1 Definitions, Acronyms and Abbreviations
The following terms and definitions are used in the document.
a) WiFi Mode: WiFi mode refers to the WLAN Protocol based on
IEEE 02.11 standard. Whenever driver runs in WiFi Mode, it
supports one of the Access Point, Client and WiFi-Direct modes.
b) BT Classic Mode: BT Classic mode refers to the Core Bluetooth
BR/EDR Protocol defined by the trade organization Bluetooth SIG.
c) BLE Mode: BLE mode refers to the Core Bluetooth Low Energy
Protocol defined by the trade organization Bluetooth SIG.
d) Zigbee Mode: Zigbee mode refers to the ZigBee Protocol based
on the IEEE 02.15 standard.
e) Coexistence(Coex) Mode: Coexistence mode refers to the
simultaneous functioning of driver in both WiFi Client mode and
Zigbee mode (or) WiFi client mode and BT (Classic or LE modes).
Driver enters into Coexistence mode whenever both protocol
modules are inserted.
f) End-to-End Mode: End-to-End mode refers to the default driver
mode where Driver operates in WiFi or Zigbee or Coex mode.
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 6
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
Onebox Driver – Setup Requirements
This section describes the hardware and software environment for the installation
and operation of the Redpine’s Onebox-Mobile Driver.
The following configuration is required to install and use the Onebox-Mobile
device on Linux platform.
.1 Hardware Requirements
•RS9113 SDIO/USB module
•Laptop/PC with SDIO interface, usb support
•Note : In case if the Laptop doesn’t have a built in MMC /SDIO interface
we can use a Ricoh card for accessing the SDHC/SD/MMC via PCI card-
bus interface. Refer to the following link below for more information on
the Ricoh cards. http://www.hwtools.net/cardreader/SDCBA_C01.html
. Software Requirements
•Linux 2.6.35 and above kernel version with open source SDIO stack patch
applied.
•DHCP server
•Iperf
•Bluetooth Manager Application
•Compatible Bluetooth Host stack(Bluez stack)
•
For higher kernel versions, i.e 3.13 and above , refer to the section Configuration
of kernels from 3.13 to 3.16 to support the Driver in the Appendix to ensure
correct kernel configuration.
.3 Extraction of the driver package
The driver tarball is copied into a new folder and untar it using the following
commands
#mkdir redpine
# cp <package_name.tgz> redpine/
Note: The example showed here is a generic release package for Linux
OS. The package name may get changed accordingly based on the
customer releases.
For eg:
cp RS9113.NXX.NL.GEN.LNX.x.x.x.tgz redpine/
Contents of the release package are
1) Readme
2) Release Notes
3) Documents
Note
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 7
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
4) Source (Optional)
5) Binary_files(Optional)
# cd redpine
# tar xzvf package name.tgz
If Driver binaries are provided then follow the below procedure.
# mkdir –p /home/rsi
# cp Binary_files/release.tgz /home/rsi
# cd /home/rsi
# tar xzvf release.tgz
Final driver binaries (*.ko) can be found in the /home/rsi/release.
If source is provided then follow the below procedure:
# cd Source
Untar the driver source using the following command
# tar xzvf host.tgz
#cd host
Follow the compilation procedure mentioned in Compilation
Procedure on various platforms. Note that the compiled binaries
will be finally copied in to the “/home/rsi/release” directory
-
-
Redpine Signals, Inc. Proprietary and Confidential Page
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
3Compilation Procedure on various platforms
Using menuconfig utility we can select or deselect features while
compiling the driver. The following are the menuconfig options:
•Interface on which the driver has to run, For eg : SDIO or USB.
•Regulatory Domain (US, Europe, Japan and rest of the world)
•Encap in FW
•Decap in FW
•Loading instructions from TA, disable it from host
•Programming BBP values from TA
•Programming SCAN values from TA
•Enable/Disable Aggregation Support
•Enable/Disable Debugging Support
•Enable/Disable Chip Enabled
•Enable/Disable AutoRate Support
•Enable/Disable EEPROM Read
•Enable/Disable RSI_SDIO MultiBlock Support
•Enable/Disable Security Support
•Enable/Disable Peer to Peer Support
•Enable/Disable AMPDU Age
The Menuconfig utility will start automatically when user
issues a “make” command in the driver source.
Note: User has to select the Interface to support (SDIO/
USB)in the menuconfig file.
In case of embedded platform the following changes are to
be made in the Makefile.
# cd host
# vim Makefile
EDIT the DEF_KERNEL_DIR path in the Makefile as shown below.
# DEF_KERNEL_DIR := (Platform Compiled Kernel path)
For example: If the kernel build path is in /work/redpine folder, then the
DEF_KERNEL_DIR should be modified as
# DEF_KERNEL_DIR:= /work/redpine/linux-x.x.x.
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 9
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
After editing the above changes issue make command followed by
the cross compilation options and the target platform on which the
binaries has to be built.
For example , if the target platform is ARM and tool chain path is
“/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-
linux-gnueabi/bin/arm-none-linux-gnueabi-“ then the command is
issued as
# make ARCH=arm CROSS_COMPILE =
/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-
linux-gnueabi/bin/arm-none-linux-gnueabi-
Please check the below snapshots for reference.
Figure 1: Menuconfig Utility Main page
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 10
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
Figure 2: Selecting the interface type to test the driver
Figure 3: Save the changes before exiting
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 11
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
4Software Boot loader Flashing
•For the driver versions 1.0.1e and above, software boot loader is
required for driver to work. On RS9113 cards with out Software
boot loader, MBR and Software boot loader need to be flashed
onto the card.
•Ensure that proper RS9113_WC_BL_with_mbr.rps file is present in
the /home/rsi/release/firmware folder.
•Ensure the following DIP switch settings are enabled while
mbr_flash.sh script is to be ran.
• Set the DIP switch settings to 010100 in case of USB interface.
(For a quick reference of Jumper and DIP switch settings, refer to
the below pictures for SDIO and USB interfaces)
•Run " sh mbr_flash.sh " script present in the /home/rsi/release.
•Wait for the debug message “FIRMWARE UPGRADED TO FLASH
SUCCESSFULLY” in dmesg logs.
•Remove the driver modules by executing "sh remove_all.sh"
script. (Make sure that the driver modules are removed by issuing
'lsmod')
• Poweroff the EVB and change the DIP switch settings to 000110
on the usb board
•In case of sdio interface the dip switch has to be 010000 and after
flashing bootloader it has to be changed to 000000. (Below
picture refers to the SDIO interface supported board with Boot
loader disabled)
•Now power on the EVB and start the required coex mode or wifi
only mode. For eg : If station mode has to be started in wifi only
mode refer to section OneBox-Mobile™ in WiFi only mode.
Similarly for other protocol modes follow the steps mentioned in
the subsequent sections.
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 12
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
SDIO DIP switch settings before flashing Boot loader
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 13
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
5Software Boot Loader Upgradation
To upgrade an existing software bootloader present on the card, follow the
procedure mentioned below:
•Ensure that proper RS9113_WC_BL.rps file is present in the
/home/rsi/release/firmware folder before running the script.
•Run sbl_upgrade.sh script present in /home/rsi/release/ folder.
#sh sbl_upgrade.sh
•On successful upgradation, you can see the print “SWBL
FLASHING THROUGH SWBL PASSED…” in dmesg.
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 14
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
6OneBox-Mobile™ in WiFi only mode
Common HAL Modules should be loaded to operate the driver in WiFi
mode or Coex mode. This section describes WiFi alone installation and
setup procedure. Coex modes like WiFi +Zigbee and WiFi + BT usage is
covered in subsequent sections
1. Ensure that common_insert.sh present in /home/rsi/release folder
has valid driver mode and coexistence mode to run in End-to-End
mode.
1. DRIVER_MODE=1 (END-TO-END Mode)
2. COEX_MODE=1 (WIFI alone).
Note: The initialization procedure mentioned below will be applicable to
both USB and SDIO interfaces.
If the checksum of the firmware burned in flash and the
firmware(RS9113_WLAN_QSPI.rps) present in the
/home/rsi/release/firmware folder of the driver package doesn’t match,
software bootloader upgrades the image automatically.
6.1 Loading SDIO stack modules (applicable only if SDIO
interface is selected by user)
In case if user needs to use the Onebox-Mobile driver with SDIO
interface, make sure the SDIO stack related modules are already inserted
in the kernel. To check this use the following command
# lsmod
Make sure the stack modules “sdhci.ko, sdhci_pci.ko, mmc_block.ko,
mmc_core.ko” are present. If these modules are not inserted use the
following script to insert them into the kernel.
# cd /home/rsi/release
# sh load_stack.sh
Note that this is one time process and need not insert for every driver
initialization unless the modules are explicitly removed by the user.
6. Installation procedure in Client mode
Use the start_sta.sh script in the release folder to start the device in
station mode. Before running the script User needs to enable the
appropriate network block settings with the information about the
Accesspoint to connect with.
The scripts mentioned here are present in /home/rsi/release path.
Note
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 15
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
To configure the station in Open mode enable the below
configuration settings in the sta_settings.conf file.
network={
ssid=“ SSID of the AP to connect with”
key_mgmt=NONE
}
•To configure the station in WEP-64 mode enable the below
configuration settings in the sta_settings.conf file.
network={
ssid=“ SSID of the AP to connect with”
wep_key0=XXXXXXXXXX
wep_tx_keyidx=X
key_mgmt=NONE
}
Note: In case of wep64 the key representation can be specified
in ASCII/ Hex.
For example
Hex format: wep_key0=1234567 90
Ascii format: wep_key0=”12345”
•To configure the station in WEP-12 mode enable the below
configuration settings in the sta_settings.conf file.
network ={
ssid=“ SSID of the AP to connect with”
wep_key0= XXXXXXXXXXXXXXXXXXXXXXXXXX
wep_tx_keyidx=X
key_mgmt=NONE
}
Note: In case of wep12 the key representation can be
specified in ASCII/ Hex.
For example
Hex format: I
wep_key0=1234567 901234567 90123456
Ascii format: wep_key0=”1234567 90123”
•To configure the station in WEP-Shared (64-bit) mode use the
following configuration settings in the sta_settings.conf file
network ={
ssid=“ SSID of the AP to connect with”
wep_key0= “abcde”
wep_tx_keyidx= 0
key_mgmt=NONE
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 16
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
auth_alg=SHARED
priority=2
}
Note: In case of wep64 –shared the key representation can be
specified in ASCII/ Hex.
For example
Hex format: wep_key0=1234567 90
Ascii format: wep_key0=”12345”
In the above example the key index is specified as zero.
Similarly for WEP-12 mode the key representation would be
Hex format: wep_key0=1234567 901234567 90123456
Ascii format: wep_key0 = “1234567 90123”
Key index can vary from 0 to 3.
•To configure the station in TKIP mode enable the below
configuration settings in the sta_settings.conf file
network ={
ssid=“ SSID of the AP to connect with”
key_mgmt=WPA-PSK
psk= Passphrase specified at AP side
proto=WPA
pairwise=TKIP
group=TKIP
}
•To configure the station in CCMP mode enable the below
configuration settings in the sta_settings.conf file
network={
ssid=“ SSID of the AP to connect with”
key_mgmt=WPA-PSK
psk=Passphrase specified at AP side
proto=WPA2
pairwise=CCMP
group=CCMP
}
Run the following script to load the driver modules followed by starting
the supplicant..
•cd /home/rsi/release
•sh start_sta.sh
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 17
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
After issuing the above command virtual interface with the interface
name “wifi0” will be created. User can view the list of interfaces using
the following command
ifconfig -a
User can create their own custom virtual interface name. In the
above example “wifi0” is used.
6.3 Printing supplicant scan results
To view the supplicant scan results user has to use the following
command at the /home/rsi/release path.
$ cd /home/rsi/release
$ ./wpa_cli –i wifi0 scan_results.
The above command shows the list of access points scanned in each
channel.
To check if the device has connected to an accesspoint use the following
command.
$ iwconfig wifi0
This command gives the status of the device. If it is in connected state
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 in the output of iwconfig..
6.4 Deep sleep:
If we enable deep sleep, the hardware components (RF, BBP and LMAC)
will be turned off and the TA will be switched to host clock.
After the completion of device initialization, the device will go into deep
sleep after receiving a Deep sleep request frame from the host. The
device will come out of sleep after creating a virtual interface in the Host.
This wakeup indication is given to firmware via writing a value in to the
SDIO_WAKEUP_REGISTER(0x000FF). Once the device comes out of sleep
hardware initialization of RF, BBP, LMAC and supporting components will
be done by the TA.
Testing procedure: Deep sleep feature can be tested by measuring
power consumption with/without Deep sleep.
Note: Currently not supporting this feature.
6.5 Connecting to Hidden AP
To connect to hidden AP, enable the below configuration in
sta_settings.conf
network={
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 1
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
ssid=“$Hidden_AP_SSIDNAME”
scan_ssid =1
key_mgmt=NONE
}
With this command, the driver sends the directed probe request to that
particular AP.
6.6 Installation procedure in AccessPoint mode
In case if SDIO interface is used make sure sdio stack modules are
loaded, refer Loading sdio stack modules above before starting the AP
mode
1. User needs to enable the appropriate network block settings with the
information about the Access point configuration.
2. To configure the Access Point in different security modes use the
following configuration file settings. The configuration files for different
security modes as well as open mode can be found in the release
folder.
3. Use the start_ap.sh script in the home/rsi/release folder with the
required configuration file as input to start_ap.sh to start driver in
Access Point mode.
$ cd /home/rsi/
$ sh start_ap.sh $conf_file
$conf_file - Depending on the security mode user can input the
configuration file accordingly.
a) To start the Access point in Open mode use the following
command.
$ sh start_ap.sh wpa_supplicant_open.conf
• The Access point is configured with the following
default parameters after the above command is
executed
1) SSID of the AP = “REDPINE_AP”
2) Frequency (2.4 GHz) – 2412
3) Open mode security
b) To start the Access point in WEP-64 security mode use the following
command
$ sh start_ap.sh wpa_supplicant_wep64.conf
• The Access point is configured with the following settings
1
) SSID of the AP = “onebox_wep”
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 19
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
-
-
2) Frequency (2.4 GHz) – 2412
3) Security mode – WEP-64
4) WEP key is “1234567 90”
5) Key index is “0”
c) To start the Access point in WEP-12 security use the following
command
$ sh start_ap.sh wpa_supplicant_wep12 .conf
• The Access point is configured with the following settings
1) SSID of the AP = “onebox_wep”
2) Frequency (2.4 GHz) – 2412
3) Security mode – WEP-12
4) WEP key is “1234567 901234567 90123456”
5) Key index is “0”
d) To start the Access point in TKIP(WPA-PSK) security mode use the
following command
$ sh start_ap.sh wpa_supplicant_tkip.conf
• The Access point is configured with the following settings
1. SSID of the AP = “onebox_tkip”
2. Frequency (2.4 GHz) – 2412
3. Security mode = TKIP
4. Pass phrase = “1234567 ”
e) To start the Access point in CCMP(WPA-PSK) security mode use
the following command
$ sh start_ap.sh wpa_supplicant_ccmp.conf
• The Access point is configured with the following settings
1. SSID of the AP = “onebox_ccmp”
2. Frequency (2.4 GHz) – 2412
3. Security mode = CCMP
4. Pass phrase = “1234567 ”
-
-
Redpine Signals, Inc. Proprietary and Confidential Page 20
R
RS
S9
91
11
13
3-
-n
n-
-L
Li
in
nk
k-
-M
Mo
od
du
ul
le
e-
-D
Dr
ri
iv
ve
er
r-
-I
In
ns
st
ta
al
ll
la
at
ti
io
on
n-
-G
Gu
ui
id
de
e
V
V
e
e
r
r
s
s
i
i
o
o
n
n
3
3
.
.
0
0
User has the option to modify the configuration inputs shown
in the above configuration files . All the SSID names,
passphrases shown in the configuration files are for sample
reference. Access Point doesn’t support WEP-Shared algorithm in
the present release.
To check if the device has started in access point mode, use the following
command.
$ iwconfig wifi0
This command gives the status of the device. It displays the Access point
SSID along with the mac address and frequency. If Access point doesn’t
start properly, message saying “Exiting: Driver Initialization not
completed even after waiting for xxms” is displayed.
6.7 Installation procedure in WiFi-Direct mode
In case if SDIO interface is used make sure sdio stack modules are
loaded, refer Loading sdio stack modules above before starting the WiFi-
Direct mode.
Ensure that common_insert.sh has valid driver mode and coexistence
mode to run in End-to-End mode.
DRIVER_MODE=1 (END-TO-END Mode)
COEX_MODE=1 (WIFI only mode)
The following steps are to be followed to start the device in WiFi Direct mode.
1. sh start_p2p.sh
The above command starts the device in p2p mode. After starting the
supplicant the p2p_commands mentioned in the below section should be
executed.
Note
Other manuals for RS9113
1
Table of contents
Other Redpine Signals Wireless Module manuals
