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
15
4.2 Enabling a Protocol
Execute following command to enable required protocol(s):
# ./onebox_util rpine0 enable_protocol $protocol_value
Below are the possible values of protocol.
• 1 – Enables Wi-Fi only
• 2 – Enables Bluetooth only
• 3– Enables both Wi-Fi+Bluetooth
Note:
• If user selects only Wi-Fi in Menuconfig during the compilation of Driver, use the command below :
sh wlan_enable.sh
• If user selects only Bluetooth in Menuconfig during thecompilation of Driver, use the command below :
sh bt_enable.sh
• If user selects both Wi-Fi and Bluetooth in Menuconfig during thecompilation of Driver,use the command
below :
sh wlan_bt_insert.sh
• If user selects all the protocols in Menuconfig during thecompilation of Driver, use the command below :
sh onebox_insert.sh
and need to run individual protocol enable scripts.
4.3 Disabling a Protocol
Execute he following command to disable required protocol(s):
# ./onebox_util rpine0 disable_protocol $protocol_value
• the possible values of protocol is same as mentioned in Enabling a Protocol.
Note:
• If user wants to disable only WLAN,use the command below :
sh wlan_disable.sh
• If user wants to disable only Bluetooth,use the command below :
sh bt_disable.sh
• If user wants to disable both WLAN and Bluetooth, use the command below :
sh remove_all.sh
4.4 OneBox-Mobile in Wi-Fi Only Mode
The steps for starting the Wi-Fi Only mode in Client, AccessPoint and Wi-Fi Direct modes are as follows:
1. Open the common_insert.sh file present in the "release" folder.
Disabling of protocol is not recommended when Wi-Fi is operating in AccessPoint mode.