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
108
./onebox_util rpine0 puf_req 4 puf_keycode_0.txt
19.3.6 PUF Load Key
This operation is used for loading key to AES engine or key holder for the given key code input.
./onebox_util rpine0 puf_req 5 puf_keycode_0.txt
19.3.7 PUF AES Encryption
This operation is used for encrypting data inputted with Key provided or with key which is already loaded into AES
by PUF. It also provides provision for encryption with AES engine for two modes (ECB, CBC). Parameters should be
provided depending on mode of usage
./onebox_util rpine0 puf_req 6 0 0 0 0 128 plain_data.txt 0 0
19.3.8 PUF AES Decryption
This operation is used for decrypting data inputted with Key provided or with key which is already loaded into AES
by PUF. It also provides provision for decryption with AES engine for two modes (ECB, CBC). Parameters should be
provided depending on mode of usage
./onebox_util rpine0 puf_req 7 0 0 0 0 128 aes_enc_data.txt 0 0
19.3.9 PUF AESMAC Generation
This operation is used for generating Message authentication check (MAC) for the data inputted with provided key
as well as Initialization Vector (IV). Parameters should be provided depending on mode of usage
./onebox_util rpine0 puf_req 8 1 0 0 0 128 plain_data.txt 0 abcdefghijklmnop
19.3.10 PUF Block Enroll
This operation is used for blocking further enroll operations.
./onebox_util rpine0 puf_req 9
19.3.11 PUF Block Set Key
This operation is used for blocking further Set Key operations.
For the above command, create a text file plain_data.txt that should have some data of length more than
128 bytes
For the above command, create a text file plain_data.txt that should have some data of length more than
128 bytes