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
107
19 PUF [ Physical Unclonable Functions ]
19.1 Introduction
PUF, is a technology which provides a secure method for storing a key, withstanding today’s attack and even
protecting against future potential attack. The purpose of PUF is to provide secure key storage without storing the
key. Instead of storing the key a Key Code is generated which in combination with SRAM startup behavior is used to
reconstruct keys.
19.2 Configuration
This feature is default disabled in Host Driver. To use this feature, ensure that driver is compiled with below define
enabled in Makefile
EXTRA_CFLAGS += -DONEBOX_CONFIG_PUF
19.3 PUF Operations and IOCTL Usage
19.3.1 PUF Enroll
This operation enrolls PUF. After successful operation Activation code will be either saved in flash or it will be sent
to host. The stored activation code shall be used for every further start operation on PUF.
./onebox_util rpine0 puf_req 0 1
19.3.2 PUF Start
This operation is used to start PUF. Once valid activation code is available PUF will be started. Start operation is
must for any further operation with PUF.
./onebox_util rpine0 puf_req 1 1 puf_ac.txt
19.3.3 PUF Set Key
This operation is used for generating Key Code for the given key input.
./onebox_util rpine0 puf_req 2 0 0 abcdefghijklmnop
19.3.4 PUF Set Intrinsic Key
This operation is used for generating Key Code for internally generated intrinsic key.
./onebox_util rpine0 puf_req 3 0 0
19.3.5 PUF Get Key
This operation is used for generating key for the given key code input.