Reference Manual
Table Of Contents
- Introduction to RS9116
- Getting Started with RS9116
- Compiling the Driver
- Installing the Driver
- Installation of Modules
- Enabling a Protocol
- Disabling a Protocol
- OneBox-Mobile in Wi-Fi Only Mode
- Installation in Wi-Fi Client Mode (with BSD interface support)
- Installation in Access Point Mode (with BSD interface support)
- Installation in Wi-Fi Client Mode (with NL80211 support)
- Installation in Wi-Fi AP mode (with NL80211 support)
- Installation in Wi-Fi Direct Mode (With BSD Interface Support)
- Installation in Wi-Fi Direct Mode (With NL80211 Support only for Kernel v3.8 or higher)
- OneBox-Mobile in Wi-Fi + Bluetooth LE Coexistence Mode
- Driver Information
- Wi-Fi ioctl Usage Guide
- Configuration Using CFG80211
- Enterprise security using CFG80211
- HOSTAPD and Wi-Fi Protected Setup (WPS)
- ACS with Hostapd
- Antenna Diversity
- Sniffer Mode
- Monitor Mode
- Concurrent Mode
- Background Scan Parameters
- Power save Modes, Profiles and Parameters
- Compliance and Certification
- Wi-Fi Performance Test ioctl usage
- Wake-On-Wireless LAN
- PUF [ Physical Unclonable Functions ]
- GTK Offload
- Steps to connect 802.11R client to AP
- Steps to configure 802.11W
- Update WLAN region based maximum powers from driver
- Bluetooth hcitool and hciconfig Usage
- Android support for RS9116
- Appendix A: Configuration of Kernels from 3.13 and above
- Appendix B: Binary Files for Embedded Platforms
- Appendix C: Using the Bluetooth Manager
- Appendix D: Common Configuration Parameters
- Appendix E: Installation of Missing Generic Netlink Libraries
- Appendix F: Procedure to use latest supplicant with NL80211 interface
- Appendix G: Considerations need to be made during hostapd usage
- RS9116 n-Link Software TRM Revision History
RS9116 n-Link Linux and Android Technical Reference Manual
Version 2.0
August 2019
28
Note: wpa_supplicant version used should be latest one (2.6 or higher) and need to compile with CONFIG_P2P and
CONFIG_WPS flag enable.
After starting the supplicant, the p2p_commands mentioned below should be executed.
To find other P2P networks
#./wpa_cli -i wifi0 p2p_find
To find other P2P devices in range
#./wpa_cli -i wifi p2p_peers
To connect to p2p network
#./wpa_cli -i wifi0 p2p_connect <BSS ID > pbc go_intent=<intent value>
#./wpa_cli -i wifi0 p2p_connect <BSS ID > pbc go_intent=<intent value>
Here the intent value range is between 0 and 15 (Putting intent value to 0 makes p2p device as client and 15 makes
p2p device as group owner). If you are becoming GO, dhcp server should be running on GO Interface.
After becoming p2p-go run below cmd
#./wpa_cli -i wifi0
To recieve each connection request from P2P-Client's every time need to run below cmd in wpa_cli cmd promt.
-> wps_pbc
If p2p-client is RSI p2p-client then we need to run below cmd on RSI P2P-Client side.
#./wpa_cli -i wifi0 p2p_connect <RSI P2P_GO Mac Addr> pbc join
4.5 OneBox-Mobile in Wi-Fi + Bluetooth LE Coexistence Mode
This section describes the installation of Wi-Fi and Bluetooth LE (BLE) 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 "release" folder.
• Ensure that the DRIVER_MODE and COEX_MODE as set as below
- DRIVER_MODE = 1
- COEX_MODE = 9 (For WLAN Station and BT LE)