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
26
wpa_supplicant version used should be latest one (2.6 or higher). Please check the start_p2pgo.sh script for better
understanding and update it accordingly.
The given below command is used to start the device in Autonomous GO mode:
# ./wpa_cli –i wifi0 p2p_group_add freq=<channel_freq>
The "channel_freq" input mentioned in the above command is the center frequency of the Wi-Fi channel in which
the GO needs to be started The OneBox-Mobile software supports DFS slave mode. However, DFS Channels need to
be avoided till the module is certified for DFS.. If this parameter is not provided, then the GO will start in the
channel specified in the p2p_nl80211.conf file.
• 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.4.6.2 To connect multiple P2P-Client to RSI P2P-GO
4.4.6.3 1.Autonomous GO Mode
Steps for installing Onebox-Mobile software in Wi-Fi Direct Mode:
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 = 1
Note: For multiple clients in RSI P2P-GO mode POWER_SAVE_OPTION value in common_insert.sh file should be set
to 0.
Go to the release folder and start the device in p2P mode.
$ cd release
$ sh wlan_enable.sh
$ ./onebox_util rpine0 create_vap wifi0 p2p_go
Configure parameters in the p2p_nl80211.conf file as required. Ex: listen channel, operating channel, GO Intent
etc.
Now run supplicant as given below.
$./wpa_supplicant -i wifi0 -D nl802ll -c p2p_nl80211.conf -ddddt > log &