Redpine Signals, Inc. Proprietary and Confidential
Page 16
R
R
S
S
9
9
1
1
1
1
3
3
M
M
o
o
d
d
u
u
l
l
e
e
E
E
v
v
a
a
l
l
u
u
a
a
t
t
i
i
o
o
n
n
K
K
i
i
t
t
U
U
s
s
e
e
r
r
G
G
u
u
i
i
d
d
e
e
V
V
e
e
r
r
s
s
i
i
o
o
n
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={