Reference Manual

Redpine Signals, Inc. Proprietary and Confidential Page 30
RS9116 n-Link Linux and Android
Technical Reference Manual
Version 2.0
P2P Devices can scan this Group Owner and can connect directly. Run following command to start receiving connect
calls from P2P devices
#. /wpa_cli i wifi0
- > wps_pbc
You will start getting ENROLEE detect calls from other P2P Devices in the vicinity. You can see the running logs on wpa_cli
prompt for the device getting connected.
Legacy Wi-Fi clients (non P2P clients) need a passphrase to connect to the p2p group. The command given below
generates the passphrase for legacy Wi-Fi clients.
#. /wpa_cli i wifi0 p2p_get_passphrase
Run DHCP Server on GO Interface before connecting P2P or Legacy devices.
4.5 OneBox-Mobile in Wi-Fi + Bluetooth Classic Coexistence Mode
This section explains about the installation of Wi-Fi and BT Classic modes. Please note that in case of using Coexistence
mode, each protocol should be loaded individually one after the other.
Open the common_insert.sh file present in the "release" folder.
Ensure that the DRIVER_MODE and COEX_MODE are set as below:
- DRIVER_MODE = 1
- COEX_MODE = 5(For WLAN Station and BT Classic Mode)
- COEX_MODE = 6 (For WLAN Access Point and BT Classic Mode)
For SDIO mode, ensure that the SDIO stack related modules are already inserted in the kernel refer Appendix A:
Configuration of Kernels from 3.13 and above section to install sdio stack modules .
1. Follow the instructions mentioned in the section 4.4.1 Installation in Wi-Fi Client Mode inorder to install the Wi-Fi
Client mode.
2. Run the "bt_enable.sh" or wlan_bt_insert.sh or onebox_insert.sh script present in the "release" folder as per the
instructions given in the Installing the Driver in order to start the Bluetooth Classic mode. This script inserts Bluetooth
modules and common HAL modules, provided if it is not already inserted.
3. You can check whether the BT Classic mode has been started successfully or not, by running the following command:
If the driver is loaded correctly, the above command displays a network adaptor named "hciX". An example output is
given below:
4. After the device is up, we can pair it with the other devices using the Bluetooth Manager application. The files can also
be sent and received using Bluetooth Manager. Instead of Bluetooth Manager, the device can be configured using
"hcitool" or "hciconfig". The procedure for using Bluetooth Manager is explained in the section Appendix C: Using the
Bluetooth Manager