all | frequencies |
|
|
|
|
|
|
|
|
|
|
exhibits | applications |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
manuals | photos | labels |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 2 3 4 |
|
User Manual | Users Manual | 1.90 MiB | December 31 2019 / June 28 2020 | delayed release | ||
1 2 3 4 |
|
kanega002 owners manual v1 | Users Manual | 291.14 KiB | March 19 2020 | |||
1 2 3 4 |
|
1912RSU024-UE-Internal Photo v1 | Internal Photos | 1.34 MiB | March 19 2020 | |||
1 2 3 4 |
|
2108RSU042-UE-Internal Rev2.0 | Internal Photos | 2.15 MiB | November 29 2021 / November 30 2021 | |||
1 2 3 4 |
|
Internal Photos | Internal Photos | 190.79 KiB | December 31 2019 / June 28 2020 | delayed release | ||
1 2 3 4 |
|
1912RSU024-UE | External Photos | 1.05 MiB | March 19 2020 | |||
1 2 3 4 |
|
2108RSU042-UE-External | External Photos | 1.30 MiB | November 29 2021 / November 30 2021 | |||
1 2 3 4 |
|
External Photos | External Photos | 449.11 KiB | December 31 2019 / June 28 2020 | delayed release | ||
1 2 3 4 |
|
KANEGA002-eLabel | ID Label/Location Info | 31.50 KiB | March 19 2020 | |||
1 2 3 4 |
|
Label and Label Location | ID Label/Location Info | 30.26 KiB | December 31 2019 | |||
1 2 3 4 |
|
2108RSU042-U4-FCC RF Test Report For BLE V3.0 | Test Report | 1.70 MiB | November 29 2021 / November 30 2021 | |||
1 2 3 4 |
|
2108RSU042-U5-FCC RF Test Report For Wi-FiV3.0 | Test Report | 1.94 MiB | November 29 2021 / November 30 2021 | |||
1 2 3 4 |
|
2108RSU042-UT-1 | Test Setup Photos | 348.37 KiB | November 29 2021 / November 30 2021 | |||
1 2 3 4 |
|
CP2C Module Authorization | Cover Letter(s) | 31.35 KiB | November 29 2021 / November 30 2021 | |||
1 2 3 4 |
|
FCC C2PC Request-BTwifi V3.0 | Cover Letter(s) | 124.75 KiB | November 29 2021 / November 30 2021 | |||
1 2 3 4 |
|
FCC Lab Authorization-signed | Cover Letter(s) | 50.28 KiB | November 29 2021 / November 30 2021 | |||
1 2 3 4 |
|
Modular Approval cover letter-BTwifi V3.0 | Cover Letter(s) | 171.50 KiB | November 29 2021 / November 30 2021 | |||
1 2 3 4 |
|
1912RSU024-U3-FCC SAR Test Report | RF Exposure Info | 1.94 MiB | March 19 2020 | |||
1 2 3 4 |
|
1912RSU024-U4-FCC IC RF Test Report For BLE v1 | Test Report | 1.76 MiB | March 19 2020 | |||
1 2 3 4 |
|
1912RSU024-U5-FCC IC RF Test Report For Wi-Fi v1 | Test Report | 2.15 MiB | March 19 2020 | |||
1 2 3 4 |
|
1912RSU024-UT | Test Setup Photos | 223.05 KiB | March 19 2020 | |||
1 2 3 4 |
|
ACB-FORM-FCC-Modular-Letter v1 | Cover Letter(s) | 281.85 KiB | March 19 2020 | |||
1 2 3 4 |
|
Annex E - Equipment Calibration Report v1 | RF Exposure Info | 5.49 MiB | March 19 2020 | |||
1 2 3 4 |
|
CP2C RedPine FCC ISED Module Authorization v1 | Cover Letter(s) | 98.90 KiB | March 19 2020 | |||
1 2 3 4 | Confidential Tune-up Procedure | Parts List/Tune Up Info | March 19 2020 | confidential | ||||
1 2 3 4 |
|
FCC Confidentiality Letter-signed | Cover Letter(s) | 46.40 KiB | March 19 2020 | |||
1 2 3 4 |
|
FCC C2PC Request-signed v1 | Cover Letter(s) | 60.75 KiB | March 19 2020 | |||
1 2 3 4 |
|
Individual Product RedPine FCC Lab Authorization-signed | Cover Letter(s) | 44.20 KiB | March 19 2020 | |||
1 2 3 4 | Block Diagram | Block Diagram | December 31 2019 | confidential | ||||
1 2 3 4 |
|
Confidential Authorization | Cover Letter(s) | 95.50 KiB | December 31 2019 | |||
1 2 3 4 |
|
MPE | RF Exposure Info | 392.95 KiB | December 31 2019 | |||
1 2 3 4 |
|
Modular Approval Letter | Cover Letter(s) | 92.71 KiB | December 31 2019 | |||
1 2 3 4 | Operational Description | Operational Description | December 31 2019 | confidential | ||||
1 2 3 4 | Schematics | Schematics | December 31 2019 | confidential | ||||
1 2 3 4 |
|
Test Report (2.4G Wi-Fi) | Test Report | 4.41 MiB | December 31 2019 | |||
1 2 3 4 |
|
Test Report (BLE) | Test Report | 3.66 MiB | December 31 2019 | |||
1 2 3 4 |
|
Test Report (Zigbee) | Test Report | 2.56 MiB | December 31 2019 | |||
1 2 3 4 |
|
Test Setup Photos | Test Setup Photos | 495.52 KiB | December 31 2019 / June 28 2020 | delayed release |
1 2 3 4 | User Manual | Users Manual | 1.90 MiB | December 31 2019 / June 28 2020 | delayed release |
RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Redpine Signals, Inc. 2107 North First Street, Suite #540, San Jose, California 95131, United States of America. Phone: +1-408-748-3385, Fax: +1-408-705-2019 Email: sales@redpinesignals.com Website: www.redpinesignals.com
RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Table of Contents 1 2 3 4 6 7 Introduction to RS9116.............................................................................................................. 7 Getting Started with RS9116 ..................................................................................................... 8 2.1 Hardware Requirements ........................................................................................................... 8 2.2 Software Requirements............................................................................................................. 8 2.3 Software Package Contents ...................................................................................................... 8 Compiling the Driver .................................................................................................................. 9 Installing the Driver.................................................................................................................. 14 4.1 Installation of Modules ............................................................................................................ 14 4.2 Enabling a Protocol.................................................................................................................. 15 4.3 Disabling a Protocol................................................................................................................. 15 4.4 OneBox-Mobile in Wi-Fi Only Mode......................................................................................... 15 4.5 OneBox-Mobile in Wi-Fi + Bluetooth LE Coexistence Mode ................................................... 28 4.6 Driver Information ................................................................................................................... 30 5 Wi-Fi ioctl Usage Guide ............................................................................................................ 31 5.1 Configuring using Wireless Extensions ................................................................................... 31 5.2 Private (Driver-Specific) Commands for Access Point and Client Modes ............................. 33 5.3 Private (Driver- Specific) Commands for Access Point Mode ................................................ 38 5.4 Private (Driver- Specific) Commands for Client Mode ........................................................... 43 5.5 Configuring Using onebox_util................................................................................................ 44 Configuration Using CFG80211 ............................................................................................... 65 6.1 Using iw Wireless Tool ............................................................................................................. 65 Enterprise security using CFG80211........................................................................................ 70 7.1 Installation and configuration of FREERADIUS Server........................................................... 70 7.2 Configuration of AP and RADIUS server to use EAP methods................................................ 71 8 HOSTAPD and Wi-Fi Protected Setup (WPS) .......................................................................... 77 8.1 Hostapd Configuration before Compilation........................................................................... 77 8.2 Configuration in hostapd_wps.conf ....................................................................................... 77 8.3 WPS........................................................................................................................................... 78 9 ACS with Hostapd .................................................................................................................... 81 2 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 10 Antenna Diversity..................................................................................................................... 82 10.1 Introduction ............................................................................................................................. 82 10.2 Configuration ........................................................................................................................... 82 11 Sniffer Mode ............................................................................................................................. 83 12 Monitor Mode ........................................................................................................................... 84 13 Concurrent Mode ..................................................................................................................... 85 13.1 Installation Procedure ............................................................................................................. 85 14 Background Scan Parameters................................................................................................. 90 15 Power save Modes, Profiles and Parameters ......................................................................... 91 15.1 Power save Modes.................................................................................................................... 91 15.2 Power save Profiles.................................................................................................................. 91 15.3 Wakeup Procedures and Data Retrieval ................................................................................. 91 15.4 Power save Parameters ........................................................................................................... 92 15.5 Procedure to enable device power save for USB interface ................................................... 93 16 Compliance and Certification ................................................................................................. 95 16.1 Federal Communication Commission Statement.................................................................. 95 16.2 Industry Canada / ISED Statement ......................................................................................... 95 16.3 Regulatory Module Integration Instructions .......................................................................... 96 17 Wi-Fi Performance Test ioctl usage......................................................................................... 98 17.1 WiFi Transmit Tests.................................................................................................................. 98 17.2 Wi-Fi Receive Tests................................................................................................................. 101 17.3 Continuous Wave (CW) mode ................................................................................................ 102 18 Wake-On-Wireless LAN .......................................................................................................... 104 18.1 WoWLAN through onebox_util .............................................................................................. 104 18.2 WoWLAN using Linux power state machine ......................................................................... 104 19 PUF [ Physical Unclonable Functions ] ................................................................................. 107 19.1 Introduction ........................................................................................................................... 107 19.2 Configuration ......................................................................................................................... 107 19.3 PUF Operations and IOCTL Usage......................................................................................... 107 20 GTK Offload ............................................................................................................................ 110 3 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 20.1 Configuration ......................................................................................................................... 110 21 Steps to connect 802.11R client to AP .................................................................................. 111 22 Steps to configure 802.11W ................................................................................................... 112 22.1 Configuring and Compiling Driver for PMF in client mode: ................................................. 112 22.2 Configuring and Compiling Driver for PMF in AP mode: ...................................................... 112 23 Update WLAN region based maximum powers from driver ................................................ 113 24 Bluetooth hcitool and hciconfig Usage ................................................................................ 114 24.1 Bluetooth Power Save Commands ....................................................................................... 116 24.2 Bluetooth Performance Test ioctl Usage.............................................................................. 116 24.3 BLE/BLR Transmit .................................................................................................................. 116 24.4 BLE/BLR Receive .................................................................................................................... 120 24.5 Hopping .................................................................................................................................. 122 25 Android support for RS9116 .................................................................................................. 124 26 Appendix A: Configuration of Kernels from 3.13 and above ................................................ 125 26.1 SDIO Stack Options................................................................................................................ 125 26.2 Wireless Extension Tools ....................................................................................................... 126 26.3 Bluetooth Stack Options ....................................................................................................... 127 26.4 Kernel Compilation ................................................................................................................ 128 27 Appendix B: Binary Files for Embedded Platforms .............................................................. 129 27.1 Common Hardware Requirements for Embedded Platforms ............................................. 129 27.2 Freescale i.MX6....................................................................................................................... 129 27.3 Freescale i.MX53..................................................................................................................... 130 27.4 Atmel AT91SAM9G45 and AT91SAM9M10 ............................................................................. 131 28 Appendix C: Using the Bluetooth Manager........................................................................... 133 29 Appendix D: Common Configuration Parameters................................................................ 136 29.1 RF Power Mode parameter.................................................................................................... 136 29.2 Country selection ................................................................................................................... 136 29.3 Antenna selection .................................................................................................................. 136 30 Appendix E: Installation of Missing Generic Netlink Libraries ............................................. 139 31 Appendix F: Procedure to use latest supplicant with NL80211 interface ........................... 140 4 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 31.1 Bgscan and Roaming ............................................................................................................. 140 32 Appendix G: Considerations need to be made during hostapd usage................................ 142 32.1 Parameters updated from hostapd.conf file........................................................................ 142 33 RS9116 n-Link Software TRM Revision History..................................................................... 143 5 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 About this Document This document is a preliminary version of RS9116 n-Link Technical Reference Manual for Linux and Android, provided to customers 6 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 1 Introduction to RS9116 The OneBox-Mobile(refers to single software providing combo of all the features supported) software supports the following modes. They are outlined below:
Wi-Fi (Access Point, Client, Wi-Fi-Direct (P2P), Sniffer and Monitor modes) Bluetooth Low Energy 802.15.4 Compatibility The OneBox-Mobile Coexistence software supports the following combination of modes. They are as follows:
WLAN STATION /WIFI-Direct/WLAN PER WLAN ACCESS POINT(including muliple APs on different vaps) WLAN ACCESS POINT + STATION MODE(on multiple vaps) WAKE ON WIRELESS(WOWLAN) BT LE MODE /BT LE PER MODE WLAN STATION + BT LE MODE WLAN STATION + BT LE MODE WLAN ACCESS POINT + BT LE MODE The subsequent sections explain the use of OneBox-Mobile software . The installation and operation of the driver on specific representative processor platforms have been explained in the Appendix sections. 7 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 This section lists the hardware and software requirements for the installation of the software and also describes the steps to be followed to initialize and run the software. 2 Getting Started with RS9116 2.1 Hardware Requirements The Hardware requirements are as follows:
RS9116N n-Link Module Laptop/PC with SDIO or USB interface or any embedded platform with Linux Board support package. If the Laptop/PC does not have an SDIO slot, a SDHC/SD/MMC to CardBus Adapter like the one available at http://www.hwtools.net/cardreader/SDCBA_C01.html can be used. 2.2 Software Requirements The Software requirements are as follows:
Linux with kernel version from 2.6.38 to 4.18.5 should enable the open source SDIO and USB stacks. DHCP Server (for Wi-Fi Access Point mode) Bluetooth supported commands bluetoothctl and bluetoothd must be present. Compatible Bluetooth Host Stack, e.g., the Open Source BlueZ Stack v4.101 ncurses and ncurses-devel libraries For kernel versions 3.13 and above, refer to the section onAppendix A: Configuration of Kernels from 3.13 and above to ensure correct kernel configuration. 2.3 Software Package Contents The OneBox-Mobile Software is delivered as a tarball with a filename in the format:
RS9116.NXX.NL.GEN.LNX.x.y.z.tgz, where the naming convention is as follows:
NXX defines whether the package supports only Wi-Fi (N00) or BT Low Energy along with Wi-Fi (NB0). x.y.z identifies the software package. Redpine driver comes in proprietary and open source form.The Linux driver package contains the following files/
folders:
Readme_nLink.txt Releasenotes_nLink.txt Documents Binary_files (optional) source (optional) Based on the Software License Agreement, driver source code will be available for the users from "https://
www.redpinenetworks.us/OpenKM/login.jsp"
8 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 3 Compiling the Driver This section describes the steps to be followed in order to compile the OneBox-Mobile Linux software for different platforms.The steps are outlined below:
1. Save the required configuration of Driver using the menuconfig utility. Following are the options available in menuconfig:
Host Interface: SDIO or USB. Operating system: Linux or Android Nl80211 support Hostapd Support Wi-Fi Bluetooth make menuconfig The following images show the menuconfig utility options. 2. To open menuconfig utility, untar the tar ball, go to source->host folder & enter the given below command. Figure 1: Main Page of menuconfig 9 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Figure 2: SelectingOperating System By default, the driver package includes "BSD" support. In case the user needs "Nl80211" support for Access point and Station modes, select the menuconfig accordingly. For Nl80211, the "Hostapd" application is used as a configuration utility. Figure 3: Selection of NL80211 and Hostapd Support 10 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 If NL80211 support is enabled in the driver, make sure that the following modules are loaded in the kernel before running the driver in order to avoid module dependencies. This can be verified by using the commands.
# lsmod | grep cfg80211
# lsmod | grep bluetooth
# modprobe cfg80211
# modprobe bluetooth If they are not installed, can be installed by using the commands below :
By default the configuration is enabled with Wi-Fi and Bluetooth. If the user wants to compile the driver for a particular protocol, he can disable the unwanted protocols in Menuconfig utility.In case of coex mode, the Wi-Fi must always be enabled in conjunction with BT protocols, even if Wi-Fi will not be used. For example, if the user wants to compile the driver only for Bluetooth only, the Wi-Fi and Bluetooth mode must be enabled. Refer to the following images of Menuconfig utility for more information:
Figure 4: Selection of WIFI Only Mode 3. After selecting the configuration, exit the menuconfig and save the configuration. Please refer the given below image of saving the configuration. 11 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 make vim Makefile Example:
4. Now to compile the driver, enter the following command:
Figure 5: Save the changes before exiting The code is compiled and the binaries are generated in thesource/host/release folder.For embedded platforms, modify the path assigned to the "DEF_KERNEL_DIR" variable in the Makefile:
cd RS9116.NXX.NL.GEN.LNX.x.y.z/source/host The DEF_KERNEL_DIR variable has to be assigned along with the compiled kernel path. For an x86 based Linux platform, the path is usually "/lib/modules/<kernel_version>/build" and this is the path assigned in the Makefile provided in the package. DEF_KERNEL_DIR:= /lib/modules/3.4.66/build Next, use the "make" command to start compiling the driver. For embedded platforms, add the target platform and toolchain path as cross compilation option to the "make" command. For example, if the target platform is ARM and tool chain path is "/opt/freescale/usr/local/gcc-4.4.4-
glibc-2.11.1-multilib-1.0/arm-fsl-linux-gnueabi/bin/arm-none-linux-gnueabi-", then the command is issued as:
make ARCH=arm CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-linux-
gnueabi/bin/arm-none-linux-gnueabi-
12 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Before installing the Onebox RS9116 Driver modules, make sure that the RSI opensource modules are uninstalled. This has been taken care in the onebox_insert.sh script. In order to un-install the RSI opensource driver, use the following commands:
# rmmod rsi_usb
# rmmod rsi_sdo
# rmmod rsi_91x 13 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 After completion of compilation, the driver generates the following modules in the release folder. They are outlined below:
4 Installing the Driver 4.1 Installation of Modules onebox_common_gpl.ko onebox_gpl.ko onebox_nongpl.ko onebox_wlan_gpl.ko onebox_wlan_nongpl.ko onebox_bt_gpl.ko onebox_bt_nongpl.ko wlan.ko wlan_wep.ko wlan_ccmp.ko wlan_tkip.ko wlan_acl.ko wlan_scan_sta.ko wlan_xauth.ko Note: Please change operating voltage configuration (1.8V or 3.3V) in common_insert.sh file in FEATURE_BITMAP_9116. Example: For 3.3V keep FEATURE_BITMAP_9116=0 For 1.8V keep FEATURE_BITMAP_9116=2 For 3.3V, 5Mhz BW keep FEATURE_BITMAP_9116=32 Note: Please select appropriate SLEEP CLOCK SOURCE in common_insert.sh file as required SLEEP CLOCK SOURCE SELCECTION =
0 - Use 32khz internal RC clock as sleep clock 1 - Use 32KHz clock from external XTAL OSCILLATOR (Applicable only for Silicon Version <= 1.3 ) 2 - Use 32KHz bypass clock on UULP_GPIO_3 3 - Use 32KHz bypass clock on UULP_GPIO_4 Note: Please configure SLEEP_GPIO in common_insert.sh file as connected SLEEP_IND_GPIO_SEL =
0 - UULP_GPIO_3 1 - UULP_GPIO_0 Now,Load various modules in the following order:
Load onebox common gpl module
# insmod onebox_common_gpl.ko Load protocol related Modules (Wi-Fi, BT) Load common Hal Modules (onebox_nongpl.ko and onebox_gpl.ko). 14 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 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 :
If user selects only Bluetooth in Menuconfig during thecompilation of Driver, use the command below :
If user selects both Wi-Fi and Bluetooth in Menuconfig during thecompilation of Driver,use the command below :
If user selects all the protocols in Menuconfig during thecompilation of Driver, use the command below :
sh wlan_enable.sh sh bt_enable.sh sh wlan_bt_insert.sh 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. If user wants to disable only WLAN,use the command below :
If user wants to disable only Bluetooth,use the command below :
If user wants to disable both WLAN and Bluetooth, use the command below :
Note:
sh wlan_disable.sh sh bt_disable.sh sh remove_all.sh Disabling of protocol is not recommended when Wi-Fi is operating in AccessPoint mode. 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. 15 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 2. Ensure DRIVER_MODE and COEX_MODE are set as below:
DRIVER_MODE = 1 COEX_MODE = 1 (For Station Mode only/WIFI-Direct) COEX_MODE = 2 (For Access Point Mode) COEX_MODE = 3 (For BothAccess Point and Station Modes) For SDIO mode, ensure that the SDIO stack related modules are already inserted in the kernel referAppendix A: Configuration of Kernels from 3.13 and above section to install sdio stack modules . 4.4.1 Installation in Wi-Fi Client Mode (with BSD interface support) The steps for installing OneBox-Mobile software in Wi-Fi Client Mode are as follows:
1. Edit the "sta_settings.conf" file in the "release" folder and enter the parameters of the Wi-Fi network as given below:
For Open (non-Secure) mode ssid="<SSID of Access Point>"
network={
key_mgmt=NONE
For WPA-PSK (TKIP) mode network={
ssid="<SSID of Access Point>"
key_mgmt=WPA-PSK psk=<passphrase specified in the Access Point>
proto=WPA pairwise=TKIP group=TKIP
For WPA2-PSK (CCMP) mode network={
ssid="<SSID of Access Point>"
key_mgmt=WPA-PSK psk=<passphrase specified in the Access Point>
proto=WPA2 pairwise=CCMP group=CCMP
For WEP-64 mode 16 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 network={
ssid="<SSID of Access Point>"
key_mgmt=NONE wep_key0=XXXXXXXXXX wep_tx_keyidx=X
The key can be input either in ASCII or Hexadecimal formats:
ASCII Format: wep_key0="12345"
Hexadecimal Format: wep_key0=1234567890 The key index can vary between 0 and 3. For WEP-128 mode network={
key_mgmt=NONE ssid="<SSID of Access Point>"
wep_key0=XXXXXXXXXXXXXXXXXXXXXXXXXX wep_tx_keyidx=X
The key can be input either in ASCII or Hexadecimal formats:
ASCII Format: wep_key0="1234567890123"
Hexadecimal Format: wep_key0=12345678901234567890123456 The key index can vary between 0 and 3. For WEP-Shared (64-bit) mode network={
ssid="<SSID of Access Point>"
key_mgmt=NONE wep_key0=XXXXXXXXXX wep_tx_keyidx=X auth_alg=SHARED
scan_ssid=1 For example The key can be input either in ASCII or Hexadecimal formats:
ASCII Format: wep_key0="12345"
Hexadecimal Format: wep_key0=1234567890 The key index can vary between 0 and 3. To connect to an Access Point whose SSID is not broadcast (Hidden), add the following line to the network block. 17 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 ssid="<SSID of Access Point>"
network={
scan_ssid=1 key_mgmt=NONE
sh start_sta.sh ifconfig a iwconfig wifi0 Next, run the "start_sta.sh" script in the "release" folder to load the driver modules and the supplicant and also connect to the Access Point specified in the "sta_settings.conf" file. User needs to make sure of the module detection w.r.t interface being used. If the module is not detected, user will end up with errors displayed on the console !
After issuing the above command, a virtual interface with the name "wifi0" will be created. You can view the list of interfaces by entering the following command:
You can check whether the connection to the Access Point is successful or not, by running the following command:
The sample output of this command is wifi0 IEEE 802.11bgn ESSID:"Range" Nickname:""
Mode:Managed Frequency:2.412 GHz Access Point: 38:A4:ED:DE:BB:06 Bit Rate:39 Mb/s Tx-Power=16 dBm Sensitivity=1/0 RTS thr:off Fragment thr:off Encryption key:****-**** Security mode:restricted Power Management:off Link Quality=80/80 Signal level=-28 dBm Noise level:0 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 This command gives the status of the device. If the connection is successful, then the connected Access point SSID along with the MAC address is displayed. If it is not connected to an Access point, a message "Not Associated" is displayed. To view the list of Access Points scanned in each channel, you can run the following command in the "release"
folder. /wpa_cli i wifi0 scan_results To obtain an IP address using DHCP, start the DHCP client by entering below commands. (1st command to remove entry for existing dhcp and 2nd to create a new entry). 18 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
$ dhclient -r wifi0
$ dhclient -v wifi0 The sample output of dhclient command is given below Listening on LPF/wifi0/88:da:1a:1e:b2:58 Sending on LPF/wifi0/88:da:1a:1e:b2:58 Sending on Socket/fallback DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 4 (xid=0x133cec16) DHCPREQUEST on wifi0 to 255.255.255.255 port 67 (xid=0x133cec16) DHCPOFFER from 192.168.43.1 DHCPACK from 192.168.43.1 (xid=0x133cec16) bound to 192.168.43.167 -- renewal in 1783 seconds 4.4.2 Installation in Access Point Mode (with BSD interface support) The steps for installing OneBox-Mobile software in Access Point Mode are as follows:
1. The "start_ap.sh" script present in the "release" folder needs to be run with the different configuration files present in the same folder in order to install an Access Point in different security modes.
# sh start_ap.sh <conf_file>
For example : sh start_ap.sh wpa_supplicant_open.conf The different configuration files (.conf files) present in the "release" folder are as follows:
For Access Point in Open Mode, wpa_supplicant_open.conf configuration file is used, and this starts an Access Point with the following parameters:
For Access Point in WEP-64 Mode, wpa_supplicant_wep64.conf configuration file is used, and this starts an Access Point with the following parameters:
SSID: REDPINE_AP Channel 1 of 2.4GHz Band (2412 MHz) Open (non-Secure) mode SSID: onebox_wep Channel 1 of 2.4GHz Band (2412 MHz) Security Mode: WEP-64 WEP Key: 1234567890 Key Index: 0 SSID: onebox_wep Channel 1 of 2.4GHz Band (2412 MHz) Security Mode: WEP-128 WEP Key: 12345678901234567890123456 Key Index: 0 SSID: onebox_tkip For Access Point in WEP-128 Mode, wpa_supplicant_wep128.conf configuration file is used, and this starts an Access Point with the following parameters:
For Access Point in WPA-PSK (TKIP) Mode, wpa_supplicant_tkip.conf configuration file is used, and this starts an Access Point with the following parameters:
19 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Channel 1 of 2.4GHz Band (2412 MHz) Security Mode: WPA-PSK (TKIP) Passphrase: "12345678"
SSID: onebox_ccmp Channel 1 of 2.4GHz Band (2412 MHz) Security Mode: WPA2-PSK (CCMP) Passphrase: "12345678"
For Access Point in WPA2-PSK (CCMP) Mode, wpa_supplicant_ccmp.conf configuration file is used, and this starts an Access Point with the following parameters:
All the above mentioned parameters can be modified in the respective configuration files by the user. The values provided in the above mentioned parameters are only for reference. The Access Point does not support WEP-Shared algorithm in the current release. 2. After running the "start_ap.sh" script a virtual interface with the name "wifi1" will be created. You can view the list of interfaces using the following command:
You can check whether the Access Point has been started successfully or not, by running the following command:
ifconfig a iwconfig wifi1 The sample output of this command is wifi1 IEEE 802.11bgn ESSID:"test" Nickname:""
Mode:Master Frequency:2.432 GHz Access Point: 88:DA:1A:16:E5:5D Bit Rate:6 Mb/s Tx-Power=30 dBm Sensitivity=1/0 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=80/80 Noise level:0 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 This command gives the status of the device. It displays the Access Point's SSID along with the MAC address and channel frequency. If the Access Point does not start, a message saying "Exiting: Driver Initialization not completed even after waiting for xxms" is displayed. To start a DHCP server, use the commands below. sh dhcp_server.sh wifi1 Note: If DHCP server is not present , we can also assign IP statically by using following command. Also it should be noted that dhclient at connected clients will not work as dhcp server is not started at AP. We should assign IP statically at client side also. 20 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 ifconfig <interface> <IP>
Example : ifconfig wifi1 192.168.2.1 4.4.3 Installation in Wi-Fi Client Mode (with NL80211 support) The steps for installing Wi-Fi Only mode in Client are as follows:
1. Open the common_insert.sh file present in the "release" folder. 2. Ensure that the DRIVER_MODE and COEX_MODE are set as below:
DRIVER_MODE = 1 COEX_MODE = 1 (For Station Mode only/WIFI-Direct) or COEX_MODE = 3 (For BothAccess Point and Station Modes) For SDIO mode, ensure that the SDIO stack related modules are already inserted in the kernel referAppendix A: Configuration of Kernels from 3.13 and above section to install sdio stack modules . Ensure that in menuconfig, NL80211 support is enabled as mentioned in Figure 4. 3. Compile the driver. Make sure the following parameters are enabled in the supplicant configuration file (wlan/supplicant/
linux/wpa_supplicant/.config) CONFIG_DRIVER_NL80211=y CONFIG_LIBNL32=y
$ make
$ cd release
$ sh wlan_enable.sh
$iw phy | grep phy Make sure to install CRDA in your system/PC to use updated regulatory domain in NL80211 mode. 4. Go to the release folder and start the device in station mode. 5. Issue the following command to get physical interfaces on which we can add wifi0 interface The output of the command will be phyX (X can be 1,2,3, eg:phy1,phy2 etc) 21 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 In case of multiple phy's to identify the appropriate phy on which to run the command, enter the following command. iw dev phy#3 phy#0 The sample output of this command is Interface wlp0s26u1u2 ifindex 10 wdev 0x300000001 addr 00:23:a7:65:2a:ac type managed Interface wlo1 ifindex 3 wdev 0x1 addr a4:17:31:a7:82:a3 type managed In the above example "Phy3" is Redpine's interface. Assuming the physical interface is detected as phy1, refer the below steps to create a virtual interface. 6. Add the wireless interface to the phy. Instead of following the above 2 steps i.e. step 5 and step 6, we can directly create vap by using "onebox_util"
binary present in the release folder.
$service NetworkManager stop
$iw phy phy1 interface add wifi0 type managed cd release
./onebox_util rpine0 create_vap wifi0 sta sw_bmiss Run the supplicant after configuring sta_settings.conf with required AP settings as mentioned in the section Installation in Wi-Fi Client Mode (with BSD interface support) In the sta_settings.conf file, in addition to the above all configurations as mentioned for BSD case, NL80211 mode required country input in the global fields which need to be set as specified below. country=US Now run supplicant as given below.
$ ./wpa_supplicant -i wifi0 -D nl802ll -c sta_settings.conf -ddddt > log &
22 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 4.4.4 Installation in Wi-Fi AP mode (with NL80211 support) The steps for installing Wi-Fi Only mode in AP are as follows:
1. Open the common_insert.sh file present in the "release" folder. 2. Ensure that the DRIVER_MODE and COEX_MODE are set as below DRIVER_MODE = 1 COEX_MODE = 2 (For Access Point Mode)
(Or) COEX_MODE = 3 (For BothAccess Point and Station Modes) 3. Ensure that in menuconfig, NL80211 and HOSTAPD support is enabled. 4. Compile the driver. Make sure the following parameters are enabled in the hostapd configuration file (wlan/hostapd-2.4/
hostapd/.config) CONFIG_LIBNL32=y Make sure to install CRDA in your system/PC to use updated regulatory domain in nl80211 mode Compilation of NL80211 requires libnl library files. Please refer to page Appendix F: Installation of Missing Generic Netlink Libraries for configuration of hoapd.conf file for libnl and installing libnl drivers if they are not available. 5. Go to the release folder and start the device in Access Point mode.
$ make
$ cd release
$ sh wlan_enable.sh
$iw phy | grep phy 6. Issue the following command to get physical interfaces on which we can add wifi0 interface The output of the command will be phyX (X can be 1,2,3, eg:phy1,phy2 etc) Now add wifi0 interface to phyX.
$service NetworkManager stop
$iw phy phy1 interface add wifi0 type __ap Instead of following the above steps in step 6, we can directly create vap by using "onebox_util" binary present in the release folder
$ ./onebox_util rpine0 create_vap wifi0 ap 23 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Configure the SSID Settings of the AP in the hostapd_open.conf file (say if you are starting AP in open mode). In order to start AP in a particular band and channels, configure variables hw_mode, channel and country in hostapd_open.conf (present in release folder) file as follows :
hw_mode=g ( 'g'-2.4GHz) channel=1 country_code=US Note:
Channel selection in the hostapd_open.conf file should be appropriate as per the band selected. Make sure in hostapd_open.conf file, the AP netdevice name is set to wifi0 or wifi1 according to the interface obtained by following the above steps. For eg:
Interface = wifi0 Note: Refer section Appendix G: Considerations need to be made during hostapd usage for description of other configurable parameters of hostapd.conf file(s). 7. Run hostapd with following command
$ ./hostapd hostapd_open.conf ddddt> log &
In the same way, we can also configure required SSID and Passphrase and key management settings in hostapd_ccmp.conf, hostapd_wep.conf, hostapd_tkip.conf files accordingly. If you want to use Auto Channel Selection using hostapd refer ACS with Hostapd section. 4.4.5 Installation in Wi-Fi Direct Mode (With BSD Interface Support) The steps for installing OneBox-Mobile software in Wi-Fi Direct Mode are as follows:
The "start_p2p.sh" script present in the "release" folder needs to be run in order to start the supplicant and also for installing the Wi-Fi Direct mode. The configurable parameters in the p2p.conf file are outlined below:
listen channel operating channel GO Intent 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 wifi0 p2p_peers To connect to a P2P network
#. /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). 4.4.5.1 Autonomous GO Mode The given below command is used to start the device in Autonomous GO mode:
24 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
# ./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.conf file. 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 4.4.6 Installation in Wi-Fi Direct Mode (With NL80211 Support only for Kernel v3.8 or higher) The steps for installing OneBox-Mobile software in Wi-Fi Direct Mode are as follows:
The "start_p2p_nl80211.sh" script present in the "release" folder needs to be run in order to start the supplicant and also for installing the Wi-Fi Direct mode. The configurable parameters in the p2p_nl80211.conf file are outlined below:
wpa_supplicant version used should be latest one (2.6 or higher). Please check the start_p2p_nl80211.sh script for better understanding and update it accordingly. After starting the supplicant, the p2p_commands mentioned below should be executed. listen channel operating channel GO Intent To find other P2P networks
#. /wpa_cli i wifi0 p2p_find To find other P2P devices in range
#. /wpa_cli i wifi0 p2p_peers To connect to a P2P network
#. /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. 4.4.6.1 Autonomous GO Mode The steps for installing OneBox-Mobile software in Wi-Fi Direct Mode are as follows:
The "start_p2pgo.sh" script present in the "release" folder needs to be run in order to start the supplicant and also for installing the Wi-Fi Direct mode. The configurable parameters in the p2p_nl80211.conf file are outlined below:
listen channel operating channel GO Intent 25 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 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 &
26 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Note: wpa_supplicant version used should be latest one (2.6 or higher) and need to compile with CONFIG_P2P and CONFIG_WPS flag enble. Use below command to start the device in Autonomous GO mode:
#./wpa_cli -i wifi0 p2p_group_add freq=<channel_freq>
Run DHCP Server on GO Interface before connecting P2P or Legacy devices using below cmd.
#sh dhcp_server.sh wifi0
#./wpa_cli -i wifi0
-> wps_pbc P2P Devices can scan this Group Owner and can connect directly. Run following command to start receiving connect calls from P2P devices. To receive each connection request from P2P-Client's every time we need to run below cmd in wpa_cli cmd promt. 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 2. GO-negotiation 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 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 &
27 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 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) 28 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 For SDIO mode, ensure that the SDIO stack related modules are already inserted in the kernel referAppendix A: Configuration of Kernels from 3.13 and above section to install sdio stack modules . 1. Follow the instructions in section 4.4.1 Installation in Wi-Fi Client Mode, inorder to install the Wi-Fi Client 2. Run the bt_enable.sh or wlan_bt_insert.sh or onebox_insert.sh script present in the "release" folder as per the instructions present in the section 4.1 inorder to start the Bluetooth LE mode. This script inserts Bluetooth modules as well as common HAL modules, provided if it is not inserted initially. 3. You can check whether the BLE mode has been started successfully or not, by running the following Note:
mode. command:
# hciconfig If the driver is loaded correctly, the above command displays a network adaptor named "hciX". An example output is given below:
hci0:Type: BR/EDR Bus: SDIO BD Address: 00:23:A7:00:05:68 ACL MTU: 1021:8 SCO MTU: 30:8 UP RUNNING PSCAN RX bytes:478 acl:0 sco:0 events:20 errors:0 TX bytes:331 acl:0 sco:0 commands:19 errors:0 4. After the device is up, we can Advertise, Scan and Connect with other BLE devices. The device can be configured using hcitool or hciconfig. 4.5.1 Advertise, Scan, Connect Commands The commands for Advertise, Scan and Connect are as follows:
Enable Advertise
# hciconfig a <hciX> leadv Disable Advertise
# hciconfig a <hciX> noleadv Initiate Scan
# hcitool -i <hciX> lescan The above command displays the scan responses and advertising information. Master Mode Connected State Ensure that the remote device is in Advertise mode and then issue the command given below:
29 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
# hcitool i <hciX> lecc <remote_MAC_Addr>
The "remote_MAC_Addr" parameter mentioned above is the MAC address of the remote device, e.g., 00:23:AC:
01:02:03. Slave Mode Connected State Ensure that our device is in Advertise mode and then issue the command given below:
# hcitool i <hciX> lecc <device_MAC_Addr>
The "device_MAC_Addr" parameter mentioned above is the MAC address of the Redpine module, e.g., 00:23:AC:
01:02:03. 4.6 Driver Information 4.6.1 Driver Statistics cat /proc/rpine<$id>/stats
# cat /proc/rpine0/stats cat /proc/rpine1/stats Use the given below command inorder to view Wi-Fi driver statistics:
<$id> Indicates Id of Wi-Fi device. For example if rpine0 is created for module then to view Wi-Fi related statistics related to module then Use the below command:
When 2nd usb device is connected to same host then rpine1 will get created, In order to see the Wi-Fi related statistics related to 2nd usb module use the below command:
This command prints statistics related to the total management packets, total data packets with respect to a given access category sent to/from the driver, buffer full status as well as semi buffer full status, FSM states etc. 4.6.2 Disabling Driver Debug Prints You may opt to disable the debug prints of the driver appearing on the console by using the given below command. Ensure that the driver is installed correctly before using this command for SDIO interface.
# echo 0x0 > /proc/onebox-hal/debug_zone For USB interface, the proc name is onebox-mobile$devnum$busnum.
# echo 0x0 > /proc/onebox-hal<$devnum$busnum>/debug_zone 30 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 5 Wi-Fi ioctl Usage Guide This section explains about the usage of various ioctl commands present in the OneBox-Mobile driver. The user has control over multiple settings such as device settings, radio, aggregation, fragmentation thresholds, power save configurations and so on. 5.1 Configuring using Wireless Extensions iwconfig" is a generic Linux based wireless tool which is used for setting parameters for a wireless network interface. It may be used in lieu of the Wi-Fi supplicant provided as a part of the OneBox-Mobile software. However, care has to be taken to follow the correct sequence of commands while using "iwconfig". The Redpine Signals recommends usage of the supplicant provided in the software package. This section describes the usage of "iwconfig" in conjunction with the Onebox-Mobile driver. For a detailed description of the tool, refer to the relevant main pages in Linux.
"iwconfig" only works when the driver is operating in the 'BSD' mode. The details of the Access Point for which the n-Link is connected in the Client mode can be viewed by using the given below command. Description This command is used to set the Channel for the n-Link module.
# iwconfig <vap_name>
The table below describes the usage of the command in more detail. Set Channel/Frequency (only in Monitor mode) Default value 1 Input Parameters VAP Name (string like wifi0, wifi1, etc.) Channel number Output Parameter None Reset required No Usage
# iwconfig <vap_name> freq <channel_no>
# iwconfig <vap_name> channel <channel_no>
Example
# iwconfig wifi0 freq 6
(OR)
(OR)
# iwconfig wifi0 channel 6 Set Data Transmit Rate Description This command is used to set the data rate for transmission. Default value 0 (Auto Rate) 31 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters VAP Name (string like wifi0, wifi1, etc.) Integer value as per the mapping below:
Auto Rate 0 1 Mbps 2 2 Mbps 4 5.5 Mbps 11 11 Mbps 22 6 Mbps 12 12 Mbps 24 18 Mbps 36 24 Mbps 48 36 Mbps 72 48 Mbps 96 54 Mbps 108 MCS0 13 MCS1 26 MCS2 39 MCS3 52 MCS4 78 MCS5 104 MCS6 117 MCS7 130 Output Parameter None Reset required No Usage
# iwconfig <vap_name> rate <rate_val>
Note: For Access Point mode, this command has to be issued after the Set Mode command only if the VAP has started using iwconfig commands and not using the supplicant provided by Redpine Signals. For Client mode, the Set Mode command is not mandatory Set RTS/CTS Threshold (only in Access Point mode) Description This command is used to set the RTS/CTS threshold of the n-Link Module. 32 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Default Value 2346 Input Parameters VAP Name (string like wifi0, wifi1, etc.) Integer between 256 and 2346 Output Parameter None Reset Required No. Usage Example
# iwconfig <vap_name> rts <payload_size>
The command below sets the RTS/CTS threshold to 1008 bytes:
# iwconfig wifi0 rts 1008 Set Transmit Power Description This command is used to set the transmit power of the n-Link Module Note: If the value of transmit power set in the above command exceeds the maximum allowable power supported by the channel specified by the regulatory domain, then the minimum of the two values shall be used Default Value
Input Parameters VAP Name (string like wifi0, wifi1, etc.) Integer value in dBm Output Parameter None Reset Required No Usage Example
# iwconfig <vap_name> txpower <val_in_dBm>
# iwconfig wifi0 txpower 10 Note:
Txpower setting can be defined as the minimum value that can be picked from the max regulatory power settings, from any user defined value and also from the maximum values the radio can support. So it is not guaranteed that the user defined value gets effected when these settings is done. Table 1: iwconfig Usage 5.2 Private (Driver-Specific) Commands for Access Point and Client Modes The "iwpriv" command is used to set parameters specific to the OneBox-Mobile software. The table below lists the usage of the "iwpriv" command for setting and getting parameters common for the Access Point and Client modes. 33 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Set Short GI Description This command is used to set the Short GI mode of the n-Link Module. Default Value 0 (Short GI disabled for both 20 MHz and 40 Mhz Bandwidth) Input Parameters VAP Name (string like wifi0, wifi1, etc.) The integer value mapping has been shown below:
0 Disable Short GI 1 Enable Short GI for 20MHz Bandwidth 2 Enable Short GI for 40MHz Bandwidth 3 Enable Short GI for 20MHz and 40MHz Bandwidths Output Parameter None Reset Required Yes. Refer to the example for the reset process Usage Example
# iwpriv <vap_name> short_gi <value>
The commands given below set the Short GI for 20MHz bandwidth and then reset the adapter for the command to take effect:
# iwpriv wifi0 short_gi 1
# ./onebox_util rpine0 reset_adapter Note:
Issue this ioctl before starting the supplicant. Note:
Here short_gi ioctl will work only in case of bsd. To set short_gi using hostapd , refer to the section Appendix G: Considerations need to be made during hostapd usage Get Short GI Description Default Value
Input Parameters VAP Name (string like wifi0, wifi1, etc.) This command is used to get the value programmed for Short GI mode of the n-Link Module 34 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Output Parameter The integer value mapping has been shown below:
0 Disable Short GI 32 Enable Short GI for 20MHz Bandwidth 64 Enable Short GI for 40MHz Bandwidth 96 Enable Short GI for 20MHz and 40MHz Bandwidths
# iwpriv <vap_name> get_short_gi The command given below explains about getting the Short GI programmed in the module:
# iwpriv wifi0 get_short_gi Reset Required No Usage Example Get Privacy Default Value
Description This command is used to get the Privacy bit of the n-Link Module Input Parameters VAP Name (string like wifi0, wifi1, etc.) Output Parameter The integer value mapping has been shown below:
0 Privacy is disabled 1 Privacy is enabled Reset Required No Usage Example
# iwpriv <vap_name> get_privacy The command given below tells about like how to get the Privacy information in the module:
# iwpriv wifi0 get_privacy Set WMM (only in Access Point mode) Description This command is used to enable the WMM (QoS) feature of the n-Link Module Default Value 1 (Enabled) Input Parameters VAP Name (string like wifi0, wifi1, etc.) The integer value mapping has been shown below:
0 Disable 1 Enable 35 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Output Parameter None Reset Required No Usage Example
# iwpriv <vap_name> wmm <value>
The command below sets the WMM mode for the module:
# iwpriv wifi0 wmm 1 Note: Issue this command before starting the supplicant in Access Point Mode. Set AMPDU Description Default Value
This command is used to enable AMPDU Aggregation in the n-Link Module Input Parameters VAP Name (string like wifi0, wifi1, etc.) The integer value mapping has been shown below:
0 Disable AMPDU Aggregation 1 Enable AMPDU Aggregation for Transmit, disable for Receive 2 Enable AMPDU Aggregation for Receive, disable for Transmit Output Parameter None Reset Required No Usage Example
# iwpriv <vap_name> ampdu_set <value>
The command given below disables A-MPDU aggregation:
The command given below enables A-MPDU aggregation for Transmit:
# iwpriv wifi0 ampdu_set 0
# iwpriv wifi0 ampdu_set 1 Set Bandwidth Description Default Value
This command is used to enable or disable 20/40 MHz Bandwidths in the n-Link Module. 36 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters VAP Name (string like wifi0, wifi1, etc.) The integer value mapping has been shown below:
1- Enable only 20MHz 2- Enable only 40MHz 3 Enable both 20 and 40MHz Output Parameter None Reset Required Yes. Refer to the example for the reset process for Client and Access Point modes Usage Example
# iwpriv <vap_name> set_htconf <value>
The commands given below is used to delete and create the VAP to set the bandwidth in Access Point mode:
# ./onebox_util rpine0 delete_vap wifi0
# ./onebox_util rpine0 create_vap wifi0 ap
# iwpriv wifi0 set_htconf $value
# ./wpa_supplicant i wifi0 wpa_supplicant_open.conf &
Note:
Note:
Issue this ioctl before starting the supplicant. The commands given below is used to set the 20MHz bandwidth in Client mode and reset the Client for the command to take effect:
# iwpriv wifi0 set_htconf 1
# ./onebox_util rpine0 reset_adapter. Here Set Bandwidth ioctl will work only in case of bsd. To set Bandwidth using hostapd , refer to the section Appendix G: Considerations need to be made during hostapd usage Set Debug Zone Default Value 0x4000 Description This command is used to select the debug zone for Wifi. 37 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters Zone value. The integer value mapping has been shown below:
0 Disable zone. 0x4000 Error Zone. Output Parameter None Reset Required No Usage Example
# iwpriv <vap name> set_dbg_zone <zone_value>
The following command disables debug zone level.
# iwpriv wifi0 set_dbg_zone 0 Table 2: iwpriv Usage for Access Point and Client Modes 5.3 Private (Driver- Specific) Commands for Access Point Mode The table below describes the usage of the "iwpriv" command for setting and getting parameters common for the Access Point Mode. Set DTIM Period Description Default Value 1 Input Parameters Output Parameter None Reset Required This command is used to set the DTIM period in the n-Link Module. Issue this command before starting the supplicant. VAP Name (string like wifi0, wifi1, etc.) Integer value between 1 and 15 Yes. In order to set the DTIM period, the virtual interface has to be reset. Usage 1. iwpriv <vap_name> dtim_period <value>
38 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Example The commands given below is used to reset the VAP and set the DTIM period:
#sh remove_all.sh
#sh wlan_enable.sh (or) wlan_bt_insert.sh (or) wlan_zigb_insert.sh (or) onebox_insert.sh script present in the "release" folder as per the instructions in Section 4.1
#./onebox_util rpine0 create_vap wifi1 ap
#iwpriv wifi1 dtim_period $value
#./wpa_supplicant I wifi1 D bsd c wpa_supplicant_open.conf ddddt > log &
Note:
Issue this ioctl before starting the supplicant in Access Point. Note:
Here dtim_period ioctl will work only in case of bsd. To set dtim_period using hostapd , refer to the section Appendix G:
Considerations need to be made during hostapd usage This command is used to get the DTIM period in the n-Link Module. Get DTIM Period Description Default Value Usage Example Get Beacon Interval Description Default Value
Input Parameters VAP Name (string like wifi0, wifi1, etc.) Output Parameter Integer value ranges between 1 and 15 Reset Required No. iwpriv <vap_name> get_dtim_period The command given below is used to get the DTIM period programmed in the module:
#iwpriv wifi0 get_dtim_period This command is used to get the Beacon Interval programmed in the n-Link Module Input Parameters VAP Name (string like wifi0, wifi1, etc.) 39 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Output Parameter Integer value Reset Required No Usage Example
# iwpriv <vap_name> get_bintval The command given below is used to get the Beacon interval programmed in the module:
#iwpriv wifi0 get_bintval MAC Command Description This command is used to set the Access Policy based on MAC address. The Access Policy can be disabled or can be used to allow or denyconnection from the MAC address.[1]
Note:
All the acl policy commands need to be issued before starting the wpa_supplicant. Default Value
Input Parameters VAP Name (string like wifi0, wifi1, etc.) The integer value mapping has been shown below:
0 Disable Access Policy 1 Enable Access Policy and Allowconnection 2 Enable Access Policy and Denyconnection Output Parameter Reset Required None No Usage Example
# iwpriv <vap_name> maccmd <value>
The command given below enables the ACL Policy and allows connection:
# iwpriv wifi0 maccmd 1 The command given below enables the ACL Policy and denies connection:
# iwpriv wifi0 maccmd 2 Add MAC Address for Access Policy Description Default Value
This command is used to add a MAC address for the Access Policy in the n-Link Module. 40 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters VAP Name (string like wifi0, wifi1, etc.) 48-bit MAC Address in hexadecimal format with colon separation. e.g., 00:23:A7:01:02:03 Output Parameter Reset Required None No Usage Example Delete MAC Address from Access Policy list Description Default Value
Output Parameter Reset Required None No Usage Example
# iwpriv <vap_name> addmac <mac_addr>
The command given below adds a MAC Address (10:10:A9:12:13:14) to the ACL Policy:
# iwpriv wifi0 addmac 10:10:a9:12:13:14 Note: Issue this command before a Station connects to the module. This command is used to delete a MAC address from the Access Policy described in the n-Link Module Input Parameters VAP Name (string like wifi0, wifi1, etc.) 48-bit MAC Address in hexadecimal format with colon separation. e.g., 00:23:A7:01:02:03
# iwpriv <vap_name> delmac <mac_addr>
The command given below is used to delete a MAC Address
(10:10:A9:12:13:14) from the ACL Policy:
# iwpriv wifi0 delmac 10:10:a9:12:13:14 Set Hidden SSID Description This command is used to stop broadcasting of the SSID of the Access Point in the n-Link Modules beacons and probe responses. Default Value 0 (Hidden SSID Disabled) Input Parameters VAP Name (string like wifi0, wifi1, etc.) The integer value mapping has been shown below:
0 Disable Hidden SSID (SSID is broadcast) 1 Enable Hidden SSID (SSID is not broadcast) 41 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Output Parameter None Reset Required Usage Example Yes. In order to move from/to Hidden SSID mode, the virtual interface has to be reset.
# iwpriv <vap_name> hide_ssid <value>
The command given below is used to start the Access Point in hidden mode:
# ./onebox_util rpine0 create_vap wifi0 ap
# iwpriv wifi0 hide_ssid 1
# ./wpa_supplicant i wifi0 D bsd c wpa.conf &
Note:
Note:
Issue this ioctl before starting the supplicant. Here hide_ssid ioctl will work only in case of bsd. To disable ssid broadcast in beacons for onebox-mobile AP using hostapd , refer to the section Appendix G: Considerations need to be made during hostapd usage Set DFS channel to switch to Description This command is used to select a channel to switch to in case of Radar Detection in Access Point mode. This is used only when the bsd driver is used. Default Value Disabled (A channel gets picked at random) Input Parameters VAP Name (string like wifi0, wifi1, etc.) Frequency of the channel to switch to in case of radar detection. Output Parameter Reset Required None No Usage Example
# iwpriv <vap name> dfs_chan_switch <frequency>
The following command sets the channel 36 as the channel for switching to.
# iwpriv wifi0 dfs_chan_switch 5180 Set Mgmt Rate Description Default Value 0 This command is used to set the mgmt rate 42 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters value*2 Output Parameter Reset Required None No Usage Example
# iwpriv <vap name> mgmt_rate <value*2>
The Following command sets the mgmt rate to 5.5Mbps
#iwpriv wifi0 mgmt_rate 11 To disable the mgmt_rate use the below command:
#iwpriv wifi0 mgmt_rate 0 Set Keep Alive Period in AP mode Description This command is used to set the Keep Alive period in the n-Link Module. It is recommended that this command is given after the VAP is created and before wpa_supplicant/hostapd is started Default Value 240 seconds Input Parameters VAP Name (string like wifi0, wifi1, etc.) Integer value ranges between 15 and 12000 (seconds). Integer value should be a multiple of 15, if the value is not a multiple of 15, it will rounded off to nearst multiple of 15. Output Parameter Reset Required None No Usage Example
# iwpriv <vap_name> keep_alive <value>
The command given below sets the Keep Alive period to 30 seconds, after rounding off 35 to the nearest multiple of 15.
# iwpriv wifi0 keep_alive 35 Table 3: iwpriv Usage for Access Point Mode 5.4 Private (Driver- Specific) Commands for Client Mode The table below lists the usage of the "iwpriv" command for setting and getting parameters common for the Client Mode. De authenticate while Roaming Description This command is used to de authenticate the n-Link Module from
"old" Access Point while roaming. 43 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Default Value NULL Data Input Parameters VAP Name (string like wifi0, wifi1, etc.) Integer value - 0 or 1 0 Inform Access Point that the module is going to be in power save mode. 1 De authenticate from the previous Access Point during Roaming. Output Parameter Reset Required Usage None No iwpriv <vap_name> setparam 12 The value 12 is used for setting Roaming related parameters for the setparam command. <value>
Example The command below sends de authentication during roaming. iwpriv wifi0 setparam 12 1 Set Keep Alive Period Description This command is used to set the Keep Alive period in the n-Link Module. Default Value 90 seconds Input Parameters VAP Name (string like wifi0, wifi1, etc.) Integer value ranges between 15 and 12000 (seconds) Output Parameter Reset Required None No Usage Example Table 4: iwpriv Usage for Client Mode 5.5 Configuring Using onebox_util
# iwpriv <vap_name> keep_alive <value>
The command given below sets the Keep Alive period to 100 seconds:
# iwpriv wifi0 keep_alive 100 The "onebox_util" program is provided to configure the n-Link module for parameters which are not specific to a virtual interface (VAP). The table below describes the usage of the "onebox_util" command for setting and getting the parameters. 44 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Create a VAP The OneBox-
Mobile software allows creation of 4 VAPs Description Default Value Input Parameters
This command is used to create a virtual interface (VAP) in the operating mode specified. Note: The OneBox-Mobile software allows creation of 4 VAPs Base Interface (string like rpine0) VAP Name (string like wifi0, wifi1, etc.) Operating Mode (string):
ap Access Point Mode sta Station/Client Mode p2p P2P Mode mon Monitor Mode Refer to the sectionMonitor Mode for more details. Beacon Filtering after connecting to an Access Point (only for Client mode). Valid inputs are:
sw_bmiss Beacon filtering disabled. All beacons of connected Access Point provided to Host driver. hw_bmiss Beacon filtering is enabled. The Beacon is provided to Host driver when there is a change in the Beacon from the connected Access Point. This feature also programs the device to indicate to the Host driver when 20 consecutive beacons are not received by the device. Output Parameter Reset Required None No Usage Example Delete a VAP Description
./onebox_util <base_interface> create_vap <vap_name>
<op_mode>
The command given below creates a virtual interface named wifi0 in the Client mode with Beacon filtering disabled.
/onebox_util rpine0 create_vap wifi0 sta sw_bm This command is used to delete an existing virtual interface
(VAP). Default Value
45 RS9116 n-Link Linux and Android Technical Reference Manual Input Parameters Base Interface (string like rpine0) VAP Name (string like wifi0, wifi1, etc.) Version 2.0 August 2019 None No Output Parameter Reset Required Usage Example Print VAP Statistics Description Default Value
Input Parameters VAP Name (string like wifi0, wifi1, etc.) Output Parameter Statistics like:
# ./onebox_util <base_interface> delete_vap <vap_name>
The command given below deletes a virtual interface named wifi0.
# ./onebox_util rpine0 delete_vap wifi0 This command is used to print the statistics of the transmitted and received packets of an existing virtual interface (VAP).
[-v] Get description of the fields in the statistics Filename (string) to which the statistics will be written 1) Number of Beacons transmitted (for Access Point/P2P GO modes) 2) Number of Beacons received (for Client/P2P Client modes) 3) Number of Management packets received 4) Number of packets received from a different BSS
# ./onebox_util <vap_name> print_vap_stats [-v] [-f filename]
The command given below prints the statistics of the transmitted and received packets of the interface wifi0 into the file stats.
# ./onebox_util wifi0 print_vap_stats -v -f stats This command is used to print the statistics of the packets exchanged between the Access Point and a Station. 46 etc. No Reset Required Usage Example Print Station Statistics
(only in Access Point mode) Description RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Default Value
Input Parameters VAP Name (string like wifi0, wifi1, etc.) Output Parameter Statistics like:
48-bit MAC Address in hexadecimal format with colon separation. e.g., 00:23:A7:01:02:03
[-v] Get description of the fields in the statistics Filename (string) to which the statistics will be written 1) Number of Beacons received 2) Number of Management packets transmitted/received 3) Number of Unicast/Multicast packets transmitted/
received 4) Number of data packets transmitted/received 5) Number of Probe Request/Response packets transmitted/
received etc.
# ./onebox_util <vap_name> print_station_stats <mac_addr> [-
v] [-f filename]
The command below logs the statistics of the packets exchanged between the Access Point (wifi0) and a Station with MAC address 00:1C:2b:10:19:1a into the file named stats.
#./onebox_util wifi0 print_station_stats 00:1C:2b:10:19:1a -v -f stats This command is used to select one of the two RF ports connecting to antennas. For the modules without integrated antenna, it is used to select between pins RF_OUT_1 and RF_OUT_2. For the modules with integrated antenna and U.FL connector, it is used to select between the two. In case Antenna Diversity feature is enabled, this ioctl will not have any effect. The Antenna selection will happen automatically at the firmware level. Note:
This ioctl is redundant. Refer to Section 16 for futher details. The functionality of the ioclt is intact. However it might be removed in the future to reduce redundancy. 47 Usage Example Select Antenna Description Default Value 2 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters Base Interface (string like rpine0) The integer value mapping has been shown below:
2 Select RF_OUT_2/Integrated Antenna 3 Select RF_OUT_1/U.FL Connector Output Parameter Reset Required Usage Example None No Enable Background Scan and Set Parameters (only in Client mode) Description
# ./onebox_util <base_interface> ant_sel <value>
The command given below selects the U.FL connector in case of modules with integrated antenna and will select RF_OUT_1 pin in the case of the module without an integrated antenna.
# ./onebox_util rpine0 ant_sel 3 This command is used to enable background scan and set the relevant parameters. Refer to the section onBackground Scan Parameters for more details on each parameter. Default Value 2 Input Parameters Base Interface (string like rpine0) Background Scan Threshold RSSI Tolerance Threshold Periodicity Active Scan Duration Passive Scan Duration Two Probe Enable Number of Background Scan Channels Channels to Scan Note: The OneBox-Mobile software supports DFS slave mode. However, DFS Channels need to be avoided till the module is certified for DFS. Output Parameter Reset Required None No. 48 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Usage Example Note Host-Triggered Background Scan (only in Client mode) Description Default Value Input Parameters Output Parameter Reset Required Usage Example
None No.
# ./onebox_util <base_interface> set_bgscan_params
<bgscan_threshold> <rssi_tolerance_threshold> <periodicity>
<active_scan_duration> <passive_scan_duration>
<two_probe_enable> <num_of_bgscan_channels>
<channels_to_scan>
The command given below enables Background Scan with a scan threshold of 10, RSSI tolerance threshold of 10, periodicity of 3 seconds, active scan duration of 20 milliseconds, passive scan duration of 100 milliseconds, two-probe enabled and the channels 36, 40 and 44.
# ./onebox_util rpine0 set_bgscan_params 10 10 3 20 100 1 3 36 40 44 In order to select 11J channels 8, 12, 16, enter the channel number as 8J, 12J, 16J respectively. Remaining 11J channels can be selected with their channel numbers. Example:
# ./onebox_util rpine0 set_bgscan_params 10 10 3 20 100 1 4 36 40 44 8J This command is used to trigger background scan without waiting for the periodicity mentioned in bgscan_parameters.
# ./onebox_util <base_interface> do_bgscan The command given below triggers background scan without waiting for periodicity timeout.
# ./onebox_util rpine0 do_bgscan Note:The do_bgscan command has to be followed by set_bgscan_params command. 49 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Set SSID for Background Scan (only in Client mode) Description Default Value
Output Parameter Reset Required None No. Usage Example Input Parameters Base Interface (string like rpine0) SSID (max. 32 characters) This command is used to set the SSID of the Hidden Access Point (SSID not being broadcast) during Background Scan.
# ./onebox_util <base_interface> bgscan_ssid <ssid>
The command below sets the SSID of a Hidden Access Point during Background Scan.
# ./onebox_util rpine0 bgscan_ssid REDPINE_AP Note:The bgscan_ssid command has to be followed by the set_bgscan_params or do_bgscan command in order for the Probe Request to be sent with the SSID requested in the bgscan_ssid command. This command is used to enable/disable power save modes and set the required power save mode for the n-Link module. Refer to the sectionPower save Modes, Profiles and Parameters for more details on each parameter and their usage. Enable Power Save and Set Parameters (only in Client mode) Description Default Value
50 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters Base Interface (string like rpine0) Power Save Enable/Disable Sleep Type Transmit Threshold Receive Threshold Transmit Hysteresis Receive Hysteresis Monitor Interval Sleep Duration Listen Interval Duration Number of Beacons per Listen Interval DTIM Interval Duration Number of DTIMs Per Sleep Duration Output Parameter Reset Required Usage None No. Example Enable UAPSD (Normal and Mimic modes) and Set Parameters Description Default Value
# ./onebox_util <base_interface> set_ps_params <ps_en>
<sleep_type> <tx_threshold> <rx_threshold> <tx_hysteresis>
<rx_hysteresis> <monitor_interval> <sleep_duration>
<listen_interval_duration> <num_beacons_per_listen_interval>
<dtim_interval_duration> <num_dtims_per_sleep>
The command below enables ULP Power Save Mode for a duration of 100 ms and with a listen_interval_duration of 100ms.
# ./onebox_util rpine0 set_ps_params 1 2 0 0 0 0 0 100 100 0 0 1 This command is used to enable the UAPSD mode and set the relevant parameters. If the Access Point does not support UAPSD, the module tries to mimic this mode. Refer to the sectionPower save Modes, Profiles and Parameters for more details.[1]
51 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters Base Interface (string like rpine0) UAPSD Wakeup Period in milliseconds 0 for Transmit Based UAPSD and between 10 and 100 for Periodic UAPSD. UAPSD Service Period Length- This field indicates number of packets delivered by AP to station after receiving one trigger frame. This filed value ranges between 0-3 as described below. 0-All buffered packets will be delivered. 1-Two buffered packets will be delivered. 2-four buffered packets will be delivered. 3-six buffered packets will be delivered.
# ./onebox_util <base_interface> set_uapsd_params 0xF
<sp_len> <uapsd_wakeup_period>
The command enables UAPSD mode and sets the wakeup period as 100ms.
# ./onebox_util rpine0 set_uapsd_params 0xF 0 100 Note: The set_uapsd_params command needs to be followed by the command given below for the values to take effect.
# ./onebox_util <base_interface> reset_adapter Output Parameter Reset Required None No. Usage Example Reset Adapter (only in Client mode) Description Default Value Input Parameters Output Parameter Reset Required
This command is used to reset the Client mode virtual interface. This command can be used to change certain configurations of the Client mode and reset the VAP for the configurations to take effect. Base Interface (string like rpine0) the base interface input ensures that the Client mode VAP is reset irrespective of the actual VAP name. Usage
/onebox_util <base_interface> reset_adapter 52 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Example
/onebox_util rpine0 reset_adapter Set Beacon Interval (only in Access Point mode) Description Default Value 200 Input Parameters Base Interface (string like rpine0) This command is used to set the Beacon Interval in milliseconds. It is recommended that this command is given before the VAP is created. Output Parameter None Reset Required Usage Example Integer value between 56 and 1000 (other values will result in default value being assigned). Yes. In order to set the beacon interval, the virtual interface has to be reset.
# ./onebox_util <base_interface> set_beacon_intvl
<beacon_intvl>
The commands given below are used to reset the Access Point and set the beacon interval to 100ms.
# sh remove_all.sh
# sh wlan_enable.sh or wlan_bt_insert.sh or wlan_zigb_insert.sh or onebox_insert.sh script present in the release folder as per the instructions in Installation of Modules
# ./onebox_util rpine0 set_beacon_intvl 100
# ./onebox_util rpine0 create_vap wifi0 ap
# ./wpa_supplicant i wifi0 -D bsd c wpa.conf -ddddt &
Issue this command before creating any virtual Access Point interfaces. Note:
Note:
Here set_beacon_intvl ioctl will work only in case of bsd. To set beacon interval using hostapd , refer to the section Appendix G:
Considerations need to be made during hostapd usage 53 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Set WMM Parameters (only in Access Point mode) Description This command is used to set the WMM parameters for specific queues. Note: This ioctl is redundant, refer to the Section 16 for further details. The functionality of the ioclt is intact, however it might be removed in the future inorder to reduce redundancy. Default Value Access Point:
AIFSN Cwmin Cwmax TxOp AC_BE 3 AC_BG7 AC_VI 1 AC_VO1 Station:
AC_BE 3 AC_BG7 AC_VI 4 AC_VO4 4 4 3 2 4 4 3 2 6 10 4 3 10 6 4 3 0 0 94 47 0 0 94 47 AIFSN Cwmin Cwmax TxOp 54 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters VAP Name (string like wifi0, wifi1, etc.) WMM Parameter Name (string like aifs, cwmin, cwmax, txop, acm) Integer value. The allowed values are as follows:
AIFSN 1 to 15 Cwmin 2n-1, where n is between 1 and 4 for BE_Q and BK_Q and between 1 and 3 for VI_Q and VO_Q. Cwmax 2n-1, where n is between 1 and 6 for BE_Q, between 1 and 10 for BK_Q and between 1 and 4 for VI_Q and VO_Q. TxOp 0 for BE_Q, BK_Q, 94 for VI_Q and 47 for VO_Q Access Category (string, as mapped below):
1) VO_Q Voice data packets queue 2) VI_Q Video data packets queue 3) BK_Q Background data packets queue 4) BE_Q Best effort data packets queue Self or Broadcast selection (Self is for the modules Access Point VAP, Broadcast is for Clients connected to the Access Point) Update Params (integer value mapped as below):
0 To set more WMM Parameters 1 To update current WMM Parameters None Output Parameter Reset Required No. Usage Example Set Country Description Default Value
# ./onebox_util <vap_name> setwmmparams
<wmm_param_name> <value> <access_category> <self/
broadcast> <update_params>
The command given below updates the AIFSN value for BE Access category for connected Clients.
# ./onebox_util wifi0 setwmmparams aifsn 2 BE_Q broadcast 1 This command is used to set the country for the n-Link Module.
55 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Input Parameters Integer (country code) mapped as below:
REGION COUNTRY_CODE COUNTRY_NAME FCC ETSI JAPAN WORLD 36 840 124 484 250 56 276 380 392 356 364 458 554 643 702 710 UNITED STATES CANADA MEXICO FRANCE BELGIUM GERMANY ITALY JAPAN AUSTRALIA INDIA IRAN MALAYSIA NEWZEALAND RUSSIA SINGAPORE SOUTH AFRICA Output Parameter None Reset Required Yes. In order to change the country code, the virtual interface has to be reset. Usage
# ./onebox_util <base_interface> set_country <country_code>
56 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Example The commands below reset the VAP and set the country to Singapore in Station mode.
# sh remove_all.sh
# sh wlan_enable.sh or wlan_bt_insert.sh or wlan_zigb_insert.sh or onebox_insert.sh script present in the release folder as per the instructions in Section 4.1
# ./onebox_util rpine0 set_country 702
# ./onebox_util rpine0 create_vap wifi0 sta sw_bmiss Note:
Issue this command before creating any interfaces. This command is used to get the country for the n-Link Module.
Base Interface (string like rpine0) Country code (string like US, JP ... ) No
#./onebox_util <base_interface> get_info country
#./onebox_util rpine0 get_info country This command is used to program the gain of the external antenna for the module without antenna. The gain values are used by the module to attenuate the output transmit power so that regulatory requirements like FCC, ETSI, etc., are not violated. This command needs to be given before creating the VAP in the normal mode and before the ./transmit command in the Wi-Fi Performance Test mode. In the Wi-Fi Performance Test mode, the transmission has to be stopped each time before the antenna gain values are programmed. 0 Base Interface (string like rpine0) Integer value for Antenna gain for 2.4 GHz band in dBm None No
# ./onebox_util <base_interface> set_ext_ant_gain <gain_2g>
<RESERVED>
57 Get Country Info Description Default Value Input Parameters Output Parameters Reset Required Usage Example Set External Antenna Gain Description Default Value Input Parameters Output Parameters Reset Required Usage RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Example The commands below set the Antenna gain values for 2.4 GHz to 3 dBm RESERVED field should be programmed as 1
# sh remove_all.sh
# sh wlan_enable.sh or wlan_bt_insert.sh or onebox_insert.sh script present in the release folder as per the instructions mentioned in the section Installation of Modules.
# ./onebox_util rpine0 set_ext_ant_gain 3 1
# ./onebox_util rpine0 create_vap wifi0 sta This command is used to configure the antenna, based on its type and its mounted path. The configuration values are used by the module to attenuate the output transmit power based on the selected antenna type for the corresponding path so that the regulatory requirements like FCC, ETSI, etc., are not violated. This command needs to be given before creating the VAP in the normal mode and before the "./transmit" command in the "Wi-Fi Performance Test ioctl usage" as mentioned in the section Wi-Fi Performance Test ioctl usage. ant_path: 1 ant_type: 1 For ant_path For ant_type If value is 1, then it is considered as RF_OUT_2/Integrated Antenna If value is 2, then it is considered as RF_OUT_1/U.FL Connector. If value is 1, then it is considered as Type 1 antenna. If value is 2, then it is considered as Type 2 antenna. If value is 3, then it is considered as Type 3 antenna. Use the following table to configure antenna type based on 2G gain values Set Antenna Type Description Default Value Input Parameters 2G Gain range Antenna Type 0 < Gain <= 0.99 Type 1 0.99 < Gain <= 1.8Type 2 1.8 < Gain <= 3 Type 3 Output Parameters None 58 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Reset Required Usage Example No
./onebox_util rpine0 ant_type ant_path ant_type
# ./onebox_util rpine0 ant_type 1 2 Set Wake-On-Wireless LAN Parameters (only in Client Mode) Description Default Value Input Parameters
Base Interface (string like rpine0) This command is used to set the Wake-On-Wireless LAN
(WoWLAN) parameters in the device. The Host has to give this command each time when it enters and exits sleep state. Refer to the section Wake-On-Wireless LAN Parameters for more details. GPIO_2 is used as a Host Wakeup Interrupt for this purpose. This feature is supported only in STA alone mode(non coex) supported wakeup options [disconnect] [magic-packet] [gtk-
with SDIO host interface rekey-failure]
48-bit Source MAC Address in hexadecimal format with colon separation. e.g., 00:23:A7:01:02:03 (valid when Unicast packet filtering from specific MAC address is enabled) Host Sleep Status WoWLAN Flags None No
# ./onebox_util <base_interface> wowlan <src_mac_addr>
<host_sleep_status> <wowlan_flags>
This command is used to program the RF power mode to High, Medium and Low profiles. It has to be issued before creating the VAP. The performance of the RF is best in the High power mode. 0 - High The integer value mapping has been shown below:
0 High power mode 1 Medium power mode 2 Low power mode 59 Example
# ./onebox_util rpine0 wowlan 00:23:a7:0c:bb:aa 1 3 Output Parameters Reset Required Usage Set RF Power Mode Description Default Value Input Parameters RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 None No
# ./onebox_util <base_interface> set_rf_tx_rx_pwr_mode tx_value rx_value
./onebox_util rpine0 set_rf_tx_rx_pwr_mode 0 1 This command is used to select the band in which the user wants to perform the scan. Using this command the user can test in 2.4Ghz 1 To scan 2.4Ghz only band Integer value None No
# ./onebox_util <base_interface> set_scan_type value
./onebox_util rpine0 set_scan_type 1 The above command performs scan only in 2.4Ghz band. Note:
Issue this command before creating station virtual interface. Set Beacon Filter (Only in AP mode) Description Default Value This command is used to enable beacon filtering in the firmware. All the third party beacons will be filtered at the firmware after applying beacon filter Ioctl. 0-Disabled by default Input Parameters The integer value mapping has been shown below:
Output Parameters Reset Required Usage Example Set scan type Description Default Value Input Prameters Output Parameters Reset Required Usage Example Output Parameter Reset Required Usage Example 0-Disabled beacon filtering 1-Enabled beacon filtering None No
# ./onebox_util <base_interface> set_rx_filter 0 0 0 0 <value> 0 0
./onebox_util rpine0 set_rx_filter 0 0 0 0 1 0 0 The above command does not allow beacons to be received from firmware to driver in AP mode. Note:
In the above command BIT (0, 1, 2, 3, 5, 6) are reserved for future use. Only BIT (4) is used for beacon filtering. 60 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Get Tx-Power Description Default Value Input Parameters Output Parameter Reset Required Usage Example Useonly rates Description Default Value Input Prameters This command is used to get current value of transmit power from firmware and updates it in iwconfig command.
None No
# ./onebox_util <base_interface> get_txpwr
./onebox_util rpine0 get_txpwr This command is used set the supported rates in AP mode. This will be helpfull to control the transmit data rates of the clients connected. All rates supported as per regulatory domain. Integer value as per the mapping below:
1 Mbps 2 2 Mbps 4 5.5 Mbps 11 11 Mbps 22 6 Mbps 12 Output Parameters Reset Required Usage Example Table 5: Usage of onebox util 5.5.1 WPS Configuration 12 Mbps 24 None No
# ./onebox_util <base_interface> useonly_rates <rate_val>
<rate_val> <rate_val>
./onebox_util rpine0 useonly_rates 2 11 12 Wi-Fi Protected Setup (WPS) is a standard for easy and secure wireless network setup and connections. The Onebox-Mobile supports the following configuration methods:
Push Button Method PIN Method Enter and Generate A WPS Configuration file is used for setting up a connection with a remote Access Point or Station. A sample WPS configuration file is given below for reference. 61 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 ctrl_interface=/var/run/wpa_supplicant update_config=1 uuid=12345678-9abc-def0-1234-56789abcdef0 device_name=RSI_P2P_DEVICE manufacturer=Redpine Signals, Inc. model_name=M2MCombo model_number=9113 serial_number=03 device_type=1-0050F204-1 os_version=01020300 config_methods=display push_button keypad 5.5.1.1 Access Point Mode The steps for configuring WPS in Access Point Mode are as follows:
1. Start the driver in Access Point mode. 2. Start the supplicant by entering the following command.
#. /wpa_supplicant i <vap_name> -D bsd c <wps_conf_file> -ddddt 3. For Push Button method:
Push the button on the STA Enter the command below for the n-Link Access Point
# ./wpa_cli i <vap_name> wps_pbc <sta_mac_addr>
The sections below list down the steps for configuring WPS and setting up a connection in Access Point and Client modes using the methods listed above. This is the 3rd party Station's MAC address. If all the MAC addresses need to be allowed, the input parameter is the string "any". 4. Wait for the STA to parse all the WPS Access Points. 5. For Enter PIN method Click on "Generate PIN" on the STA. A 4/8-digit numeric WPS PIN is generated. Enter the command below for the n-Link Access Point
#. /wpa_cli i <vap_name> wps_pin <sta_mac_addr> <wps_pin>
Wait for the STA to parse all the WPS Access Points. 6. For Generate PIN method Enter the command below for the n-Link Access Point 62 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
#. /wpa_cli i <vap_name> wps_pin <sta_mac_addr>
This will generate a 4/8-digit numeric WPS PIN. 7. Enter the PIN on the STA. 8. Wait for the STA to parse all the WPS Access Points. Note:
1. WPS_PIN and passphrase are different. 2. WPS connection timeout is 120 seconds 3. 3rd party Stations usually try to connect to all scanned WPS Access Points until they succeed in connecting to 4. WPS can be used along with any of the Secure modes (except WEP) and also with Open mode. one of them. 5.5.1.2 Client Mode The steps for configuring WPS in Client mode are as follows:
1. Start the driver in Client mode. 2. Start the supplicant by entering the following command.
# ./wpa_supplicant i <vap_name> -D bsd c <wps_conf_file> -ddddt 3. For Push Button method:
Push the button on the Access Point Enter the command below for the n-Link STA
# ./wpa_cli i <vap_name> wps_pbc <bssid>
Note:
This is the Access Point's MAC address. If the BSSID is not known, the input parameter will be the string named "any". Wait for the STA to parse all the WPS Access Points. 4. For Enter PIN method, Click on "Generate PIN" on the Access Point. A 4/8-digit numeric WPS PIN is generated. Enter the command below for the n-Link STA
# ./wpa_cli i <vap_name> wps_pin <bssid> <wps_pin>
a. Wait for the STA to parse all the WPS Access Points. 5. For Generate PIN method, Enter the command below for the n-Link STA 63 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
#. /wpa_cli i <vap_name> wps_pin <bssid>
This will generate an 8-digit numeric WPS PIN. Enter the PIN on the Access Point Wait for the STA to parse all the WPS Access Points. 64 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 6 Configuration Using CFG80211 This section explains about the usage of various IOCTL commands, which can be issued to the Onebox-Mobile driver operating in CFG80211 mode from the user space. 6.1 Using iw Wireless Tool
'iw' is a new nl80211 based CLI configuration utility for wireless devices. It is used to set/get various parameters of a wireless network interface. This section covers the usage of 'iw' when used with the Onebox-Mobile driver. For a detailed description of 'iw' tool, please refer to the relevant man pages on Linux system. The list of supported commands via "iw" tool are listed below. Creating a virtual Interface Description This command is used to create a virtual interface in the specific mode requested by user Default Value
Input Parameters <phy name > Phy name can be obtained by using the following command
$ iw phy In case of multiple wireless interfaces are present, please refer to the NOTE given below on how to determine the phy name.
<interface name> name of the virtual interface to be created
<operating mode> operating mode of the virtual interface that can be either
'managed' for station mode or '__ap' for access point mode. Output Parameter
Reset Required No Usage Example Scan Default Value
iw phy <phy name> interface add <interface name> type <operating mode>
To create a virtual interface in Access Point mode, use the command given below:
$ iw phy phy0 interface add wifi0 type __ap To create a virtual interface in Station mode use the command below:
$ iw phy phy0 interface add wifi0 type managed Description This command is used to scan for the Access points nearby our device. Input Parameters Interface name on which scan has to be performed List of AP's scanned Output Parameter Reset Required No 65 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Usage The following command initiates a scan and displays the list of AP's scanned.
$ iw dev $interface_name scan Example
$ iw dev wifi0 scan This command is used to connect devices to the Access points in open or WEP security mode. Input Parameters SSID, BSSID, key_index, key of AP. Open mode:
$ iw dev $interface_name connect $SSID_NAME $BSSID. WEP Security:
$ iw dev $interface_name $ssid_name $bssid keyid:$key_index:$key
$ iw dev wifi0 connect REDPINE_AP 00:23:a7:00:05:55 The above command connects to REDPINE_AP access point in open mode
$ iw dev wifi0 REDPINE_AP 00:23:a7:00:05:55 keys d:1:234567890 The above command instructs our device to connect to the REDPINE_AP in wep64 mode with the key index 1 and key '234567890'. Description This command is used to disconnect our device from the connected network. Connect Description Default Value
Output Parameter None Reset Required No Usage Example Input Parameters Interface name Disconnect Default Value Output Parameter Usage Example
Reset Required No iw dev $interface_name disconnect
$ iw dev wifi0 disconnect The above command disconnects our device from the connected Access point. 66 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Description This command is used to get the connection status of our device. Link Status Default Value
Input Parameters Interface name. Connection status. Reset Required No Output Parameter Usage Example Interface Info iw dev $interface_name link iw dev wifi0 link iw dev $interface_name info iw dev wifi0 info Reset Required No Output Parameter Usage Example Station Dump Description Default Value
Input Parameters Interface name. Description This command is used to get information about the device . Default Value
Input Parameters Interface name. Interface mac address, type, operating mode etc. This command is used to station statistic information such as the amount of tx/rx bytes, the last TX bitrate (including MCS rate) Output Parameter Connected Stations/AP mac address,tx bytes, rx bytes, signal level etc,. will be displayed. Reset Required No Usage Example iw dev $interface_name station dump iw dev wifi0 station dump 67 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Description This command is used to set power save mode on/off in station mode. Set Power save mode Default Value
Input Parameters Interface name. Output Parameter No Reset Required No Get Power save mode Default Value
Input Parameters Interface name. Output Parameter Reset Required No Usage Example iw dev $interface_name set power_save <on | off>
iw dev wifi0 set power_save <on | off>
Description This command is used to get power save mode on/off in station mode. Shows whether power save mode is on | off in station mode Usage Example iw dev $interface_name get power_save iw dev wifi0 get power_save 68 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Note:
If there are multiple phys, i.e there are several instances of cfg80211 being used by different modules, then to determine the correct phy, run the following commands:
$ cat /sys/class/ieee80211/
This will give a list of all the phys that are currently active.
$ cat /sys/class/ieee80211/phyX/macaddress where 'X' is the number of the phys which are obtained from the previous command. The redpine module MAC address (xx:xx:xx:xx:xx:xx) has to be used in the field 'macaddress'. Generic iw commands listed below are also supported. Please refer to the man page of the utility for further information on their usage.
$ iw phy <phyname> info
$ iw dev <devname> del
$ iw reg get
$ iw reg set <ISO/IEC 3166-1 alpha2>
$ iw dev <devname> scan dump [-u]
$ iw phy <phyname> set name <new name>
The commands that are supported only in the Access Point mode are as follows:
$ iw dev <devname> set channel <channel> [HT20|HT40+|HT40-]
$ iw dev <devname> set freq <freq> [HT20|HT40+|HT40-]
$ iw dev <devname> station del <MAC address>
$ iw dev <devname> station get <MAC address>
Limitation:
In STA alone mode, after connection iw reg set command is not expected. If this command is given then whatever country code is given in command will be applicable. In this case it may possible that STA may disconnect from connected AP. e.g. STA is connected to AP in JP (Japan region) on channel 14. If user is giving command iw reg set US then channels will be limited to 1-11 and STA will disconnect from AP and will be looking for AP in those channels only by running scan. 69 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 7 Enterprise security using CFG80211 7.1 Installation and configuration of FREERADIUS Server The following packages are required to install the freeradius server 3.09:
libtalloc-devel openssl-devel The steps for downloading as well as installing the freeradius tar ball are as follows:
$ tar zxvf freeradius-server-3.0.9.tar.gz
$ cd freeradius_3.09
$ ./configure
$ make
$ make install Configure the freeradius server as per the given steps below:
Edit users file, which will contain the identity and password.
$ vim /usr/local/etc/raddb/users Add the following line at the starting in the users file test Cleartext-Password := "password"
2. As an example, user1 is an identity and test123 is the password that has to be entered at client side i.e. in the sta_settings.conf file. 3. Now we need to edit eap file which contains the paths consisting of certificates and information about the EAP-
Methods supported
$ vim /usr/local/etc/raddb/mods-enabled/eap If Free-radius version is below 3.x eap, it will be located in raddb folder and will be named as eap.conf. In tls-config tls-common section, changes are made to point to our certificates which are placed in /etc/certs folder 70 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 tls-config tls-common {
#private_key_password = whatever private_key_password = Wi-Fi
#private_key_file = ${certdir}/server.pem private_key_file = /etc/certs/wifiuser.pem
#certificate_file = ${certdir}/server.pem certificate_file = /etc/certs/wifiuser.pem
#ca_file = ${cadir}/ca.pem ca_file = /etc/certs/wifiuser.pem
#dh_file = ${certdir}/dh dh_file = /etc/certs/dh
To start the Radius server, run the flowing command in the terminal:
$ radiusd -X For openssl versions of range 1.0.2 release - 1.0.2h release (or) in range 1.0.1 - 1.0.1t release
(or) in range 1.1.0 - 1.1.0a release edit radiusd.conf file
$vim /usr/local/etc/raddb/radiusd.conf and change 'allow_vulnerable_openssl' to yes or CVE-2016-6304 allow_vulnerable_openssl =yes
(or) allow_vulnerable_openssl ='CVE-2016-6304'
(here CVE-2016-6304 is openssl vulnerability ID which radius server will allow) 7.2 Configuration of AP and RADIUS server to use EAP methods Hostapd is used as the RADIUS Server. The AP and the server are co-located (in the same system). The following packages which have to be installed are as follows:
libnl-devel libsqlite3x-devel 71 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 openssl-devel 7.2.1 Configuration of the AP Go to driver source folder and compile it with the following options enabled:
[*] NL80211 support
[*] HOSTAPD support
$ make To start the device in AP mode, go to the release folder and run the following commands:
$ cd release
$ sh wlan_enable.sh or wlan_bt_insert.sh or wlan_zigb_insert.sh or onebox_insert.sh script present in the release folder as per the instructions mentioned in Section 4.1.
$ iw phy phyX interface add wifi1 type __ap where 'X' represents phy number. It can be obtained by the following command:
$ iw list | grep phy Before starting the device in AP mode, ensure that in hostapd_eap.conf the following entities are enabled:
ieee8021x=1 own_ip_addr=192.168.2.1 /* IP address of AP */
/* RADIUS authentication server */
auth_server_addr=127.0.0.1 auth_server_port=1812 auth_server_shared_secret=testing123 /* shared secret must be the same as in /etc/hostapd.radius_clients file */
Run the following command to start the device in the AP mode:
72 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
$. /hostapd hostapd_eap.conf -ddddt >log &
$ sh dhcp_server.sh wifi1 , where wifi1 is the interface name 7.2.2 Configuring hostapd as RADIUS server The steps for configuring hostapd as RADIUS server are as follows:
Copy the certs folder in /etc location, which will contain the certificates, hostapd.radius_clients, hostapd.eap_user and dh files. Go to driver folder and copy the certs folder to the /etc location in your system Check whether the interface in hostapd_server.conf is same or not as the name of AP interface name.
$ cp -rvf certs /etc/
Example
$ vim hostapd_server.conf interface = wifi1 ,so that RADIUS server will listen on that interface name. Start the RADIUS server after AP had started in a new terminal.
$./hostapd hostapd_server.conf -ddddd All the Credentials will be in /etc/certs/hostapd.eap_user file. A sample hostapd.eap_user file is present in the certs.tgz in the release folder. The /etc/certs/hostapd.radius_clients file contains the IP required to communicate the shared secret between AP and RADIUS server. Here it is co-located, hence it is the loop-back address. 7.2.3 Configuring Station to connect to an EAP enabled AP. Go to Driver Folder and copy the certs folder to /etc/ in your system, as it contains all the certificates required.
$ cp -rvf certs /etc/
Go to the driver folder and compile it, ensuring that the below options are enabled in wpa_supplicant.conf file.
$ vim wlan/supplicant/linux/wpa_supplicant/.config 73 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 CONFIG_DRIVER_NL80211=y CONFIG_IEEE8021X_EAPOL=y CONFIG_EAP_MSCHAPV2=y CONFIG_EAP_TLS=y CONFIG_EAP_PEAP=y CONFIG_EAP_TTLS=y CONFIG_EAP_FAST=y CONFIG_EAP_LEAP=y CONFIG_PKCS12=y CONFIG_TLS=internal Ensure that in menuconfig, NL80211 support is enabled. Compile the driver. Go to the release folder and start the device in station mode.
$ make
$ cd release
$ sh wlan_enable.sh or wlan_bt_insert.sh or wlan_zigb_insert.sh or onebox_insert.sh script present in the
"release" folder as per the instructions in Section 4.1
$ service NetworkManager stop
$ iw phy phyX interface add wifi0 type managed X is the phy number it will vary to get it type $ iw list |grep phy. Run the supplicant after configuring sta_settings.conf according to the required EAP method. The network blocks listed below can be used as a reference.
$ ./wpa_supplicant -i wifi0 -D nl802ll -c sta_settings.conf -ddddt > log &
To connect using EAP-PEAP method, sta_settings.conf should be described as below:
network={
ssid="Redpine_Signals"
key_mgmt=WPA-EAP eap=PEAP anonymous_identity="peapuser"
identity="test"
password="password"
74 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 To connect using EAP-TTLS method, sta_settings.conf should be described as below:
To connect using EAP-TLS method, sta_settings.conf should be described as below:
network={
ssid="Redpine_Signals"
key_mgmt=WPA-EAP eap=TTLS anonymous_identity="ttlsuser"
identity="test"
password="password"
network={
ssid="Redpine_Signals"
key_mgmt=WPA-EAP eap=TLS anonymous_identity="tlsuser"
identity="test"
password="password"
ca_cert="/etc/certs/wifiuser.pem"
client_cert="/etc/certs/wifiuser.pem"
private_key_passwd="Wi-Fi"
private_key="/etc/certs/wifiuser.key"
network={
ssid="Redpine_Signals"
key_mgmt=WPA-EAP eap=FAST anonymous_identity="fastuser"
identity="test"
password="password"
phase1="fast_provisioning=1"
pac_file="/etc/p1.pac"
phase2="auth=mschapv2"
ca_cert="/etc/certs/wifiuser.pem"
private_key_passwd="wifi"
To connect using EAP-FAST method, sta_settings.conf should be described as below:
EAP-LEAP has been used when Freeradius is the RADIUS Server. This has been verified with only Cisco AP. To connect using EAP-LEAP method, sta_settings.conf should be described as below:
75 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 To connect using EAP-LEAP for CCX, sta_settings.conf should be described as below:
network={
ssid="Redpine_Signals"
key_mgmt=WPA-EAP eap=LEAP identity="user1"
password="test123"
network={
ssid="Redpine_Signals"
key_mgmt=WPA-CCKM eap=LEAP identity="user1"
password="test123"
pairwise=TKIP group=TKIP proto= WPA2 WPA scan_ssid=1 priority=2
$ radiusd -X 76 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 8 HOSTAPD and Wi-Fi Protected Setup (WPS) This section describes how the WPS implementation in hostapd can be configured and how an external component on an AP is used to enable enrollment of client devices. WPS uses the following terms to describe the entities participating in the network setup:
Access Point: WLAN access point Registrar: A device that controls a network and can authorize addition of new devices. This may be either in the AP
("internal Registrar") or in an external device, e.g., a laptop, ("external Registrar") Enrollee: A device that is being authorized to use the network It should also be noted that the AP and a client device may change roles (i.e., AP acts as an Enrollee and client device as a Registrar) when WPS is used to configure the access point.) 8.1 Hostapd Configuration before Compilation WPS component needs to be enabled in hostapd build configuration (.config) i.e: vim host/wlan/hostapd-2.3/hostapd/.config Ensure that the below mentioned entities are enabled in .config file CONFIG_WPS=y CONFIG_WPS2=y CONFIG_WPS_UPNP=y 8.2 Configuration in hostapd_wps.conf driver=nl80211 interface=wifi1; wifi1 is the name of the interface
# WPA2-Personal configuration for the AP ssid=wps-test wpa=2 wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP
# Default WPA passphrase for legacy (non-WPS) clients wpa_passphrase=12345678
# Enable random per-device PSK generation for WPS clients
#wpa_psk_file=/etc/hostapd.wpa_psk 77 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Check if the hostapd.wpa_psk file present in /etc/, if not, then create a new empty file naming hostapd.wpa_psk in location (/etc/ ).
# Enable control interface for PBC/PIN entry ctrl_interface=/var/run/hostapd
# Enable internal EAP server for EAP-WSC (part of Wi-Fi Protected Setup) eap_server=1 wps_state=2 ap_pin=12345670 wps_pin_requests=/var/run/hostapd_wps_pin_requests
$ sh wlan_enable.sh or wlan_bt_insert.sh or wlan_zigb_insert.sh or onebox_insert.sh script present in the release folder as per the instructions mentioned in Section 4.1 8.3 WPS 8.3.1 AP-mode for WPS -push button method
$ is phi ; it will give phyX number
$ iw phy phyX interface add wifi1 type __ap
$ ./hostapd hostapd_wps.conf -ddddddt>log &
$ sh dhcp_server.sh wifi1
$ ./hostapd_cli wps_pbc Now push wps button on station side. At this point, the client has two minutes to complete WPS negotiation 8.3.2 AP-mode for WPS Enter-pin method
$ sh wlan_enable.sh or wlan_bt_insert.sh or wlan_zigb_insert.sh or onebox_insert.sh scripts present in the release folder as per the instructions mentioned in Section 4.1 78 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
$ iw phy ; it will give phyXX number
$ iw phy phyXX interface add wifi1 type __ap
$ /hostapd hostapd_wps.conf -ddddddt>log &
$ sh dhcp_server.sh wifi1
./hostapd_cli wps_pin any [wps-pin-of station]
$ ./hostapd_cli wps_pin any 12345670
$ iw phy ; it will give phyXX number
$ iw phy phyXX interface add wifi1 type __ap
$ ./hostapd hostapd_wps.conf -ddddddt>log &
$ sh dhcp_server.sh wifi1
$ hostapd_cli wps_ap_pin random [timeout]
8.3.3 AP-mode for WPS-Generate pin- method
$ sh wlan_enable.sh or wlan_bt_insert.sh or wlan_zigb_insert.sh or onebox_insert.sh script present in the release folder as per the instructions mentioned in section 4.1 The above command generates a random AP pin number. If the optional timeout parameter is given then the AP pin will be enabled for the specified number of seconds.
$ ./hostapd_cli wps_ap_pin random 300 The above command generates a 8digit random pin which needs to be entered at the station side using the procedure mentioned below. Here AP acts as an Enrolee and client device as a Registrar, so ensure that the below mentioned entities are enable at the STATION side. PATH: host/wlan/supplicant/linux/wpa_supplicant/.config CONFIG_DRIVER_NL80211=y CONFIG_WPS=y CONFIG_WPS2=y CONFIG_WPS_ER=y 8.3.4 Disable AP pin To disable AP Pin, enter the command given below:
79 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
$ hostapd_cli wps_ap_pin disable The command disables AP PIN (i.e., it does not allow external Registrars to use it inorder to learn the current AP settings or to reconfigure the AP). 8.3.5 Get the AP pin To fetch the current AP pin enter the command given below:
$ hostapd_cli wps_ap_pin get 8.3.6 Set the AP pin
$ hostapd_cli wps_ap_pin set <PIN> [timeout]
Sets the AP PIN and enables it. 8.3.7 Get the current configuration
$ hostapd_cli get_config The above command displays the current configuration of the AP mode If the optional timeout parameter is given, the AP PIN will be enabled for the specified number of seconds. 80 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 9 ACS with Hostapd 1. Compilation Steps:
Following steps should be followed for Auto Channel Selection using Hostapd:
a. Enable CONFIG_ACS in Driver Makefile b. Enable Hostapd and NL80211 in make menuconfig c. Enable CONFIG_ACS in hostapd .config file. (wlan/hostapd/hostapd-2.4/hostapd/.config) d. Compile the driver using make command 2. Hostapd Conf File changes required for ACS:
Set the correct interface and driver in hostapd.conf file (driver will be nl80211 for this) interface=wlan0 driver=nl80211 Set SSID you want to configure ssid=REDPINE Set hw_mode to g for 2.4 GHz hw_mode=g channel=0 Set channel=0 (For ACS this value should be zero. Hostapd will pick a channel depending upon survey dump from driver) Select the number of scans to be performed to trigger survey data commands. Hostapd will call this much times for new survey data acs_num_scans=5 (Default Value) Steps for Setting AP Insert the driver and create AP interface using wlan_enable.sh and post_vap.sh 1. 2. Up the ap interface created 3. Run the following command to run hostapd:
./hostapd hostapd.conf ddd > log_file_name &
81 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 10 Antenna Diversity 10.1 Introduction 10.2 Configuration RSI_ANTENNA_DIVERSITY=1 Antenna diversity is a feature which enables the automatic selection of the antennas which is needed to be use. The antenna on which the packets with better RSSI values are received is selected. The RSSI monitoring happens continuously. Once it is enabled, this feature will persist for the entire duration of operation. The steps described in this section are used to start the antenna diversity feature in Client mode only. Once it is enabled, the antenna selection happens automatically:
1. Open the common_insert.sh file present in the release folder. 2. Ensure that the variable RSI_ANTENNA_DIVERSITY is set as given below:
When Antenna Diversity is enabled, User has to make sure that external antenna is connected to the module. Without connecting the external antenna the behavior may be unspecified 82 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 11 Sniffer Mode The Steps for operating the device in Sniffer Mode are outlined below. Ensure that the common_insert.sh present in the release folder has valid driver mode and coexistence mode. DRIVER_MODE=7 (Sniffer mode) COEX_MODE = 1 (Wi-Fi station/ Wi-Fi-Direct/Wlan-Per/Sniffer) Go to the release folder and start the driver modules by using the given below command
# sh wlan_enable.sh Create the virtual interface in monitor mode.
# ./onebox_util <base_interface> create_vap wifi0 mon For NL80211 mode , Set Country code with the following command
# iw reg set <Country_code>
Ex : # iw reg set JP This command will set country to Japan To select the channel, use the given below command.
# iwconfig <interface_name(wifi0)> freq <Frequency_in_Ghz>
To start capturing the packets, use the given below command.
# ifconfig <interface_name (wifi0)> up Use tcpdump or wireshark tools to observe the packets being captured by the device. 83 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 12 Monitor Mode The Monitor Mode is one of the operating modes that can be set while creating a VAP. It enables capturing of packets which is transferred over a single or multiple VAPs and are operating in either Access Point or Client or P2P modes. The order of the VAPs' creation does not matter. Once it is created, the "tcpdump" command can be used to display the packets which are being transferred. Monitor mode VAP should be enabled after enabling all other VAP's. Example Scenario 1: Create a Client mode VAP and a Monitor mode VAP and display packets which are being transferred to/from the Client Example Scenario 2: Create an Access Point mode VAP, a Client mode VAP and a Monitor mode VAP and display the packets which are being transferred to/from the Access Point and Client. /onebox_util rpine0 create_vap wifi0 sta sw_bmiss
./onebox_util rpine0 create_vap wifi1 mon ifconfig wifi0 up ifconfig wifi1 up tcpdump i wifi1
./onebox_util rpine0 create_vap wifi0 ap
./onebox_util rpine0 create_vap wifi1 sta sw_bmiss
./onebox_util rpine0 create_vap wifi2 mon ifconfig wifi0 up ifconfig wifi1 up ifconfig wifi2 up tcpdump i wifi2 The difference between Sniffer and Monitor modes is explained below:
Monitor mode displays the packets which are being transferred to/from the device and are configured in different operating modes like Access_point, Client and so on. Where as, Sniffer mode displays all the packets on air depending on the channel and band width configured and displays them using wire shark tool. 84 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 13 Concurrent Mode Concurrent mode is the mechanism in which Onebox-Mobile can be operated in AP and Client modes simultaneously.User can create a virtual interface as client mode on one interface and as AP mode on other interface. Below are the Steps to operate the device in concurrent Mode. Ensure that common_insert.sh present in the release folder has valid driver mode and coexistence mode. DRIVER_MODE=1 (End to End mode) COEX_MODE = 3 (AP + Station -on multiple vaps) 13.1 Installation Procedure 13.1.1 Creating VAP in Client Mode cd /home/rsi/release
$ sh wlan_insert.sh Insert the driver using script wlan_insert.sh which is present in following folder. Create VAP in client mode using command.
$. /onebox_util rpine0 create_vap <vap name> sta sw_bmiss For example: ./onebox_util rpine0 create_vap wifi0 sta sw_bmiss After issuing the above command virtual interface with the specified interface name wifi0 will be created. User can view the list of interfaces using the following command. ifconfig -a Make sure the appropriate settings are present in the sta_settings.conf file. Please refer the section 4.4.1 for the configuration details for different security modes. After the configuration settings run the supplicant using the following command
$. /wpa_supplicant i <vap_name> Dbsd c sta_settings.conf ddddt >log&
Ex:./wpa_supplicant i wifi0 Dbsd c sta_settings.conf ddddt >log&
For example: If user creates the virtual interface with the name wifi0 in client mode then the supplicant should be run on that interface only 85 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 13.1.2 Creating VAP in AP mode Create VAP in AP mode using command:
$. /onebox_util rpine0 create_vap <vap_name> ap Ex:./onebox_util rpine0 create_vap wifi1 ap After issuing the above command virtual interface with name wifi1 will be created. User can view the list of interfaces using the following command. ifconfig a User needs to enable the appropriate network block settings with the information about the Access point configuration. To configure the Access Point in different security modes use the configuration file settings. Please refer to the section on Security for the configuration files for different security modes Here the virtual interface name is referred as wifi1. User can create the virtual interface with any name of his choice The steps to be followed in order to recognize the expected concurrent mode operation are outlined below:
1. Boot the RPINE device in STA mode and wait for it to connect to the 3rd party AP. 2. Then start the AP mode, and connect a 3rd party station. 3. In case the 3rd party AP shuts off, or the RPINE STA for some reason is disconnected, the STA will NOT move into scan phase. 4. We can now scan for the 3rd party AP using the host based scan command,
"./onebox_util rpine0 host_scan <periodicity> <active scan duration> <no of channels>
<list of channels....>"
a. Periodicity : This parameter specifies the interval between the scans. The unit of this field is seconds. Setting the value of this field as 0 will disable scans. b. Active scan duration : This parameter determines the duration of the active scan in each channel during the on-demand scan process. The recommended value for this parameter is 20ms for quicker scan operations and uninterrupted throughput. The maximum allowed value for this parameter is 255ms. c. No of channels : Specifies the no of channels to scan d. List of channels : The list of channels in which the scan is to be performed Example: ./onebox_util rpine0 host_scan 5 30 3 1 6 11. This commands enables host based scan, with a periodicity of 5 seconds, active scan duration of 30ms in the channels 1, 6 & 11. 1. Note, we do not have support for passive scan duration as of now. 2. When the STA is successfully able to connect to the AP, the user can stop the scan by setting the periodicity to "0". 3. Even if the user DOES NOT stop the scan after the RPINE STA is connected to the AP, use of the scan command on successive disconnections is a MUST. The host_scan command should be issued only when the AP VAP is also UP. It is also possible that STA can connect to the 3rd party AP without host_scan command and having AP VAP already UP. This case is possible due to the process that STA will continuously listen to beacons being received in the present channel. If any AP beacon matches with sta_settings, STA will start connection procedure. But for this to happen 3rd party AP should also be in the same channel in which RSI AP & RSI STA are UP. 86 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 In the case The following command scans all the 2G channels, 1-14 with periodicity of 5 seconds and active scan duration of 30ms. 1. /onebox_util rpine0 host_scan_2g 5 30 The following command stops the host based scan. 2. /onebox_util rpine0 host_scan_stop User can create the client mode first followed by AP mode or viceversa.If driver is unloaded in between the virtual interfaces created so far will be removed.For deleting particular virtual interface please follow th e below command.
$. /onebox_util rpine0 delete_vap <vap_name>
Ex: ./onebox_util rpine0 delete_vap wifi0 You can create two VAPs at a time and then run corresponding supplicant command because supplicant command will be differentiated by using the interface name user has mentioned while creating VAP. 13.1.3 State of the Station To check the Station state, Use the below command. /onebox_util rpine0 check_sta_state The possible outputs are, 1. INIT 2. SCAN 3. AUTH 4. ASSOC 5. RUN 6. DOWN Error Msg:
In case the driver is unable to issue the ioctl, then the error message displayed as : "ERROR! Unable to check STA State"
Description of output states, 1. INIT: This stage indicates, the STATION VAP is up, but it is not scanning. In case the station 87 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 disconnects from the AP, by default it will move to the INIT state. The user is expected to give the host_scan command to initiate scanning. 2. SCAN: In This state the device performs scan and sends the scan results to the supplicant. In the STA alone mode, the scan request from the supplicant is sufficient for the STA to move to this state. In case AP is running and the STA is started, then the user has to give the host_scan command for the STA to move to this state. 3. AUTH: This is an intermediate state during connection. Once the STA collects the SCAN results and sends to the supplicant, if any desired BSS is found, then the STA moves to this state to complete authentication. 4. ASSOC: Once the AUTH is successful, the STA moves to the ASSOCIATION State. 5. RUN: Once the ASSOCIATION is successful, the STA moves to RUN state and the user can co-relate this to Connection Established. Once the STA enters into the RUN state, it automatically disables the host_scan command, i.e the device no longer performs the SCAN even if the user hasn't explicitly sent the scan stop command. If the user wishes to continue the SCAN he must initiate it again. 6. DOWN: If the STA VAP is not up, then the output is DOWN Flow chart Limitations 88 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 AP will always operate in channel in which the client [corresponding to other VAP] connects. For eg: In case if client connects in ch6 then AP mode will get created in ch6 irrespective of the channel configured.Similarly if AP mode is started first in the user configured channel and client mode is started later, then AP switches to the channel in which client is finally connected. However AP and client can operate in different security modes. If station disconnects then the AP mode would also not be operational [i.e the AP stops beaconing and disconnects all of the connected stations. Background scan(Bg-scan) and powersave features are not supported for the station mode vap in concurrent mode. In NL80211 mode, STA VAP has to be settled first (i.e. should be connected) to use proper country code. Whatever country of STA VAP's AP (third party AP to which STA is connected), that will be advertised in Beacons of AP VAPs. If AP VAPs were created first then also whatever country will be of 3rd party connected AP, that will be updated in our AP VAP's beacon. In NL80211 mode, If Multiple AP VAPs only created then all VAP should have same country code. In this case whichever AP will start first with country code, same will be use for others also. 89 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 14 Background Scan Parameters This section describes the various parameters for the Background scan commands that can be sent to the n-Link Client using the onebox_util program.
<bgscan_threshold>: The Background scan threshold is referred to as the RSSI Upper Threshold. At every background scan interval (configured via <periodicity>), the n-Link module decides whether to initiate or not to initiate a background scan based on the connected Access Points RSSI. The module initiates a background scan if the RSSI of the connected Access Point is below this threshold. The input value should be the absolute value in dBm.
<rssi_tolerance_threshold>: If the difference between the current RSSI value of the connected Access Point and the RSSI value of the Access Point from the previous background scan is greater than the RSSI Tolerance Threshold, then the module performs a background scan. Assigning a large value to this field will eliminate this method of triggering background scans.
<periodicity>: This parameter specifies the interval between the background scans. The unit of this field is seconds. Setting the value of this field as 0 will disable background scans.
<active_scan_duration>: This parameter determines the duration of the active scan in each channel during the Background scan process. The recommended value for this parameter is 20ms for quicker Background scan operation and uninterrupted throughput. The maximum allowed value for this parameter is 255ms.
<passive_scan_duration>: This parameter determines the duration of the passive scan in each configured channel.The maximum allowed value for this parameter is 255ms.
<two_probe_enable>: If this feature is enabled, the Client sends two probe requests to the Access Point. This is useful when scanning is carried out in channels with high traffic. The valid values are a. 0 Disable b. 1 Enable
<num_of_bgscan_channels>: Specifies the number of Background scan channels. The n-Link module supports up to 24 channels.
<channels_to_scan>: The list of channels in which Background scan has to be performed 90 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 15 Power save Modes, Profiles and Parameters The Power save modes and parameters are valid only for the Client mode. By default, the module's power save is disabled. 15.1 Power save Modes The module broadly supports two types of power save modes. They are outlined below:
Low Power (LP) Mode: The PHY (RF and Baseband) and LMAC sections are powered off but the UMAC and Host Interface sections of the module are powered on and fed a low frequency clock. The module responds to commands/requests from the Host processor immediately in this mode. Ultra-low Power (ULP) Mode: A majority of the module is powered off except for a small section which has a timer and interrupts logic for waking up the module. The module cannot respond to the Host processor's commands/requests unless and until it gets wake up because of timeout or because of an interrupt asserted by Host processor. The sleep entry/exit procedures in this mode are indicated to the Host processor either through a packet based or signal based handshake. This mode is supported only for SDIO host interface. Out of two ULP Handshake Modes (GPIO (signal) based or Message (packet) based), GPIO based mode is more effective. If target platform does not have free/spare GPIO, they can use message based mode. 15.2 Power save Profiles For each of the above power save modes, the module supports multiple power save profiles. They are outlined below:
Deep Sleep: The module is in deep sleep mode when it is not connected to an Access Point. The duration of the Deep Sleep is defined by the <sleep_duration> parameter of the set_ps_params command. For LP mode, a value of 0 for the <sleep_duration> parameter programs the module to be in Deep Sleep mode indefinitely till it is woken up by the Host processor via the host interface. The value of 0 is invalid for ULP mode and should not be used. Connected Power Save: In the connected state, the module can operate in Traffic Based Power Save Profile
(PSP) or Fast PSP. These profiles are used by the module to decide when to enter and exit from power save modes on the fly. They have to be selected based on the performance and power consumption requirements of the end product. Traffic Based PSP: This profile is dependent on the <tx_threshold> and <rx_threshold> parameters, which indicate transmit and receive throughput thresholds beyond which the module exits power save mode and below which the module enters power save mode. The <tx_hysteresis> and <rx_hysteresis> parameters are also used in this profile. This profile is enabled when non-zero values are assigned to the <tx_threshold> and
<rx_threshold> parameters along with the <monitor_interval> parameter. Fast PSP: This profile is a variant of the Traffic Based PSP which exits power save mode even for a single packet and enters the power save mode if no packet is transferred for the <monitor_interval> amount of duration. This profile is enabled independently for the Transmit and Receive directions if the <tx_threshold>
and <rx_threshold> parameters are assigned zero, respectively, while assigning a non-zero value to the
<monitor_interval> parameter. 15.3 Wakeup Procedures and Data Retrieval When in power save mode, the module wakes up at periodic intervals or due to certain events (like pending transmit packets from the Host). At every wake up, the module has to poll the Access Point and check whether there are any pending Rx packets destined for the module. The module uses different protocols to retrieve data from the Access Point based on the protocol supported by the Access Point. These data retrieval methods
(protocol-based) are used to further classify the power save profiles described in the previous section into Max PSP, Periodic UAPSD and Transmit based UAPSD. The MAX PSP and UAPSD modes are explained below:
91 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Max PSP: In this mode, the module wakes up at the end of sleep period (Listen or DTIM interval) and retrieves pending Rx packets from the Access Point by sending a PS-POLL packet. It also transmits any packets received from the Host processor and then goes back to sleep. The parameters listed below are used by the module to decide the period of sleep during power save, in the same order of priority:
a. <listen_interval_duration>
b. <dtim_interval_duration>
c. <num_beacons_per_listen_interval>
d. <num_dtims_per_sleep>
Periodic UAPSD: This mode is enabled by the set_uapsd_params command only if the
<uapsd_wakeup_period> parameter is assigned with a non-zero value. For this mode, the wakeup period can be assigned with a value ranging between 10 and 100 milliseconds. If it is supported by the Access Point, then in this mode, the module wakes up at the end of each sleep period and transmits pending data or a QoS Null packet in order to retrieve the data from the Access Point. The sleep period is governed by the parameter set which is using commands like set_ps_params command (see the list under Max PSP above) and also set_uapsd_params command. The sleep period has the minimum of the values programmed using the above two commands. If the Access Point does not support UAPSD, the module tries to mimic this mode by waking up at the end of the sleep period and transmits pending data and a PS_POLL packet to retrieve the data from the Access Point. Transmit based UAPSD: If <uapsd_wakeup_period> parameter is set to 0 in the set_uapsd_params command, the Transmit based UAPSD mode is enabled. In ULP mode, the Transmit based UAPSD mode can be used only when the signal-based handshake is enabled (and not in packet-based handshake mode). In this mode, the module wakes up from sleep when the Host sends a packet to be transmitted and then retrieves the pending packets from the Access Point by transmitting the packet. The module also wakes up if there is no packet transmitted for the sleep duration programmed in the set_ps_params command. If the Access Point does not support UAPSD, the module mimics this mode by waking up whenever there is a packet to be transmitted. It generally transmits the packet and then retrieves the pending data from the Access Point by sending a PS_POLL packet. 15.4 Power save Parameters The input parameters of the set_ps_params command are explained below.
<ps_en>: This parameter is used to enable (1) or disable (0) power save mode.
<sleep_type>: This parameter is used to select the sleep mode between LP (1) and ULP (2) modes.
<tx_threshold>: If a non-zero value is assigned, this parameter is used to set a threshold for the Transmit throughput computed during the <monitor_interval> period so that the module can decide to enter
(throughput threshold) or exit (throughput > threshold) the power save mode. The value is in Mbps and Supported TX threshold is 0 to 10Mbps
<rx_threshold>: If a non-zero value is assigned, this parameter is used to set a threshold for the Receive throughput computed during the <monitor_interval> period so that the module can decide to enter
(throughput threshold) or exit (throughput > threshold) the power save mode. The value is in Mbps and Supported RX threshold is 0 to 10Mbps
<tx_hysteresis>: The decision to enter or exit power save mode based on the Transmit throughput alone can result in frequent switching between the power save and non-power save modes. If this is not beneficial, the <tx_hysteresis> parameter can used to make the module re-enter the power save mode only when the throughput falls below the difference between the <tx_threshold> and <tx_hysteresis> values. The value is in Mbps and minimum value is 0 Mbps. This parameter should be assigned a value which is less than the value assigned to the <tx_threshold> parameter.
<rx_hysteresis>: The decision to enter or exit power save mode based on the Receive throughput which alone can result in frequent switching between the power save and non-power save modes. If this is not beneficial, the <rx_hysteresis> parameter can be used to make the module re-enter the power save mode only when the throughput falls below the difference between the <rx_threshold> and <rx_hysteresis>
92 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 values. The value is in Mbps and minimum value is 0 Mbps. This parameter should be assigned a value which is less than the value assigned to the <rx_threshold> parameter.
<monitor_interval>: This parameter specifies the duration (in milliseconds) over which the Transmit and Receive throughputs are computed to compare with the <tx_threshold>, <rx_threshold>, <tx_hysteresis>
and <rx_hysteresis> values. The maximum value of this parameter is 30000 ms (30 seconds).
<sleep_duration>: This parameter specifies the duration (in milliseconds) for which the module sleeps in the Deep Sleep mode. For LP mode, a value of 0 for the <sleep_duration> parameter programs the module to be in Deep Sleep mode indefinitely till it is woken up by the Host processor via the host interface. The value of 0 is invalid for ULP mode and should not be used. The maximum value for this parameter can be 65535.
<listen_interval_duration>: This parameter specifies the duration (in milliseconds) for which the module sleeps in the connected state power save modes. If a non-zero value is assigned to this parameter it takes precedence over the other sleep duration parameters that follow (<num_beacons_per_listen_interval>,
<dtim_interval_duration>, <num_dtims_per_sleep>). The maximum duration for which the device supports sleep is 4095 times the duration of the beacon interval considering the listen interval parameters of the access point. The maximum value for this parameter can be 65535, but the duration should be the deciding factor in the beacon interval of the access point. This parameter is considered only after the module is connected to the access point. For example, if the beacon interval of the AP is 100ms and listen interval of AP is 8 beacons, then the maximum time the device can sleep without any data loss is 800 ms (8 * 100). Hence, the listen_interval_duration can be up to 800ms.
<num_beacons_per_listen_interval>: This parameter specifies the number of beacon intervals for which the module sleeps in the connected state power save modes. Here, the device will wake up for the nth beacon, where n is the listen interval value programmed by the user. If a non-zero value is assigned to this parameter it takes precedence over the other sleep duration parameters that follow
(<dtim_interval_duration>, <num_dtims_per_sleep>). This parameter is used only when the above parameter is assigned to 0. The maximum value for this parameter is 4095. The value for this parameter also has to be chosen keeping in mind the listen interval of the access point. This parameter is considered only after the module is connected to the access point.
<dtim_interval_duration>: This parameter specifies the duration (in milliseconds) for which the module sleeps in the connected state power save modes. The device will wake up for the nearest DTIM beacon after the time which the user has programmed expires. This parameter can be used when DTIM information is not available. If a non-zero value is assigned to this parameter, then it takes precedence over the other sleep duration parameter that follows (<num_dtims_per_sleep>). This parameter is used only when the above parameters are assigned 0. The maximum value for this parameter can be 10000ms. This parameter is considered only after the module is connected to the access point.
<num_dtims_per_sleep>: This parameter specifies the number of DTIM intervals for which the module sleeps in the connected state power save modes. This parameter has least priority compared to the ones above and is used only if the above parameters are assigned to 0. The maximum value for this parameter is 10. This parameter is considered only after the module is connected to the access point. The LP and ULP Power Save modes are supported with SDIO interface. USB interface supports only LP Power Save mode 15.5 Procedure to enable device power save for USB interface In order to enable power save for USB interface, following steps must be followed after enabling LP power save on USB interface. Find where the RSI module got detected. Eg: When RSI module is inserted, following prints are observed when dmesg is done. 93 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 usb 2-1: new high-speed USB device number 4 using ehci-pci usb 2-1: New USB device found, idVendor=1618, idProduct=9113 usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 usb 2-1: Product: Wireless USB Network Module usb 2-1: Manufacturer: Redpine Signals, Inc. usb 2-1: SerialNumber: 000000000001 It means Redpine module is detected as 2-1 device. Please make a note of this. Read the manufacturer of 2-1 device using following command.
#cat /sys/bus/usb/devices/2-1/manufacturer The output of this command should be Redpine Signals, Inc. Issue the following command to enable device power saves for RSI module in USB mode.
# echo 15 > /sys/bus/usb/devices/2-1/power/autosuspend_delay_ms Recommended delay is 15msec. 94 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 16 Compliance and Certification M4SBmodule is FCC/IC/CE certified. This section outlines the regulatory information for the M4SBmodule. This allows integrating the module in an end product without the need to obtain subsequent and separate approvals from these regulatory agencies. This is valid in the case no other intentional or un-intentional radiator components are incorporated into the product and no change in the module circuitry. Without these certifications, an end product cannot be marketed in the relevant regions. RF Testing Software is provided for any end product certification requirements. 16.1 Federal Communication Commission Statement This device complies with FCC Rules Part 15. Operation is subject to the following two conditions:
This device may not cause harmful interference. This device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a class B digital device, pursuant to Part 15 of the Federal Communications Commission (FCC) rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment causes harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by doing one or more of the following measures:
Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. FCC Caution Any changes or modifications not expressly approved by the party responsible for compliance could void the users authority to operate the equipment. The antenna(s) used for this transmitter must not be co-located or operating in conjunction with any other antenna or transmitter. Radiation Exposure Statement:
FCC Label Instructions:
This equipment must be installed and operated in accordance with provided instructions and the antenna(s) used for this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. The outside of final products that contains this module device must display a label referring to the enclosed module. This exterior label can use wording such as: Contains Transmitter Module FCC ID: XF6-M4SB,or Contains FCC ID: XF6-M4SB, Any similar wording that expresses the same meaning may be used. 16.2 Industry Canada / ISED Statement This product meets the applicable Innovation, Science and Economic Development Canada technical specifications. Ce produit repond aux specifications techniques applicables a l'innovation, Science et Developpement economique Canada. Radiation Exposure Statement:
This equipment complies with IC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20cm between the radiator &
your body. Dclaration dexposition aux radiations:
95 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Cet quipement est conforme aux limites dexposition aux rayonnements IC tablies pour un environnement non contrl. Cet quipement doit tre install et utilis avec un minimum de 20 cm de distance entre la source de rayonnement et votre corps. This device complies with Industry Canada license-exempt RSSs. Operation is subject to the following two conditions:
1) This device may not cause interference, and 2) This device must accept any interference, including interference that may cause undesired operation of the device. Le present appareil est conforme aux CNR dIndustrie Canada applicables aux appareils radio exempts de licence. Lexploitation est autorisee aux deux conditions suivantes :
1) lappareil ne doit pas produire de brouillage;
2) lutilisateur de lappareil doit accepter tout brouillage radioelectrique subi, meme si le brouillage est susceptible den compromettre le fonctionnement. 16.2.1 Labeling and User Information Innovation, Science and Economic Development Canada ICES003 Compliance Label: CAN ICES-3 (B)/NMB-3(B) The M4SBmodule has been labeled with its own IC ID number (8407A-M4SB) and if the IC ID is not visible when the module is installed inside another device, then the outside of the finished product into which the module is installed must also display a label referring to the enclosed module. This exterior label can use following wording: Contains Transmitter Module IC ID: 8407A-M4SBor Contains IC ID: 8407A-
M4SBUser manuals for license-exempt radio apparatus shall contain the above mentioned statement or equivalent notice in a conspicuous location in the user manual or alternatively on the device or both Le module M4SB a t tiquet avec son propre numro dID IC (8407A-M4SB) et si lID IC nest pas visible lorsque le module est install dans un autre priphrique, alors lextrieur du produit fini dans lequel le module est install doit galement afficher une tiquette faisant rfrence au module inclus. Cette tiquette extrieure peut tre libelle comme suit: Contient le module metteur ID IC: 8407A-M4SB ou contient l'ID IC: 8407A-M4SB. Les manuels d'utilisation d'appareils radio exempts de licence doivent contenir l'nonc susmentionn ou une notification quivalente un endroit bien en vidence dans le manuel d'utilisation. ou alternativement sur l'appareil ou les deux 16.3 Regulatory Module Integration Instructions List of applicable FCC rules This device complies with part 15.247 of the FCC Rules. Summarize the specific operational use conditions This module can be used in household electrical appliances as well as lighting equipment(s). The input voltage to the module should be nominally 1.8-3.3 Vdc,typical and the ambient temperature of the module should not exceed 85. This module using two kinds of antennas,PCB antenna with maximum gain is 1.00 dBi. Other antenna arrangement is not covered Limited module procedures Not applicable Trace antenna designs Not applicable RF exposure considerations This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance20cm between the radiator& your body. If the device built into a host as a portable usage,the additional RF exposure evaluation may be required as specified by 2.1093.by this certification.The antenna is not field replaceable. If the antenna needs to be changed,the certification should be re-applied. Antennas 96 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Provision for Chip Antenna or other Antennae Label and compliance information Already in the manual Information on test modes and additional testing requirements a) The modular transmitter has been fully tested by the module grantee on the required number of channels, modulation types, and modes, it should not be necessary for the host installer to re-test all the available transmitter modes or settings. It is recommended that the host product manufacturer, installing the modular transmitter,perform some investigative measurements to confirm that the resulting composite system does not exceed the spurious emissions limits or band edge limits (e.g., where a different antenna may be causing additional emissions). b) The testing should check for emissions that may occur due to the intermixing of emissions with the other transmitters, digital circuitry, or due to physical properties of the host product (enclosure). This investigation is especially important when integrating multiple modular transmitters where the certification is based on testing each of them ina stand-alone configuration. It is important to note that host product manufacturers should not assume that because the modular transmitter is certified that they do not have any responsibility for final product compliance. c) If the investigation indicates a compliance concern the host product manufacturer is obligated to mitigate the issue. Host products using a modular transmitter are subject to all the applicable individual technical rules as well as to the general conditions of operation in Sections 15.5, 15.15, and 15.29 to not cause interference. The operator ofthe host product will be obligated to stop operating the device until the interference hasbeen corrected 2.10 Additional testing, Part 15 sub part B disclaimer The final host / module combination need to be evaluated against the FCC Part 15Bcriteria for unintentional radiators in order to be properly authorized for operation as a Part15 digital device. Below are steps for TX verification Already in the manual Other in User Manual The host integrator installing this module into their product must ensure that the final composite product complies with the FCC requirements by a technical assessment or evaluation to the FCC rules, including the transmitter operation and should refer to guidance in KDB 996369. Frequency spectrum to be investigated For host products with certified modular transmitter, the frequency range of investigation of the composite system is specified by rule in Sections 15.33(a)(1) through (a)(3), or the range applicable to the digital device, as shown in Section 15.33(b)(1), whichever is the higher frequency range of investigation. Operating the host product When testing the host product, all the transmitters must be operating. The transmitters can be enabled by using publicly-available drivers and turned on, so the transmitters a reactive. In certain conditions it might be appropriate to use a technology-specific call box(test set) where accessory devices or drivers are not available.When testing for emissions from the unintentional radiator, the transmitter shall be placed in the receive mode or idle mode, if possible. If receive mode only is not possible then, the radio shall be passive
(preferred) and/or active scanning. In these cases, this would needto enable activity on the communication BUS (i.e., PCIe, SDIO, USB) to ensure the unintentional radiator circuitry is enabled. Testing laboratories may need to add attenuation or filters depending on the signal strength of any active beacons (if applicable)from the enabled radio(s). See ANSI C63.4, ANSI C63.10 and ANSI C63.26 for further general testing details. 97 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 17 Wi-Fi Performance Test ioctl usage The One Box-Mobile software provides applications to test Transmit and receive performances of the module. The Band of operation of the module needs to be configured before performing any tests. Also open the common_insert.sh file present in the "release" folder using an editor like vim. Ensure that below parameters are set as specified. DRIVER_MODE=2 POWER_SAVE_OPTION=0 STANDBY_ASSOC_CHAIN_SEL=0 LMAC_BEACON_DROP=0 Run the following command in order to install the Driver in Performance Test mode sh wlan_enable.sh or wlan_bt_insert.sh or wlan_zigb_insert.sh or onebox_insert.sh script 17.1 WiFi Transmit Tests The "transmit" utility, present in the "release" folder allows the configuration of the following parameters in order to start the transmission of packets. Transmit Power Transmit Data Rate Packet Length Transmit Mode External PA Enable/Disable This is not supported in the current release. Rate Flags like Short GI, Greenfield, etc. Enable/Disable Aggregation Number of packets to be transmitted in Burst Mode Delay between packets in Burst Mode Regulatory Domain 17.1.1 Transmit Command Usage The command usage is explained below
./transmit <base-interface> <tp> <r> <l> <m> <c> <p> <f> <a> <n> <d> <rd>
<base_interface>:This parameter specifies the Base Interface (string like rpine0).
<tp>: Transmit Power. To control transmit power in dBm units. To set the transmit power value; enter a value either between -7 and18. If a value of 127 is entered, the packet will be transmitted at the maximum power from the Transmit power table in the module.
<r>: Transmit Data Rate. To set the transmit data rate, select a value from 1, 2, 5.5, 11, 6, 9, 12, 18, 24, 36, 48, 54, mcs0, mcs1, mcs2, mcs3, mcs4, mcs5, mcs6 and mcs7.
<l>: Transmit packet length in bytes. Enter a value between 24 and 1536 when aggregation is not enabled and between 24 and 30000 when aggregation is enabled.
<m>: Transmit mode. Enter 0 for Burst mode and 1 for Continuous mode.
<c>: Cabled tests can be run in configured channels.. The following table maps the channel numbers to the center frequencies for 20MHz and 40MHz bandwidth modes in 2.4 GHz band. 98 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Band (GHz) Bandwidth (MHz) Channel Number Center Frequency (MHz) 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 20 20 20 20 20 20 20 20 20 20 20 20 20 40 40 40 40 40 40 40 40 40 1 2 3 4 5 6 7 8 9 3 4 5 6 7 8 9 10 11 12 13 10 11 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2422 2427 2432 2437 2442 2447 2452 2457 2462
<p>: Enable/Disable External PA. This parameter is not supported in the current release.
<f>: Rate Flags. This parameter is used to enable/disable Short GI and Greenfield and also to set the channel width of the transmitted packets. The table below explains the flags that can be enabled and disabled. Multiple flags can be set at a time. 99 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Bit Description Short GI 0 Disable Short GI 1 Enable Short GI Greenfield transmission 0 Disable Greenfield transmission 1 Enable Greenfield transmission Operating bandwidth of the channel (3 bits)
]]></ac:plain-text-body></ac:structured-macro>
0 20MHz 2 (Bit 3 is set) Upper 20MHz of 40MHz 4 (Bit 4 is set) Lower 20MHz of 40MHz 6 (Bits 3 and 4 are set) Full 40MHz This bit has to be set when the user selects 11J channel.
<a>: Enable/Disable Aggregation. Enter 0 to disable aggregation and 1 to enable aggregation. The packet length is divided into chunks of size 1792 bytes and aggregated. This parameter applies only to the Burst mode transmission and is ignored in the case of Continuous mode of transmission.
<n>: Number of packets to be transmitted in Burst mode. The transmission stops after the number of packets specified by this parameter are transmitted in the Burst mode. If this value is 0, then the transmission will not stop until the user gives the "./transmit 0" command inorder to stop the transmissions. This parameter is ignored in the case of Continuous mode of transmission.
<d>: Delay between packets in Burst mode. This parameter is used to specify a delay between any two packets. The delay has to be specified in microseconds. If this value is 0, then the packets will be transmitted without any delay. This parameter is ignored in the case of Continuous mode of transmission. After the transmission starts, the following commands need to be given to stop the transmissions.
<rd>: Regulatory Domain. Refer the table below for the mapping of values to the regulatory domains.
[4:2]
0 1 5 0 1 2 Input Value Regulatory Domain US (FCC) Europe (ETSI) Japan(JP) 255 World Domain Examples:
100 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
#. /transmit rpine0 2 5.5 750 1 11 0 1 0 0 0 0 The above command starts continuous transmission with the following configuration:
Transmit gain 2dbm Data rate 5.5Mbps Packet Length 750 bytes Transmit mode 1 (continuous mode). Channel number 11 External PA disabled Rate flags 1 (Short GI is enabled with 20MHz Channel width) Aggregation disabled (ignored in continuous mode) Number of packets to be transmitted 0 (ignored in continuous mode) Delay between the packets 0 (ignored in continuous mode)
#. /transmit 12 36 1000 0 6 0 25 0 1000 0 0 The above command starts burst mode transmission with the following configuration:
Transmit gain 12dBm Data rate 36Mbps Packet Length 1000 bytes Transmit mode 0 (Burst mode). Channel number 6 External PA disabled Rate flags 25 (Short GI with Full 40MHz Channel width) Aggregation disabled Number of packets to be transmitted 1000 Delay between the packets 0 17.2 Wi-Fi Receive Tests Total number of CRC PASS packets Total number of CRC FAIL packets and Total number of FALSE CCAs 17.2.1 Receive Command Usage The "receive" utility present in the "release" folder can be invoked for displaying the following information. /receive <base-interface> <filename> <channel_number> <start/stop> <channel_width>
<base_interface>:This parameter specifies the Base Interface (string like rpine0).
<filename>: Name of the file into which the statistics will be logged, in addition to being displayed on the console.
<channel_number> Cabled tests can be made run in configured channels.: Channel number in which the statistics need to be logged.
<start/stop>: Parameter to start or stop logging the statistics. Enter 0 to start logging and 1 to stop logging.
<channel_width>: Operating bandwidth of the channel. Refer to the table below. Value Channel Width 0 2 4 6 20MHz Upper 20MHz of 40MHz Lower 20MHz of 40MHz Full 40MHz 101 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Value Channel Width 8 20Mhz mode for 11J channel Table 10: Channel Width Values Examples:
./receive rpine0 stats 6 0 0 The above command starts the receive utility and logs statistics with the following parameters. Filename stats Channel number 6 Channel Width 20MHz The test utility displays the following information:
Total number of packets received with correct CRC. Total number of packets received with incorrect CRC. Total number of False CCA's received. /receive stats 6 1 0 The above command will stop the receive application 17.3 Continuous Wave (CW) mode The Continuous Wave mode is used to transmit a single tone either a sine wave or a cosine wave. 17.3.1 Command Usage
./onebox_util <base_interface> cw_mode <channel> <start/stop> <type>
<base_interface>: This parameter specifies the Base Interface (string like rpine0)
<channel_number>: Channel number in which the transmission has to be done. Please refer to the Table 7:
Channel Numbers and Corresponding Center Frequencies for a mapping between the channel numbers and the center frequencies.
<start/stop>: This parameter is used to start or stop the transmission. Enter 0 to start transmission and 2 to stop transmission. In order to start transmission for 11J 20MHz channels, enter 1.
<type>: This parameter is used to select among the different types of waves to be transmitted. Enter 2 for Single Tone of 5MHz. Enter 5 for DC tone. 1. The transmit power for the CW mode transmission is set using the "transmit" utility. The "transmit"
command has to be issued first inorder to start the transmission at the required transmit power level and then it is called again to stop the transmission before giving the "onebox_util" command to start the CW transmission. The Antenna direction in CW mode will be in reverse direction. The user can select the appropriate antenna by using the following command.
# ./onebox_util <base_interface> ant_sel <value>
<value = 2> Select RF_OUT_2/Integrated Antenna
<value = 3 > Select RF_OUT_1/U.FL Connector Examples 102 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
#. /transmit rpine0 2 5.5 750 1 11 0 1 0 0 0 0
#. /transmit rpine0 0
#. /onebox_util rpine0 cw_mode 6 0 2 The above command starts continuous wave transmission with the following configuration. Channel number 6 Type Single tone Transmit Power 2dBm The command used for stopping continuous wave transmission is outlined below:
#. /onebox_util rpine0 cw_mode 6 2 2 The command used for starting transmission in 184(11J ) channel is outlined below:
#. /onebox_util rpine0 cw_mode 184 1 2 The command used for stopping the transmission is outlined below:
#. /onebox_util rpine0 cw_mode 184 2 2 103 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 18 Wake-On-Wireless LAN 18.1 WoWLAN through onebox_util The parameters listed below for the Wake-On-Wireless LAN are valid only in Client mode. The <hw_bmiss>
parameter needs to be given as an input during VAP creation inorder to use the WoWLAN feature refer to the section 5.5 Configuring Using onebox_util for details on VAP creation.
<base_interface>: Base Interface (string like rpine0)
<src_mac_addr>: This parameter is the 48-bit Source MAC address in hexadecimal format with colon separation, which is used to filter the Unicast packets received by the device. This parameter is valid only when bit 2 of the <wowlan_flags> parameter is set to '1'.
<host_sleep_status>: This parameter informs the device whether the Host is entering sleep state ("1") or exiting sleep state ("0"). The device will toggle the GPIO_2 (Host Wakeup Interrupt) only when the Host indicates that it is entering to sleep state.
<wowlan_flags>: This parameter is a bitmap used to program the device to wake up the Host based on the type of packets received by it. It is a 16-bit value as explained in the table below. The Host can program multiple bits to "1" at the same time to enable wakeup on different types of events. The above configuration is used only when you have kept the device in transmit burst mode and has made random hopping as "enabled". For more details in "Configuration of device in the transmit burst mode", please refer to the section 18.2.1BT Transmit Tests. 18.2 WoWLAN using Linux power state machine Linux supports different power states to handle power management i.e. S3 (suspend), S4 (hibernate) and S5
(poweroff). WoWLAN can be verified through these power states which is the idle way. Presently only S3 is supported in N-Link Linux driver. Also WoWLAN configuration is allowed in NL80211 interface only. Enable ONEBOX_CONFIG_WOWLAN in Makefile to use this feature before building the driver. It supports kernel v3.11 or higher 18.2.1 Overview WoWLAN is a power saving technique where device goes to sleep until an explicit trigger is received through WLAN. For this feature to work station should be connected to an AP and the connection should retain while the system is in suspend. User shall configure WoWLAN trigger types like magic packet or pattern etc using which he wants to wake up the system. This trigger packet will be received by the WLAN device through AP. Device firmware shall process the trigger and check whether it is a valid trigger or not. If it is a valid trigger packet, it will trigger the GPIO of host wake-up. It is the vendor responsibility to map this GPIO to the platforms power module. To verify WoWLAN below steps are needed:
Configure WoWLAN Suspend the system Trigger wakeup 104 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 To configure WoWLAN, standard network tool iw can be used. Issue below command in the terminal to configure 18.2.2 Configure WoWLAN WoWLAN.
# iw phy <phyX> wowlan enable <trigger_type>
phyX is the phy physical device number of the system for the device. It can be obtained by using the 'info'
command. The command and its example output is shown below.
# iw dev <intf_name> info Interface wlan0 ifindex 5 wdev 0x100000001 addr 00:23:a7:b9:ab:44 type managed wiphy 1 channel 6 (2437 MHz), width: 20 MHz (no HT), center1: 2437 MHz As can be seen, in this case, phy<X> is termed as phy1. 18.2.3 Trigger Type These are the type of triggers currently available in linux. Possible triggers are:
[any] [disconnect] [magic-packet] [gtk-rekey-failure] [eap-identity-request] [4way-handshake]
[rfkillrelease]
[offset1+]<pattern1> ...]
[net-detect interval <in_msecs> [delay <in_secs>] [freqs <freq>+] [matches [ssid <ssid>]+]]
[active [ssid <ssid>]+|passive] [randomise[=<addr>/<mask>]]] [tcp <config-file>] [patterns Triggers which are currently supported are:
<any> - To wake for any received packet
<disconnect> - To wake up for receival of disassociation or deauthentication from connected AP.
<magic-packet> - Receive of any magic packet generated through wowlan applications. That host will be waked up if the connection is lost in any case (Like AP is powered off etc). Also host will be wakeup when GTK rekey packet is received. Hence before going to suspend, it is recommended to configure high GTK rekey timeout 18.2.4 Suspend system Use below command to suspend the system. 105 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
#systemctl suspend This step will suspend the system and system goes to power save mode. 18.2.5 Trigger wakeup To initiate trigger packet, connect a PC or laptop to AP through LAN/WLAN. Get IP and check ping to AP is working Copy WOWLAN applications 'wakeonlan' or 'etherwake' to this third party PC. Issue below command to issue or not. trigger. Or 1. wakeonlan <MAC_addr_of_our_device>
2. etherwake <MAC_addr_or_our_device>
For eatherwake application, please edit ether-wake.c and go to main() function, update the ifname with the interface name of our device. Compile the application using below command. 3. gcc ether-wake.c o etherwake Upon issuing this trigger, system should resume in 2 to 5 seconds. 106 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 19 PUF [ Physical Unclonable Functions ]
PUF, is a technology which provides a secure method for storing a key, withstanding todays 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.1 Introduction 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
./onebox_util rpine0 puf_req 0 1 19.3.2 PUF Start 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. 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. 107 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
./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 For the above command, create a text file plain_data.txt that should have some data of length more than 128 bytes 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 For the above command, create a text file plain_data.txt that should have some data of length more than 128 bytes 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. 108 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
./onebox_util rpine0 puf_req 10 19.3.12 PUF Block Get Key This operation is used for blocking further Get Key operations. /onebox_util rpine0 puf_req 11 Refer the page Features for all IOCTL commands in detail 109 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 20 GTK Offload 20.1 Configuration GTK Offload is a firmware feature that updates the Group Temporal Key (GTK) by processing EAPOL messagewithin firmware instead of sending EAPOL messages to host driver. To use this feature, ensure that driver is compiled with below define enabled in Makefile EXTRA_CFLAGS += -DONEBOX_CONFIG_GTK_OFFLOAD To enable/disable this feature at run time, use the following ioctl
./onebox_util rpine0 gtk_offload 1/0 110 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 21 Steps to connect 802.11R client to AP 1. Use the following configuration in sta_settings.conf file to connect to 802.11R AP. network={
ssid="<SSID of Access Point>"
key_mgmt=FT-PSK psk=<passphrase specified in the Access Point>
proto=WPA2 pairwise=CCMP group=CCMP
2. Use following command to roam Over-The-DS for RSI 802.11R client:
#./wpa_cli -i <interface_name> ft_ds <AP_MAC_ID>
NOTE: Here AP_MAC_ID is obtained from scan results and given manually. 111 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 22 Steps to configure 802.11W 22.1 Configuring and Compiling Driver for PMF in client mode:
1. Enable CONFIG_11W in Driver Makefile 2. Enable CONFIG_IEEE80211W=y in wpa_supplicant .config 3. Enable WPA-PSK-SHA256 as key_mgmt in network block in supplicant sta_settings.conf i. pmf=1/2, PMF is enabled/required correspondingly . pmf=2 network = {
ssid="REDPINE_AP_MFP"
pairwise=CCMP group=CCMP key_mgmt=WPA-PSK-SHA256 psk="12345678"
proto=WPA2 priority=1
4. Configure AP as MFP Capable/Required. 22.2 Configuring and Compiling Driver for PMF in AP mode:
1. Enable CONFIG_11W in Driver Makefile 2. Enable CONFIG_IEEE80211W=y in hostapd .config 3. Enable WPA-PSK-SHA256 as key_mgmt in hostapd_ccmp.conf i. pmf=1/2, PMF is enabled/required correspondingly . Make sure below options are enabled apart from your configuration.
# This field is a bit field that can be used to enable WPA (IEEE 802.11i/D3.0)
# and/or WPA2 (full IEEE 802.11i/RSN):
# bit0 = WPA
# bit1 = IEEE 802.11i/RSN (WPA2) (dot11RSNAEnabled) wpa=2
# ieee80211w: Whether management frame protection (MFP) is enabled
# 0 = disabled (default)
# 1 = optional
# 2 = required ieee80211w=2 wpa_key_mgmt =WPA-PSK-SHA256 group_mgmt_cipher=AES-128-CMAC 112 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 23 Update WLAN region based maximum powers from driver Following are the steps need to be followed to program region based maximum powers to the WLAN device. 1. Go to the host/release folder. 2. Open and update maximum powers in wlan_gain_table.txt file. 3. Now give below commands
#sh wlan_enable.sh
#./onebox_util rpine0 update_wlan_gain_table With the above commands, gain tables programming will start and a successful programming should show below output in dmesg logs.
**************Successfully completed programming n gain tables *************
Here 'n' is the number of structures given in wlan_gain_table.txt file. Note: Please note that in END-TO-END mode gain table update is recommended to be done before VAP creation and after enabling the protocol ( sh wlan_enable.sh). 113 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 24 Bluetooth hcitool and hciconfig Usage The hcitool and hciconfig commands are used to control and configure parameters for the Bluetooth interface. The HCI commands explained here are the most frequently used commands. For other HCI commands please refer to the Bluetooth specification, Volume 2 Part E, Chapter7 from www.bluetooth.org. This command is used to issue a soft reset to the Bluetooth module Reset Description Default Value Input Parameters Output Parameter Reset Required Read Local Version Information Description Default Value Input Parameters Output Parameter
None None No.
None HCI version HCI revision LMP version Manufacturer name LMP subversion Usage hcitool -i <hciX> cmd 0x03 0x03 This command is used to read the local version information Reset Required No. Usage hcitool -i <hciX> cmd 0x04 0x01 Read Local Supported Commands Description Default Value Input Parameters
None This command is used to read the local controller supported HCI commands. Output Parameter List of supported commands (64 bytes of bit field) 114 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Reset Required No. Usage hcitool -i <hciX> cmd 0x04 0x02 Get Local BD Address This command is used to get the local BD Address Output Parameter 6 Byte BD Address hcitool -i <hciX> cmd 0x04 0x09
None No. None. No. Description Default Value Input Parameters Reset Required Usage Start Inquiry Description Default Value Input Parameters Output Parameter Reset Required Usage Write Local Name Description Default Value This command is used to start the Inquiry process LAP (3 Bytes): (0x9E8B00 0x9E8B3F) Inquiry duration: (0x01 to 0x30 -> 1.28 to 61.44 Seconds) Number of responses: (0x01 0xFF) hcitool -i <hciX> cmd 0x01 0x01 <LAP> <duration>
<no_of_responses>
This command is used to Set the local device name Input Parameters Name of the device. Output Parameter Reset Required None. No. Usage hcitool -i <hciX> cmd 0x03 0x13 <name>
Table 12: Bluetooth hcitool and hciconfig usage 115 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 24.1 Bluetooth Power Save Commands The vendor-specific HCI Commands are used to configure the device in the power save mode. The module supports Low Power (LP) and Ultra-Low Power (ULP) modes. These are explained in more detail in the Power Save Modes section of WLAN ioctl Usage Guide. The LP and ULP modes are supported with the SDIO interface while only the LP mode is supported in USB mode. Vendor Specific Power Save Description Default Value
Input Parameters This command is used to enable/disable the power save mode of the device and also set the sleep duration in Standby mode. Sleep Enable:
0x01 - Sleep enable 0x00 - Sleep disable Sleep Mode:
0x01 LP (Low Power) mode 0x02 ULP (Ultra Low Power) mode Sleep Duration in Standby mode (in msec) : (Range 0x00 0xFF) Output Parameter Reset Required None No. Usage hcitool -i <hciX> cmd 0x3F 0x0003 <sleep enable/disable> <sleep mode> <sleep duration>
24.2 Bluetooth Performance Test ioctl Usage The OneBox-Mobile software provides applications to test Transmit and Receive performance of the module.Open the common_insert.sh file present in the "release" folder using an editor like vim. Ensure that the DRIVER_MODE and COEX_MODE is set as below:
DRIVER_MODE = 2 COEX_MODE = 8(for BT LE) 24.3 BLE/BLR Transmit 24.3.1 Introduction Access address Ensure that only Bluetooth is selected in menuconfig. Run the onebox_insert.sh script present in the "release" folder to install the Driver in Performance Test mode. Next, follow the instructions below to run the Transmit and Receive tests. The "transmit" utility, present in the "release" folder requires configuring the following parameters to start transmitting packets. 116 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 le channel type packet length ble rate Receive channel index Transmit_channel index Scrambler seed no.of packets payload type tx power tx mode hopping_type antenna selection pll_mode rf_type rf_chain inter_pkt_gap 24.3.2 IOCTL The following command can be given to start the transmission
./ble_transmit <Access_Addr> <pkt_length> <ble_rate> <rx_channel_index> <tx_channel_index>
<scrambler_seed> <no_of_packets> <payload_type> <le_channel_type> <tx_power> <tx_mode>
<hopping_type> <ant_sel> <inter_pkt_gap> <pll_mode> <rf_type> <rf_chain>
After the transmission starts, the following command can be given to stop the transmission. Please stop the transmission before you start again using the command below :
./ble_transmit 0 24.3.3 Description Access Address : It is a 32-bit address in hexadecimal format, e.g.,00112233 pkt_length : Length of the packet, in bytes, to be transmitted. ble_rate : 1Mbps - 1 ,2Mbps - 2 , 125Kbps - 4, 500Kbps - 8 rx_channel_index : Receive channel index, as per the Bluetooth standard.i.e, 0 to 39 tx_channel_index : Transmit channel index, as per the Bluetooth standard. i.e, 0 to 39 scrambler_seed : Initial seed to be used for whitening. It should be set to 0 in order to disable whitening. In order to enable the whitening scrambler seed should be given, which is used on the receive side. no_of_packets : Number of packets to be transmitted. It is valid only when the <tx_mode> is set to Burst mode. payload_type : Type of payload to be transmitted 0 Payload consists of all zeros 1 Payload consists of all 0xFFs 2 Payload consists of all 0x55s 3 Payload consists of all 0xF0s 4 Payload consists of PN9 sequence. le_channel_type : advertising channel - 0 data channel - 1 tx_power : Transmit power value should be between 0 and 18 tx_mode : Burst mode - 0 Continuous mode - 1 hopping_type: no hopping -0 fixed hopping - 1 random hopping - 2 ant_sel : onchip antenna - 2 u.f.l - 3 117 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 inter_pkt_gap : Number of slots to be skipped between two packets - Each slot will be 1250usec pll_mode : PLL_MODE0 0 PLL_MODE1 1 PLL_MODE2 2 rf_type : External RF 0 Internal RF 1 rf_chain: WLAN_HP_CHAIN 0 WLAN_LP_CHAIN 1 BT_HP_CHAIN 2 BT_LP_CHAIN 3 24.3.4 Appendix Frequencies and channel Numbers used for Bluetooth LE Mode:
Band(GHz) Bandwidth (MHz) Channel Centre Freq (MHz) 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 2402 2404 2406 2408 2410 2412 2414 2416 2418 2420 2422 2424 2426 2428 2430 2432 2434 2436 2438 2440 2442 2444 2446 2448 2450 2452 2454 2456 2458 118 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Band(GHz) Bandwidth (MHz) Channel Centre Freq (MHz) 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2.4 2 2 2 2 2 2 2 2 2 2 2 29 30 31 32 33 34 35 36 37 38 39 2460 2462 2464 2466 2468 2470 2472 2474 2476 2478 2480 Examples:
<Access_Addr> <pkt_length> <ble_rate> <rx_channel_index> <tx_channel_index> <scrambler_seed>
<no_of_packets> <payload_type> <le_channel_type> <tx_power> <tx_mode> <hopping_type> <ant_sel>
<inter_pkt_gap> <pll_mode> <rf_type> <rf_chain>
Continuous mode :
./ble_transmit 71764129 250 1 38 38 2 0 0 1 10 1 0 3 0 0 1 3 For transmitting a BLE-1Mbps Advertising packet with Access Address of 0x71764129 and packet length of 250bytes on 2478MHz with the following parameters Access_Addr - 71764129 pkt_length - 250 ble_rate -1 rx_channel_index -38 tx_channel_index -38 scrambler_seed - 2 no_of_packets - 0 payload_type - 0 le_channel_type -1 tx_power -10 tx_mode - 1 hopping_type - 0 ant_sel -3 inter_pkt_gap -0 pll_mode -0 rf_type - 1 rf_chain - 3 Burst mode :
119 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
./ble_transmit 71764129 250 1 38 38 0 0 0 1 10 0 0 3 0 0 1 3 For transmitting a BLE-1Mbps Advertising packet with Access Address of 0x71764129 and packet length of 250bytes on 2478MHz with the following parameters Access_Addr - 71764129 pkt_length - 250 ble_rate - 1 rx_channel_index -38 tx_channel_index -38 scrambler_seed - 0 no_of_packets - 0 payload_type - 0 le_channel_type -1 tx_power - 10 tx_mode - 0 hopping_type - 0 ant_sel -3 inter_pkt_gap -0 pll_mode -0 rf_type - 1 rf_chain - 3 24.4 BLE/BLR Receive 24.4.1 Introduction Access Address Data Length indication Scrambler_seed ble_rate Receive channel index Transmit_channel index LE Channel type hopping type Antenna selection Loop_back_mode enable/disable pwrsave_options pll_mode rf_type rf_chain Please stop the transmission before you start again using the command below :
. /ble_transmit 0 The "receive" utility, present in the "release" folder requires configuring the following parameters to start transmitting packets. 120 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 24.4.2 IOCTL The following command can be given to start the reception
./ble_receive <access_addr> <data_legth_indication> <scrambler_seed> <ble_rate> <rx_channel_index>
<tx_channel_index> <le_channel_type> <hopping_type> <ant_sel> <loop_back_mode> <pwrsave_options>
<pll_mode> <rf_type> <rf_chain>
scrambler_seed : Initial seed to be used for whitening. It should be set to 0 in order to disable whitening. After the receive starts, the following command can be given to stop the reception. /ble_receive 0 Stop the Reception first before starting of Receiving 24.4.3 Description Access Address : It is a 32-bit address in hexadecimal format, e.g.,00112233 data_length_indication : 0 Disable(37 Bytes) 1 Enable(255 Bytes) ble_rate : 1Mbps - 1 ,2Mbps - 2 , Long Range(LR) - 4 rx_channel_index : Receive channel index, as per the Bluetooth standard.i.e, 0 to 39 tx_channel_index : Transmit channel index, as per the Bluetooth standard. i.e, 0 to 39 le_channel_type : advertising channel 0 data channel 1 hopping_type: no hopping -0 fixed hopping - 1 random hopping - 2 ant_sel : onchip antenna - 2 u.f.l 3 loop_back_mode : Disable 0 Enable 1 pwrsave_options : Disable 0 Enable 1 pll_mode : PLL_MODE0 0 PLL_MODE1 1 PLL_MODE2 2 rf_type : External RF 0 Internal RF 1 rf_chain: WLAN_HP_CHAIN 0 WLAN_LP_CHAIN 1 BT_HP_CHAIN 2 BT_LP_CHAIN 3 24.4.4 Appendix Examples:
scrambler_seed : 0 hopping_type: disable ant_sel : u.f.l loop_back_mode : Disabled Frequencies and channel numbers used for Bluetooth LE Mode are same as BLE TX case. For receiving a BLE-1Mbps Advertising packet with Access Address of 0x71764129 and packet length of 250bytes on 2478MHz with the following parameters 121 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019
. /ble_receive71764129 0 0 1 37 37 0 3 0 0 0 1 3 pwrsave_options : Disabled pll_mode : PLL_MODE0 rf_type : Internal RF rf_chain: BT_LP_CHAIN IOCTL Command:
24.5 Hopping 24.5.1 Introduction 24.5.2 IOCTL 24.5.3 Description Classic_le_mode: 2 BLE The bt_util command is used to configure the device in order to transmit packets in required channels when random hopping feature is enabled. The parameters of "bt_util" command are as follows:
./bt_util afh_map <classic_le_mode> <channel_bit_map>
channel_bit_map: It is bitmap to transmit in required channels. It is 10 bytes in length. Range:
00000000000000000001 to 7FFFFFFFFFFFFFFFFFFF Bit number is the channel number used. 24.5.4 Appendix Note:-
The above configuration is used only when you have kept the device in transmit burst mode and has made random hopping as "enabled". For more details in "Configuration of device in the transmit burst mode", please refer to the sectionBLE/BLR Transmit. 111111111111 Examples:
. /bt_util afh_map 2 7FFFFFFFFFFFFFFFFFFF Classic_le_mode 2
. /bt_util afh_map 2 00000000000000000007 Classic_le_mode 2
/bt_util afh_map 2 70000000000000000000 Classic_le_mode 2 channel_bit_map 7FFFFFFFFFFFFFFFFFFF (here all the bits of bit map are set. So, transmission happens in all the channels randomly) channel_bit_map 00000000000000000007 (here only lower 3 bits of bit map are set. So, transmission happens in 0,1 & 2 channels randomly) 122 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 channel_bit_map 70000000000000000000 (here only upper 4 bits of bit map are set. So, transmission happens in 76,77 & 78 channels randomly) 123 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 25 Android support for RS9116 Redpine Signlas also supports Android Operating System. Currently supported variants in Android MarshMallow (6.0.1) Nougat (7.1) Please contactsales@redpinesignals.com for further details. 124 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 26 Appendix A: Configuration of Kernels from 3.13 and above To ensure that the OneBox-Mobile software works on kernel versions from 3.13 and above, some configuration changes might be needed. These are explained in this section. Super user permissions are needed to make these changes. For SDIO mode, ensure that the SDIO stack related modules are already inserted in the kernel. This can be verified by using the commands below :
cd release sh load_stack.sh lsmod Verify that the output of the "lsmod" command should describe sdhci.ko, sdhci_pci.ko (Specific for x86/PC, others should use their controller specific ko ), mmc_block.ko as well as mmc_core.ko modules. This is a one-time process and need not be repeated unless the modules are explicitly removed by the user. 26.1 SDIO Stack Options If SDIO is the interface to the Host processor, it has to be ensured that the SDIO stack related modules are compiled in the kernel. If the SDIO stack modules are not present, follow the steps below in order to enable SDIO support in the kernel. 1. Navigate to the Linux kernel source folder. This is usually in /usr/src/kernels/Linux-<kernel-version>
2. Execute the 'make menuconfig' command in order to open the Kernel Configuration menu. 3. Scroll down to the "Device Drivers --->" option and hit Enter. 4. In the new menu, scroll down to the "MMC/SD/SDIO card support --->" option and press 'M' to modularize the "MMC/SD/SDIO card support" feature and hit Enter. 125 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 5. In the new menu, press 'M' to modularize the following options:
MMC block device driver Secure Digital Host Controller Interface support SDHCI support on PCI bus 6. Hit the Tab key to select Exit and hit Enter. Repeat this till you are asked whether you want to save the 7. Select "Yes" and hit Enter. If the above options are already selected, the menuconfig screen will exit configuration. immediately 26.2 Wireless Extension Tools Wireless Extension tools like 'iwconfig' and 'iwpriv' are required for configuring the OneBox-Mobile software. Make sure that the wireless extensions are enabled in the Linux kernel configuration file. User needs to enable below options in kernel configuration file, re-compile the kernel and cross compile the driver. 126 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 CONFIG_WIRELESS_EXT CONFIG_WEXT_PRIV CONFIG_WEXT_SPY 26.3 Bluetooth Stack Options If Bluetooth is required, it has to be ensured that the Bluetooth modules are compiled in the kernel. If the Bluetooth modules are not present, follow the steps below to enable Bluetooth support in the kernel. 1. Navigate to the Linux kernel source folder. This is usually in /usr/src/kernels/linux-<kernel-version>
2. Execute the 'make menuconfig' command in order to open the Kernel Configuration menu. 3. Scroll down to "Networking support --->" and hit Enter. 4. In the new menu, scroll down to the "Bluetooth subsystem support --->" option and press 'M' to modularize the "Bluetooth subsystem support" feature and hit Enter. 127 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 5. In the new menu, press 'M' to modularize the following options:
RFCOMM Protocol support (enable the "RFCOMM TTY support" feature under this). BNEP Protocol support (enable the "Multicast filter support" and "Broadcast filter support" features under this). CMTP Protocol support HIDP Protocol support 6. Hit the Tab key to select Exit and hit Enter. Repeat this till you are asked whether you want to save the configuration. 7. Select "Yes" and hit Enter. If the above options are already selected, the menuconfig screen will exit immediately. 26.4 Kernel Compilation The steps used for Kernel Compilation are as follows:
1. Navigate to the kernel source folder. 2. Execute the "make" command. 3. Execute the "make modules_install" command. 4. Execute the "make install" command. This ensures that the customized kernel is installed and the boot loader is updated appropriately. 5. Reboot the system in order to boot up with the customized kernel. 128 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 27 Appendix B: Binary Files for Embedded Platforms Redpine offers pre-built binary files of the OneBox-Mobile software in order to enable customers to evaluate the software on specific embedded processor platforms. The platforms supported for the current release are listed below:
Freescale i.MX6 Atmel ATSAM9G45 and AT91SAM9M10 27.1 Common Hardware Requirements for Embedded Platforms RS9116 Evaluation Kit. The contents are as follows:
RS9116 Module Evaluation Board USB-to-microUSB Cable SDIO Adaptor Cable SPI Adaptor Cable USB Pen Drive The sections below explain about the usage of the binaries on these platforms and also describes like how to generate the binaries in case of the OneBox-Mobile software source is available. 27.2 Freescale i.MX6 27.2.1 Hardware Requirements i.MX 6SoloLite Evaluation Kit. The kit contents are as follows:
a. Board: MCIMX6SLEVK b. Cables: Micro USB-B-2-USB-Type A male, V2.0 c. Power supply: 100/240 V input, 5 V, 2.4 A output W/AC adaptor d. Two SD cards: Programmed Android e. Linux PC with Serial-to-USB drivers installed Used to communicate with the i.MX6 platform. 27.2.2 Software Requirements Toolchain, BSP and Ubuntu Linux OS package for i.MX6 - Kernel version 3.0.35. OneBox-Mobile Software Release package. 27.2.3 Hardware Setup The steps for Hardware Setup are as follows:
1. Connect the i.MX6 board to the Linux PC by using the USB-to-microUSB cable the cable has to be connected to port J26 (microUSB) of the board. 2. Connect the Redpine Evaluation Board (EVB) to the i.MX6 board by using the SDIO adaptor or USB-to-
microUSB cable (both are included in the Redpine Evaluation Kit), depending on which Host Interface is needed. i.MX6 + Redpine EVB with USB: Connect USB cable to J10 (USB) port of i.MX6 i.MX6 + Redpine EVB with SDIO: Connect SDIO Adapter to SD3 port of i.MX6 1. Preparing the MMC Card: It is an SD/MMC memory card which is required to transfer the bootloader and kernel images for initializing the partition table and copy the root file system. This is included in the i.MX6 Evaluation Kit but it is programmed for Android OS. Refer to the i.MX_6SoloLite_EVK_Linux_User's_Guide.pdf document provided by Freescale as a part of the L3.0.35_4.1.0_LINUX_MMDOCS documentation package in order to prepare the SD/MMC card for Linux OS with kernel version 3.0.35. 129 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 27.2.4 Cross Compile and Copy OneBox-Mobile Software If the OneBox-Mobile software's source is available, follow the steps mentioned in the Compiling the Driver section in order to cross compile the OneBox-Mobile software for i.MX6. Assign the DEF_KERNEL_DIR variable in the Makefile as follows (assuming the kernel source is available in the "/lib/
modules" folder):
DEF_KERNEL_DIR:= /lib/modules/linux-3.0.35_SOLOLITE_hw The "make" command for the i.MX6 is as follows, assuming the toolchain is present in the "/toolchain/opt/
freescale" folder:
make ARCH=arm CROSS_COMPILE=/toolchain/opt/freescale/FWIOCUA0R1M1P1/TOOLS/cross/bin/arm-mv5sft-linux-
gnueabi-
Next, plugin the SD/MMC card to the PC and copy the pre-built binaries or the binaries generated above to the SD/
MMC card. Plugin the SD/MMC card into the i.MX6 board and follow the boot procedure. Once the bootup and login are completed, go to the release folder and follow the procedure explained in the Installing the Driver section. 27.3 Freescale i.MX53 27.3.1 Hardware Requirements IMX53QSB: i.MX53 Quick Start Board. The kit contents are as follows:
i.MX53QUICK START Board a. b. microSD Card preloaded with Ubuntu Demonstration Software c. USB Cable (StandardA to MicroB connectors) d. 5V/2.0A Power Supply e. Quick Start Guide f. Documentation DVD g. Linux PC with Serial port this will be used to communicate with the processor platform. h. Serial RS232 Cable 27.3.2 Software Requirements The software requirements Free scale i MX53 platform are as follows:
Toolchain, BSP and Linux OS package for i.MX6 - Kernel version 2.6.35. OneBox-Mobile Software Release package minicom/GTKTerm on the Linux PC 27.3.3 Hardware Setup The hardware setup is as follows:
1. Connect the i.MX53 board to the Linux PC using the Serial RS232 cable. 2. Connect the Redpine Evaluation Board (EVB) to the i.MX53 board using the SDIO adaptor or USB-to-
microUSB cable (both included in the Redpine Evaluation Kit), depending on which the Host Interface is needed. 3. Open a serial terminal program like minicom or GTKTerm and configure it with the following settings:
a. Baud Rate: 115200 b. Data bits: 8 c. Stop bits: 1 d. Parity: None e. Flow Control:
130 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 4. Preparing the MMC Card: An SD/MMC memory card is required to transfer the bootloader and kernel images for initializing the partition table and copy the root file system. This is included in the i.MX53 Evaluation Kit. Refer to the i.MX53_EVK_Linux_BSP_UserGuide.pdf document provided by Freescale as a part of the IMX53_1109_LINUXDOCS_BUNDLE documentation package, in order to prepare the SD/MMC card for Linux OS with kernel version 2.6.35. 27.3.4 Cross Compile and Copy OneBox-Mobile Software If the OneBox-Mobile software's source is available, follow the steps mentioned in the section Compiling the Driver in order to cross compile the OneBox-Mobile software for i.MX53. Assign the DEF_KERNEL_DIR variable in the Makefile as follows (assuming the kernel source is available in the "/
lib/modules" folder):
DEF_KERNEL_DIR := /lib/modules/linux-2.6.35.3 The "make" command for the i.MX53 is as follows:
make ARCH=arm CROSS_COMPILE=/toolchain/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-
linux-gnueabi/bin/arm-none-linux-gnueabi-
Next, plugin the SD/MMC card to the PC and copy the pre-built binaries or the binaries generated above to the SD/
MMC card. Plugin the SD/MMC card into the i.MX53 board and follow the boot procedure. Once the bootup and login are completed, go to the release folder and follow the procedure explained in the section 4 Installing the Driver. 27.4 Atmel AT91SAM9G45 and AT91SAM9M10 The Linux kernel version used on the Atmel AT91SAM9G45/M10 is 2.6.30. This is used to verify only the Wi-Fi mode. Bluetooth drivers are not compatible with this kernel version. 27.4.1 Hardware Requirements SAM9M10-G45-EK - ARM926-based eMPU Eval Kit. The kit contents are as follows:
a. Board: SAM9M10-G45-EK b. Cables: One micro A/B-type USB cable, One serial RS232 cable, One RJ45 crossed cable c. Power supply: Universal input AC/DC power supply, One 3V Lithium Battery type CR1225 d. Linux PC with Serial port Used to communicate with the processor platform 27.4.2 Software Requirements The software requirements for Atmel AT91SAM9G45 and AT91SAM9M10 platform are as follows:
Toolchain, BSP and Ubuntu Linux OS package for AT91SAM9G45 and AT91SAM9M10 - Kernel version 2.6.30 OneBox-Mobile Software Release package minicom/GTKTerm on the Linux PC 27.4.3 Hardware Setup The hardware setup is as follows:
Baud Rate: 115200 Data bits: 8 1. Connect the Atmel board to the Linux PC using the Serial RS232 cable. 2. Connect the Redpine Evaluation Board (EVB) to the processor board using the SDIO adaptor or USB-to-
microUSB cable (both included in the Redpine Evaluation Kit), depending on which Host Interface is needed. 3. Power on the processor board. 4. Open a serial terminal program like minicom or GTKTerm and configure it with the following settings:
131 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Stop bits: 1 Parity: None Flow Control:
1. Connect the RJ45 cable between the PC and the board. 2. Follow the instructions given at http://www.at91.com/linux4sam/bin/view/Linux4SAM/GettingStarted in order to setup the board with the Linux OS kernel version 2.6.30. 27.4.4 Cross Compile and Copy OneBox-Mobile Software If the OneBox-Mobile software's source is available, follow the steps mentioned in the section Compiling the Driver in order to cross compile the OneBox-Mobile software for the Atmel processor. Assign the DEF_KERNEL_DIR variable in the Makefile as follows (assuming the kernel source is available in the "/
lib/modules" folder):
DEF_KERNEL_DIR := /lib/modules/linux-2.6.30 The "make" command for the AT91SAM9G45/M10 is as follows, assuming the toolchain is present in the "/
toolchain/opt/atmel" folder:
make ARCH=arm CROSS_COMPILE=/toolchain/opt/atmel/arm-2007q1/bin/arm-none-linux-gnueabi-
The steps need to be followed inorder to copy the pre-built binaries or the binaries generated above the Atmel processor platform are as follows:
Ensure that the Linux PC and the Atmel platform are in the same subnet. The IP of the processor platform can be assigned using the minicom/GTKTerm terminal. ifconfig <vap_name> <ip_address>
Example: ifconfig eth0 192.168.1.24 Power cycle the board. Login as "root". There is no password required for the default credentials unless and until some changes has been done by the user. Create a folder called "rsi" in the "/home" folder. Copy the OneBox-Mobile binaries by using the command below:
scp r release/ root@192.168.1.24:/home/rsi Follow the procedure explained in the section Installing the Driver in order to start using the OneBox-Mobile software. 132 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 28 Appendix C: Using the Bluetooth Manager The steps given below explain about the usage of the Bluetooth Manager in Fedora Core 18 on an x86 platform for pairing Bluetooth devices and transferring files. Once the Bluetooth modules have been installed using wlan_bt_insert.sh or onebox_insert.sh script present in the "release" folder as per the instructions mentioned in Section 4.1, hit the "Windows" button on the keyboard. You will see Bluetooth symbol at the bottom-right corner of the screen, as shown in the given below figure. This will open the Bluetooth Manager as shown in the figure below:
Click on Search in order to start inquiry. 133 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Select the particular device, like your smartphone, right click and select Pair tab to pair with that device. After successfully pairing with the device, right-click on the device and select "Send a file" button in order to send data to the device. You will be presented with a dialog box to select the file that you wish to send. 134 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 135 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 29 Appendix D: Common Configuration Parameters The common_insert.sh script is used to configure parameters at boot time. The parameters with their usage and input values are described below. 29.1 RF Power Mode parameter The RF Power Mode parameter is used to set the power mode at which the RF operates. It is applicable for each protocol. By default, it is set to high power TX and high power RX. The following are the possible configurable values:
0x00 - For Both TX and RX High Power 0x11 - For Both TX and RX Medium Power 0x22 - For Both TX and RX LOW Power 0x10 - For High Power TX and Medium RX Power 0x20 - For High Power TX and LOW RX Power 0x01 - For Medium TX and RX High Power 0x21 - For Medium Power TX and LOW RX Power 0x02 - For Low Power TX and RX High Power 0x12 - For LOW Power TX and Medium RX Power WLAN_RF_PWR_MODE is used to set the rf power mode for WLAN protocol. BT_RF_PWR_MODE is used to set the rf power mode for Bluetooth protocol. Example:
WLAN_RF_PWR_MODE=0x00 The above sets high TX and high RX power for WLAN. BT_RF_PWR_MODE=0x00 The above sets high TX and high RX power for Bluetooth. 29.2 Country selection 0 - World Domain 840 - US Domain Maps to US Region 276 - Germany Maps to EU Region 392 - Japan Maps to Japan Region Example:
SET_COUNTRY_CODE=0 The above sets the module in the world domain. This parameter is used to set the module in a specific country. This is set commonly across all protocols. The following country codes are applicable. In the NL80211 mode priority is given for the country code from "sta_settings /hostapd.conf / iw" than the country code from common_insert.sh. It is recommended to use same country code in all inputs to avoid confusion. This variable is used to select the antenna to be used. The following are the possible values:
29.3 Antenna selection 2 Select internal antenna 3 Select external antenna Example:
ANT_SEL_VALUE=2 The above line selects the internal antenna. The Operation starts on this antenna. 136 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 If antenna diversity selection feature is also enabled, initial operation will start on the antenna selected. Antenna diversity operation will continue as expected. 29.3.1 COEX Mode selection This variable is used to select the Coex mode in which the module has to operate. The following are the possible values:
1 - WLAN STATION /WIFI-Direct/WLAN PER 2 - WLAN ACCESS POINT (including multiple APs on different vaps) 3 - WLAN ACCESS POINT + STATION MODE (on multiple vaps) 8 - BT LE MODE /BT LE PER MODE 9 - WLAN STATION + BT LE MODE 12 - BT CLASSIC + BT LE MODE Example:
COEX_MODE=3 The above line sets the module to operate in WLAN AP + STA concurrent mode. 29.3.2 LED ON/OFF This variable is used to enable or disable the LED functionality for Wi-Fi activity. The following are the possible values:
0 Disable LED functionality 1 Enable LED functionality Example:
LED_FUNC_EN=1 The above line enables the LED functionality for Wi-Fi activity. This variable is used to select the BT RF TYPE which the module has to operate. The following are the possible values:
29.3.3 BT RF Type 0 - EXTERNAL RF 1 - INTERNAL RF Example:
BT_RF_TYPE=1 The above sets bt rf type to Internal RF. 29.3.4 BLE_TX_PWR_INX BLE_TX_PWR_INX=0x1e 29.3.5 BLE_PWR_SAVE_OPTIONS BLE_PWR_SAVE_OPTIONS=2 BLE_DUTY_CYCLING BIT(0) This variable is used to select the BLE_TX _PWR index value.The following are the possible values. Default Value for BLE Tx Power Index is 30 Range for the BLE Tx LP Chain Power Index is 1 - 63 (0, 32 are invalid) Range for the BLE Tx HP Power Index is 64 to 76 This variable is used to select the BLE_PWR_SAVE_OPTIONS mode value.The following are the possible values. 137 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 BLR_DUTY_CYCLING BIT(1) BLE_PWR_SAVE_4X_MODE BIT(2) 138 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 30 Appendix E: Installation of Missing Generic Netlink Libraries libnl CFlags should be enabled with CONFIG_LIBNL32=y in supplicant and hostpad .config file \[The above configuration settings should be set to "y" in case NL80211 is used\]. Make sure that the NL80211 support and Hostapd support are enabled in the menuconfig during compilation. Create a directory in the location where Tool chain and BSP are present Download the libnl 3.2.xx.tar.gz\[Referring 3.2.27.tar.gz as an example here \] library and extract it in the build directory. mkdir build cd build tar xvf 3.2.27.tar.gz Configure the libnl library for target platfrom CC=/path to the toochain/bin/arm-linux-gnueabihf-gcc
./configure --host=arm-linux-gnueabihf -prefix=/<complete path to build directory>/
Here headers will be installed in ${prefix}/include/libnl3. Make and install the libraries in the destination directory or else they will be installed in /usr/local/lib and /usr/
local/include/libnl folders of host machine by default. Follow the example given below:
make DESTDIR=$(arm-cortex_a8-linux-gnueabihf-gcc -print -/<path to build directory>/build/) Exporting the path for build directory in the command line or add these flags in the supplicant and hostapd config files under CONFIG_DRIVER_NL80211= y variable.
#export LDFLAGS='-L/<path to build directory>/lib/libnl'
OR CFLAGS += -I/<path to build directory>/include/libnl3 Ex: LIBS += -L/<path to build directory>/lib/libnl LIBS : Contains a list of additional libraries to pass to the linker command. 139 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 31 Appendix F: Procedure to use latest supplicant with NL80211 interface Follow the below steps to use latest supplicant with the NL80211 interface Download the supplicant from https://w1.fi/wpa_supplicant/
Extract the supplicant using the following command Make sure the following parameters are enabled in the supplicant configuration file (.config) tar xvf wpa_supplicant-2.6.tar.gz cd wpa_supplicant-2.6/wpa_supplicant cp defconfig .config CONFIG_DRIVER_NL80211=y CONFIG_BGSCAN_SIMPLE=y NL80211_CMD_ROAM=y CONFIG_LIBNL20=y CONFIG_LIBNL32=y CONFIG_WPS2=y CONFIG_p2p=y CONFIG_BGSCAN=y Save the configuration file and exit Compile the supplicant using "make" command in the following path
$ cd wpa_supplicant-2.6/wpa_supplicant
$ make clean
$ make After successful compilation the supplicant executable will be found in the same path.Copy the supplicant executable to the driver release folder. cp wpa_supplicant RS9116.NXX.NL.XXX.LNX.XXX/source/host/release. To enable Bgscan and Roaming add 'bgscan="simple:10:-45:100" ' in the sta_settings.conf. 31.1 Bgscan and Roaming 31.1.1 Description wpa_supplicantbehaviorforbackgroundscanningcanbespecifiedbyconfiguringabgscanmodule.Thesemodule sareresponsibleforrequestingbackgroundscansforthepurposeofroamingwithinanESS(i.e.,withinasinglenet workblockwithalltheAPsusingthesameSSID). Thebgscan parameteruses the below format:
"<bgscanmodulename>:<moduleparameters>"
bgscan="simple:<shortbgscanintervalinseconds>:<signalstrengththreshold>:<longinterval>"
140 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 ctrl_interface=/var/run/wpa_supplicant update_config=1 network={
ssid="REDPINE_AP_CCMP"
pairwise=CCMP TKIP group=CCMP TKIP key_mgmt=WPA-PSK psk="12345678"
proto=WPA2 WPA bgscan="simple:10:-45:100"
priority=1
31.1.2 ConfigureConnectionqualitymonitoring(cqm)rssiandhysteresisusingiwcommand To know more about iw tool, refer to the sectionConfiguration Using CFG80211.
$iw dev <devname> cqm rssi <threshold|off> [<hysteresis>]
Set connection quality monitor RSSI threshold. Example:
$iw dev wlan0 cqm rssi -45 4 When finished, execute the commands given in the chapterWi-Fi ioctl Usage Guide-->>Enable Background Scan and Set Parameters (only in Client mode). To know more about Background Scan and Set Parameters, refer to the section Background Scan Parameters. Use only open source supplicant for roaming using NL80211. Latest supplicant is recommended. 141 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 32 Appendix G: Considerations need to be made during hostapd usage 32.1 Parameters updated from hostapd.conf file The following are the parameters that will be updated from hostapd conf file instead of using onebox util ioctls. Band Selection:To enable 40MHz for onebox-mobile AP using hostapd following params must be enabled in hostap.conf file Here ht_capab variable must be set as per the channel selected, description regarding this is available in hostap.conf file, set_htconf ioctl will not work in case of hostapd. Hidden ssid: To disable ssid broadcast in beacons for onebox-mobile AP using hostapd , use following ieee80211n=1 ht_capab=[HT40-] (or) ht_capab=[HT40+]
require_ht=1 wmm_enabled=1 variable in hostapd.conf file. ignore_broadcast_ssid=0 Here hide_ssid ioctl will not work in case of hostapd. in hostapd.conf file. dtim_period=5 DTIM Interval: To set dtim interval in beacons for onebox-mobile AP using hostapd, use following variable Here dtim_period iwprivioctl will not work in case of hostapd. SHORT GI: To enable Short GI using hostapd following params must be enabled in hostap.conf file. ht_capab=[SHORT-GI-20][SHORT-GI-40]
Here SHORT-GI iwprivioctl will not work in case of hostapd. hostapd.conf file. beacon_int=200 Here beacon_int iwprivioctl will not work in case of hostapd. Beacon Interval : To set beacon interval for onebox-mobile AP using hostapd, use following variable in 142 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 33 RS9116 n-Link Software TRM Revision History Revision No. Version No. Date Changes 1 2 3 4 5 6 7 8 9 v1.0 v1.1 v1.2 v1.3 v1.4 October 2017 Preliminary version January 2018 March 2018 Formatted the document as per Redpine document standard Added information related to FW_LOAD_MODE configuration option March 2018 April 2018 Added information related to BGSCAN and ROAMING for NL80211 Driver 1. Added Appendix I page regarding hostapd.conf file v1.5 June 2018 1. Modified AP set channel/frequency command usage usage considerations 2. Added support for GTK offload feature 3. Added support for 802.11R roaming feature 4. Added support for PUF feature 5. Updated the hostapd configuration parameter info 6. Added new parameter(service period length) in uapsd power save params ioctl. inWi-Fi ioctl Usage Guide section. 2. Updated PER transmit and receive commands in Wi-Fi Performance Test ioctl usage section. 3. Updated info note inMonitor Mode section. 4. Fixed documentation issues. 5. Added information of radius server usage in Enterprise security using CFG80211 section. 1. Added Notes in bgscan ioctl section 2. Added missing info notes in IOCTL section. 3. Added information regarding Country code update from supplicant in NL mode. 4. Fixed documentation issues. 5. Removed ESSID change and modified channel change commands inWi-Fi ioctl Usage Guide section in Wi-Fi Performance Test ioctl usage. 2. Added Steps to configure 802.11W. 3. Updated BLE Transmit commands. 4. Updated ioctl details for hostapd. 5. Fixed documentation issues. v1.7 December 2018 1. Updated configuration parameters for WIFI PER mode v1.8 January 2019 1. Removed the set mode and get mode commands in Wi-Fi ioctl Usage Guide section. v1.6 October 2018 143 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Revision No. Version No. Date Changes 10 v1.9 March 2019 1. Added the NOTES and updated the INFO for some Wi-
Fi ioctl Usage Guide commands. 2. AddedProgramming WLAN region based maximum powers from driver section. 3. Updated information of hostapd as radius server usage in Enterprise security using CFG80211 section 4. Updated set_scan_type ioctl in Wi-Fi ioctl Usage 5. Added Get Country information ioctl in Wi-Fi ioctl Guide section. Usage Guide section. 6. Added operating voltage configuration information to the Installing the Driver section. Added LED ON/OFF parameter in Appendix D:
Common Configuration Parameters section 11 v2.0 August 2019 144 RS9116 n-Link Linux and Android Technical Reference Manual Version 2.0 August 2019 Disclaimer The information in this document pertains to information related to Redpine Signals, Inc. products. This information is provided as a service to our customers, and may be used for information purposes only. Redpine assumes no liabilities or responsibilities for errors or omissions in this document.This document maybechangedatanytimeatRedpinessolediscretionwithoutanypriornoticetoanyone.Redpineisnot committed to updating this document in the future. Copyright 2019 Redpine Signals, Inc. All rights reserved. 145
1 2 3 4 | kanega002 owners manual v1 | Users Manual | 291.14 KiB | March 19 2020 |
Step 1 PORT Step 2 TOP TM Quick Start Guide Whats in the box?
Kanega LTE Watch, Charger, Power Cable, Four Batteries, Quick Start Videos and downloadable User Guide at www.unaliwear.com/support. Charge your Kanega batteries before inserting on the watch. 1. Connect the power cable to one end of the charger and plug into wall. Verify green light on charger jack is on. 2. Insert two (2) batteries into ports by placing the top end with the gold prongs first, and then pressing the bottom of the battery gently downwards until you hear or feel it attach into place. BATTERY JACK 3. Battery light fades red when batteries are charging and turns green when they are charged. Charging time may take up to 4 hours. Install fully-charged Kanega batteries on the watch. 1. To insert a battery, place the top end with the gold prongs first, and then press the bottom of the battery gently downwards until you hear or feel it attach into place. 2. Place a charged battery on both sides of the watchband and put the remaining two batteries on the charger so they are ready when needed. TOP BOTTOM BOTTOM 3. You will see a black/blank screen. After batteries are installed for the first time, the display changes to Kanega Watch with moving dots. If you do not see this within 5 seconds, press the crown button once. 4. Initial set up may take up to ten (10) minutes. 5. The display changes to Press crown to begin when the watch is ready for you to listen to the short tutorial Step 3 Listen to welcome voice tutorial through the Kanega watch speaker. 1. One short press of the crown button starts the 5 minute voice tutorial. There is one (1) minute to begin before the watch goes to sleep and returns to black/blank screen. 2. Please wear your Kanega watch during the voice tutorial. UnaliWear Customer Success Community@UnaliWear.com 1-888-343-1513, ext. 1 Thank you for purchasing the Kanega watch. Refer to the User Guide for details. FCC ID: 2AM4C-KANEGA002 Contains LTE Module FCC ID: 2AM4C-HL7800M And Contains BT/Wi-Fi Module FCC ID: XF6-M4SB This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and
(2) this device must accept any interference received, including interference that may cause undesired operation. FCC Statement This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/ TV technician for help. Any changes or modifications not expressly approved by the party responsible for compliance could void the users authority to operate the equipment. The exposure standard for wireless transmitter employs a unit of measurement known as the Specific Absorption Rate, or SAR. The SAR limit set by the FCC is 1.6W/kg. The highest SAR value for the EUT as reported to the FCC when worn on the body, as described in this user guide, is 0.01 W/kg for LTE module, 0.05 W/kg for BT/Wi-Fi Module. IC: 25867-KANEGA002 Contains LTE Module IC: 25867-HL7800M And Contains BT/Wi-Fi Module IC: 8407A-M4SB This device contains licence-exempt transmitter(s)/receiver(s) that comply with Innovation, Science and Economic Development Canadas licence-exempt RSS(s). Operation is subject to the following two conditions:
(1) This device may not cause interference.
(2) This device must accept any interference, including interference that may cause undesired operation of the device. Ce dispositif contient une licence qui autorise le (S) metteur (S)/ rcepteur (S) qui est (sont) autoris (S) avec Innovation, La licence canadienne en matire de Science et de dveloppement conomique fait lobjet de deux conditions:
(1) ce dispositif peut ne pas causer de gne.
(2) cet appareil doit accepter toute intrusion, y compris celle qui peut provoquer lindsirabilit Fonctionnement de lappareil. The exposure standard for wireless transmitter employs a unit of measurement known as the Specific Absorption Rate, or SAR. The SAR limit set by the ISED is 1.6W/kg. The highest SAR value for the EUT as reported to the ISED when worn on the body, as described in this user guide, is 0.01 W/kg for LTE module, 0.05 W/kg for BT/Wi-Fi Module. La norme d'exposition pour l'metteur sans fil utilise une unit de mesure connue sous le nom de taux d'absorption spcifique, ou SAR. La limite SAR fixe par l'IC est de 1,6 W / kg. La valeur SAR la plus leve pour l'EUT signale l'IC lorsqu'elle est porte sur le corps, comme dcrit dans ce guide de l'utilisateur, est de 0,01 W/kg pour le module LTE, 0,05 W/kg pour BT/Wi-Fi Module.
1 2 3 4 | 2108RSU042-UE-Internal Rev2.0 | Internal Photos | 2.15 MiB | November 29 2021 / November 30 2021 |
1 2 3 4 | Internal Photos | Internal Photos | 190.79 KiB | December 31 2019 / June 28 2020 | delayed release |
1 2 3 4 | External Photos | External Photos | 449.11 KiB | December 31 2019 / June 28 2020 | delayed release |
1 2 3 4 | KANEGA002-eLabel | ID Label/Location Info | 31.50 KiB | March 19 2020 |
Model: KANEGA002 FCC ID: 2AM4C-KANEGA002 Contains FCC ID: 2AM4C-HL7800M Contains FCC ID: XF6-M4SB IC: 25867-KANEGA002 Contains IC: 25867-HL7800M Contains IC: 8407A-M4SB TO ACCESS THE E-LABEL:
1. Press the crown button once to display the date screen 2. Press the crown button twice to display the user info screen 3. Press the crown button twice to display the above regulatory screen NOTE:
1. Device does not require special accessories or supplemental plug-ins (e.g., the installation of a SIM/USIM card) to access the information. 3410 Cherry Lane, Austin, TX 78703 2. The FCC ID and IC information is part of the device operation software and the information is secured in such a manner that third parties cannot modify it. 3410 Cherry Lane, Austin, TX 78703
1 2 3 4 | 2108RSU042-U4-FCC RF Test Report For BLE V3.0 | Test Report | 1.70 MiB | November 29 2021 / November 30 2021 |
1 2 3 4 | 2108RSU042-U5-FCC RF Test Report For Wi-FiV3.0 | Test Report | 1.94 MiB | November 29 2021 / November 30 2021 |
1 2 3 4 | CP2C Module Authorization | Cover Letter(s) | 31.35 KiB | November 29 2021 / November 30 2021 |
13th September 2021 Class II Permissive Change - Declaration of Authorization To whom it may concern, We, the undersigned, hereby authorize Jean Anne Booth of UnaliWear, Inc,3410 Cherry Lane, Austin, TX 78703, to make a Class II permissive change to FCC ID: XF6-M4SB and IC: 8407A-M4SB for the following reason/s: portable operation usage in specific host device. This authorization gives authority to Jean Anne Booth to act on our behalf, as our agent, in the following matters related to the FCC and/or Innovation, Science and Economic Development Canada
(ISED) approval of this product:
report submittal, related correspondence, the signing of all documents relating to these matters, and any other lawful activity necessary to obtain this Class II permissive change. Any act carried out by Jean Anne Booth within the scope of this authorization shall have the same effect as our own. Sincerely, Company Officer:
Title:
Company:
Sekhar Abburi, Senior Director & Site Manager Silicon Labs
1 2 3 4 | FCC C2PC Request-BTwifi V3.0 | Cover Letter(s) | 124.75 KiB | November 29 2021 / November 30 2021 |
UnaliWear, Inc. 3410 Cherry Lane Austin, TX, 78703 Date: 11/23/2021 Federal Communications Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 FCC ID: XF6-M4SB Request for Class II Permissive Change To whom it may concern, This is a request to file a Class II permissive change for FCC ID: XF6-M4SB, originally granted on 12/31/2019. In the new use case, this module is now being used in a portable device. The module has been changed in the following ways from the original authorization: antenna changed, Zig-Bee and 40MHz BW of 2.4G Wi-Fi are disabled through firmware, only supporting 2.4GHz Wi-Fi and BLE. All the circuits and components were the same as the original module, there is no hardware change. The summary changes filed under this application are:
OriginalModule PresentPortableDevice FCCID FCCID:XF6M4SB ContainsFCCID:XF6M4SB OriginalGrantDate:December31,2019 RadioSpec 2.4GWiFi/BLE/Zigbee Only2.4GWiFi(disable40MHzBW)/BLE ChipSupplyPower 1.8Vor3.3V AntennaType ChipAntenna AntennaGain 1dBi Only1.8V FPCAntenna 2dBi We have performed the SAR evaluation of this portable device and also re-measured the radiated spurious emissions and bandage measurement. Sincerely, Signature:
Jean Anne Booth CEO
1 2 3 4 | FCC Lab Authorization-signed | Cover Letter(s) | 50.28 KiB | November 29 2021 / November 30 2021 |
UnaliWear,Inc. 3410 Cherry Lane Austin, TX,78703 Date: 11/08/21 Federal Communications Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 Declaration of Authorization To whom it may concern, I the undersigned, hereby authorize, MRT Tehnology (Suzhou) Co., LTD, D8 Building, No.2 Tianedang Rd., Wuzhong Economic Development Zone, Suzhou, China (MRT), to act on our behalf in all manners relating to application for equipment authorization, including signing of all documents relating to these matters, for the following product(s):
Product: Single Band SIP Module, Small Form Factor Single Band 802.11b/g/n, Bluetooth 5.0, Zigbee Module FCC ID: XF6-M4SB Model: M4SB Company: Silicon Labs Any and all acts carried out by MRT on our behalf, of the named product(s) above, shall have the same effects as acts of our own. I, the undersigned, hereby certify that we are not subject to a denial of federal benefits, that includes FCC benefits, pursuant to Section 5301 of the Anti-Drug Abuse Act of 1988, 21 U.S.C 853(a). This authorization is valid for one hundred and twenty (120) days from 10/12/2021. Sincerely, Signature:
Jean Anne Booth CEO
1 2 3 4 | Modular Approval cover letter-BTwifi V3.0 | Cover Letter(s) | 171.50 KiB | November 29 2021 / November 30 2021 |
Request for Modular/Limited Modular Approval Date: November 25, 2021 Subject: Manufacturers Declaration for - Modular Approval Confidentiality Request for: ______XF6-M4SB_____
- Limited Modular Approval - Limited Split Modular Approval
- Split Modular Approval 8 Basic Requirements FCC Part 15.212(a)(1) For Items Marked NO(*), the Limited Module Description Must be Filled Out on the Following Pages Modular Approval Requirement 1. The modular transmitter must have its own RF shielding. This is intended to ensure that the module does not have to rely upon the shielding provided by the device into which it is installed in order for all modular transmitter emissions to comply with FCC limits. It is also intended to prevent coupling between the RF circuitry of the module and any wires or circuits in the device into which the module is installed. Such coupling may result in non-compliant operation. The physical crystal and tuning capacitors may be located external to the shielded radio elements. 15.212(a)(1)(i) Details: <example The module contains a metal shield which covers all RF components and circuitry. The shield is located on the top of the board next to antenna connector>
- YES - NO(*) Requirement Met 2. The modular transmitter must have buffered modulation/data inputs (if such inputs are provided) to ensure that the module will comply with FCC requirements under conditions of excessive data rates or over-modulation. 15.212(a)(1)(ii) Details: <example Data to the modulation circuit is buffered as described in the operational description provided with the application>
- YES - NO(*) 3. The modular transmitter must have its own power supply regulation on the module. This is intended to ensure that the module will comply with FCC requirements regardless of the design of the power supplying circuitry in the device into which the module is installed. 15.212(a)(1)(iii) Details: <example The module contains its own power supply regulation. Please refer to schematic filed with this application>
- YES - NO(*) 4. The modular transmitter must comply with the antenna and transmission system requirements of 15.203, 15.204(b), 15.204(c), 15.212(a), and 2.929(b). The antenna must either be permanently attached or employ a unique antenna coupler (at all connections between the module and the antenna, including the cable). The professional installation provision of 15.203 is not applicable to modules but can apply to limited modular approvals under paragraph 15.212(b). 15.212(a)(1)(iv) Details: <example The module connects to its antenna using an UFL connector which is considered a non-standard connector. A list of antennas tested and approved with this device may be found in users manual provided with the application>
- YES - NO(*) 5. The modular transmitter must be tested in a stand-alone configuration, i.e., the module must not be inside another device during testing. This is intended to demonstrate that the module is capable of complying with Part 15 emission limits regardless of the device into which it is eventually installed. Unless the transmitter module will be battery powered, it must comply with the AC line conducted requirements found in Section 15.207. AC or DC power lines and data input/output lines connected to the module must not contain ferrites, unless they will be marketed with the module (see Section 15.27(a)). The length of these lines shall be length typical of actual use or, if that length is unknown, at least 10 centimeters to insure that there is no coupling between the case of the module and supporting equipment. Any accessories, peripherals, or support equipment connected to the module during testing shall be unmodified or commercially available (see Section 15.31(i)). 15.212(a)(1)(v) Details: <example The module was tested with host device(watch), and the model of the watch was KANEGA003.>
- YES - NO(*) 070920-02b Modular Approval Requirement 6. The modular transmitter must be labeled with its own FCC ID number, or use an electron display Requirement Met
(see KDB Publication 784748). If using a permanently affixed label with its own FCC ID number, if the FCC ID is not visible when the module is installed inside another device, then the outside of the device into which the module is installed must also display a label referring to the enclosed module. This exterior label can use wording such as the following: Contains Transmitter Module FCC ID: XYZMODEL1 or Contains FCC ID: XYZMODEL1. Any similar wording that expresses the same meaning may be used. The Grantee may either provide such a label, an example of which must be included in the application for equipment authorization, or, must provide adequate instructions along with the module which explain this requirement. In the latter case, a copy of these instructions must be included in the application for equipment authorization. If the modular transmitter uses an electronic display of the FCC identification number, the information must be readily accessible and visible on the modular transmitter or on the device in which it is installed. If the module is installed inside another device, then the outside of the device into which the module is installed must display a label referring to the enclosed module. This exterior label can use wording such as the following: Contains FCC certified transmitter module(s). Any similar wording that expresses the same meaning may be used. The user manual must include instructions on how to access the electronic display. A copy of these instructions must be included in the application for equipment authorization. 15.212(a)(1)(vi) Details: <example There is a label on the module as shown in the labeling exhibit filed with this application. Host specific labeling instructions are shown in the installation manual .filed with this application.>
- YES - NO(*) 7. The modular transmitter must comply with all specific rule or operating requirements applicable to the transmitter, including all the conditions provided in the integration instructions by the grantee. A copy of these instructions must be included in the application for equipment authorization. For example, there are very strict operational and timing requirements that must be met before a transmitter is authorized for operation under Section 15.231. For instance, data transmission is prohibited, except for operation under Section 15.231(e), in which case there are separate field strength level and timing requirements. Compliance with these requirements must be assured. 15.212(a)(1)(vii) Details: <example The module complies with FCC Part 15C requirements. Instructions to the OEM installer are provided in the installation manual filed with this application.>
- YES - NO(*) 8. The modular transmitter must comply with any applicable RF exposure requirements. For example, FCC Rules in Sections 2.1091, 2.1093 and specific Sections of Part 15, including 15.319(i), 15.407(f), 15.253(f) and 15.255(g), require that Unlicensed PCS, UNII and millimeter wave devices perform routine environmental evaluation for RF Exposure to demonstrate compliance. In addition, spread spectrum transmitters operating under Section 15.247 are required to address RF Exposure compliance in accordance with Section 15.247(b)(4). Modular transmitters approved under other Sections of Part 15, when necessary, may also need to address certain RF Exposure concerns, typically by providing specific installation and operating instructions for users, installers and other interested parties to ensure compliance. 15.212(a)(1)(viii) Details: <example The module meets Portable exclusion levels as shown in the RF exposure information filed with this application.>
- YES - NO(*) 070920-02b Limited Module Description When Applicable
* If a module does NOT meet one or more of the above 8 requirements, the applicant may request Limited Modular Approval (LMA). This Limited Modular Approval (LMA) is applied with the understanding that the applicant will demonstrate and will retain control over the final installation of the device, such that compliance of the end product is always assured. The operating condition(s) for the LMA; the module is only approved for use when installed in devices produced by grantee. A description regarding how control of the end product, into which the module will be installed, will be maintained by the applicant/manufacturer, such that full compliance of the end product is always ensured should be provided here. Details: This module does NOT meet one of the above requirements, the applicant may request Limited Modular Approval
(LMA). Due this module was installed into one HOST. The HOST information was shown as below:
Host Name: Kanega Watch Model No.: KANEGA003 Brand Name: UnaliWear Software Considerations KDB 594280 / KDB 442812 (One of the following 2 items must be applied) Requirement Requirement Met 1. For non-Software Defined Radio transmitter modules where software is used to ensure compliance of the device, technical description must be provided about how such control is implemented to ensure prevention of third-party modification; see KDB Publication 594280. Details: <example The firmware of the device can not be modified or adjusted by the end user as described in a separate cover letter filed with this application. >
- Provided in Separate Cover Letter
- N/A 2. For Software Defined Radio (SDR) devices, transmitter module applications must provide a software security description; see KDB Publication 442812.
- Provided in Separate Cover Letter
- N/A Details: <example N/A>
Split Modular Requirements Requirement Provided in Manual 1. For split modular transmitters, specific descriptions for secure communications between front-end and control sections, including authentication and restrictions on third-party modifications; also, instructions to third-party integrators on how control is maintained. Details: <example N/A >
- Provided in Separate Cover Letter
- N/A 070920-02b OEM Integration Manual Guidance KDB 996369 D03 Section 2 Clear and Specific Instructions Describing the Conditions, Limitations, and Procedures for third-parties to use and/or integrate the module into a host device. Requirement Is this module intended for sale to third parties?
- YES
- No, If No, and LMA applies, the applicant can optionally choose to not make the following detailed info public. However there still needs to be basic integration instructions for a users manual and the information below must still be included in the operational description. If the applicant wishes to keep this info confidential, this will require a separate statement cover letter explaining the module is not for sale to third parties and that integration instructions are internal confidential documents. Items required to be in the manual See KDB 996369 D03, Section 2 As of May 1, 2019, the FCC requires ALL the following information to be in the installation manual. Modular transmitter applicants should include information in their instructions for all these items indicating clearly when they are not applicable. For example information on trace antenna design could indicate Not Applicable. Also if a module is limited to only a grantees own products and not intended for sale to third parties, the user instructions may not need to be detailed and the following items can be placed in the operational description, but this should include a cover letter as cited above. 1. List of applicable FCC rules. KDB 996369 D03, Section 2.2 a. Only list rules related to the transmitter. 2. Summarize the specific operational use conditions. KDB 996369 D03, Section 2.3 a. Conditions such as limits on antennas, cable loss, reduction of power for point to point 3. Limited Module Procedures. KDB 996369 D03, Section 2.4 systems, professional installation info a. Describe alternative means that the grantee uses to verify the host meets the necessary limiting conditions b. When RF exposure evaluation is necessary, state how control will be maintained such that compliance is ensured, such as Class II for new hosts, etc. 4. Trace antenna designs. KDB 996369 D03, Section 2.5 a. Layout of trace design, parts list, antenna, connectors, isolation requirements, tests for design verification, and production test procedures for ensuring compliance. If confidential, the method used to keep confidential must be identified and information provided in the operational description. 5. RF exposure considerations. KDB 996369 D03, Section 2.6 a. Clearly and explicitly state conditions that allow host manufacturers to use the module. Two types of instructions are necessary: first to the host manufacturer to define conditions (mobile, portable xx cm from body) and second additional text needed to be provided to the end user in the host product manuals. 6. Antennas. KDB 996369 D03, Section 2.7 a. List of antennas included in the application and all applicable professional installer instructions when applicable. The antenna list shall also identify the antenna types
(monopole, PIFA, dipole, etc note that omni-directional is not considered a type) 7. Label and compliance information. KDB 996369 D03, Section 2.8 a. Advice to host integrators that they need to provide a physical or e-label stating Contains FCC ID: with their finished product 8. Information on test modes and additional testing requirements. KDB 996369 D03, Section 2.9 a. Test modes that should be taken into consideration by host integrators including clarifications necessary for stand-alone and simultaneous configurations. b. Provide information on how to configure test modes for evaluation 9. Additional testing, Part 15 Subpart B disclaimer. KDB 996369 D03, Section 2.10
- All Items shown to the left are provided in the Modular Integration Guide (or UM) for Full Modular Approval
(MA) or LMA.
- An LMA applies and is approved ONLY for use by the grantee in their own products, and not intended for sale to 3rd parties as provided in a separate cover letter. Therefore the information shown to the left is found in the theory of operation. Sincerely, 070920-02b By:
_ ___ CEO______ __Jean Anne Booth___
(Signature/Title1 (Print name) 1 - Must be signed by applicant contact given for applicant on the FCC site, or by the authorized agent if an appropriate authorized agent letter has been provided. Letters should be placed on appropriate letterhead. 070920-02b
1 2 3 4 | ACB-FORM-FCC-Modular-Letter v1 | Cover Letter(s) | 281.85 KiB | March 19 2020 |
Request for Modular/Limited Modular Approval Date: March 19, 2020 Subject: Manufacturers Declaration for - Modular Approval Confidentiality Request for: _____ XF6-M4SB ______
- Limited Modular Approval - Limited Split Modular Approval
- Split Modular Approval For Items Marked NO(*), the Limited Module Description Must be Filled Out on the Following Pages Modular Approval Requirement Requirement Met 8 Basic Requirements FCC Part 15.212(a)(1) 1. The modular transmitter must have its own RF shielding. This is intended to ensure that the module does not have to rely upon the shielding provided by the device into which it is installed in order for all modular transmitter emissions to comply with FCC limits. It is also intended to prevent coupling between the RF circuitry of the module and any wires or circuits in the device into which the module is installed. Such coupling may result in non-compliant operation. The physical crystal and tuning capacitors may be located external to the shielded radio elements. 15.212(a)(1)(i) The radio portion of this module has been shielded, please see exhibition External Photo. 2. The modular transmitter must have buffered modulation/data inputs (if such inputs are provided) to ensure that the module will comply with FCC requirements under conditions of excessive data rates or over-modulation. 15.212(a)(1)(ii) The EUT has buffered data inputs, it is integrated in chip ALT1250TG. 3. The modular transmitter must have its own power supply regulation on the module. This is intended to ensure that the module will comply with FCC requirements regardless of the design of the power supplying circuitry in the device into which the module is installed. 15.212(a)(1)(iii) The part number of the regulator is ALT1250TG. 4. The modular transmitter must comply with the antenna and transmission system requirements of 15.203, 15.204(b), 15.204(c), 15.212(a), and 2.929(b). The antenna must either be permanently attached or employ a unique antenna coupler (at all connections between the module and the antenna, including the cable). The professional installation provision of 15.203 is not applicable to modules but can apply to limited modular approvals under paragraph 15.212(b). 15.212(a)(1)(iv) The EUT meets the FCC antenna requirements. 5. The modular transmitter must be tested in a stand-alone configuration, i.e., the module must not be inside another device during testing. This is intended to demonstrate that the module is capable of complying with Part 15 emission limits regardless of the device into which it is eventually installed. Unless the transmitter module will be battery powered, it must comply with the AC line conducted requirements found in Section 15.207. AC or DC power lines and data input/output lines connected to the module must not contain ferrites, unless they will be marketed with the module (see Section 15.27(a)). The length of these lines shall be length typical of actual use or, if that length is unknown, at least 10 centimeters to insure that there is no coupling between the case of the module and supporting equipment. Any accessories, peripherals, or support equipment connected to the module during testing shall be unmodified or commercially available (see Section 15.31(i)). 15.212(a)(1)(v) The EUT was tested in a stand-alone configuration inside a host. Please see exhibition Test Setup.
- YES - NO(*)
- YES - NO(*)
- YES - NO(*)
- YES - NO(*)
- YES - NO(*) 053019-02a 6. The modular transmitter must be labeled with its own FCC ID number, or use an electron display (see Modular Approval Requirement Requirement Met KDB Publication 784748). If using a permanently affixed label with its own FCC ID number, if the FCC ID is not visible when the module is installed inside another device, then the outside of the device into which the module is installed must also display a label referring to the enclosed module. This exterior label can use wording such as the following: Contains Transmitter Module FCC ID: XYZMODEL1 or Contains FCC ID:
XYZMODEL1. Any similar wording that expresses the same meaning may be used. The Grantee may either provide such a label, an example of which must be included in the application for equipment authorization, or, must provide adequate instructions along with the module which explain this requirement. In the latter case, a copy of these instructions must be included in the application for equipment authorization. If the modular transmitter uses an electronic display of the FCC identification number, the information must be readily accessible and visible on the modular transmitter or on the device in which it is installed. If the module is installed inside another device, then the outside of the device into which the module is installed must display a label referring to the enclosed module. This exterior label can use wording such as the following: Contains FCC certified transmitter module(s). Any similar wording that expresses the same meaning may be used. The user manual must include instructions on how to access the electronic display. A copy of these instructions must be included in the application for equipment authorization. 15.212(a)(1)(vi) Please see exhibition Label Sample for the FCC ID of this module. 7. The modular transmitter must comply with all specific rule or operating requirements applicable to the transmitter, including all the conditions provided in the integration instructions by the grantee. A copy of these instructions must be included in the application for equipment authorization. For example, there are very strict operational and timing requirements that must be met before a transmitter is authorized for operation under Section 15.231. For instance, data transmission is prohibited, except for operation under Section 15.231(e), in which case there are separate field strength level and timing requirements. Compliance with these requirements must be assured. 15.212(a)(1)(vii) The EUT is compliant with all applicable FCC rules. 8. The modular transmitter must comply with any applicable RF exposure requirements. For example, FCC Rules in Sections 2.1091, 2.1093 and specific Sections of Part 15, including 15.319(i), 15.407(f), 15.253(f) and 15.255(g), require that Unlicensed PCS, UNII and millimeter wave devices perform routine environmental evaluation for RF Exposure to demonstrate compliance. In addition, spread spectrum transmitters operating under Section 15.247 are required to address RF Exposure compliance in accordance with Section 15.247(b)(4). Modular transmitters approved under other Sections of Part 15, when necessary, may also need to address certain RF Exposure concerns, typically by providing specific installation and operating instructions for users, installers and other interested parties to ensure compliance. 15.212(a)(1)(viii) The EUT is compliant with all applicable RF exposure requirements.
- YES - NO(*)
- YES - NO(*)
- YES - NO(*) 053019-02a Limited Module Description When Applicable
* If a module does NOT meet one or more of the above 8 requirements, the applicant may request Limited Modular Approval (LMA). This Limited Modular Approval (LMA) is applied with the understanding that the applicant will demonstrate and will retain control over the final installation of the device, such that compliance of the end product is always assured. The operating condition(s) for the LMA;
the module is only approved for use when installed in devices produced by grantee. A description regarding how control of the end product, into which the module will be installed, will be maintained by the applicant/manufacturer, such that full compliance of the end product is always ensured should be provided here. This module does NOT meet one of the above requirements, the applicant may request Limited Modular Approval (LMA). Due this module was installed into one HOST. The HOST information was shown as below:
Host Name: Kanega Watch Model No.: KANEGA002 Brand Name: UnaliWear Software Considerations KDB 594280 / KDB 442812 (One of the following 2 items must be applied) Requirement Requirement Met 1. For non-Software Defined Radio transmitter modules where software is used to ensure compliance of the device, technical description must be provided about how such control is implemented to ensure prevention of third-party modification; see KDB Publication 594280. The firmware of the device can not be modified or adjusted by the end user. 2. For Software Defined Radio (SDR) devices, transmitter module applications must provide a software security description; see KDB Publication 442812.
- Provided in Separate Cover Letter
- N/A
- Provided in Separate Cover Letter
- N/A Details: <example N/A>
Split Modular Requirements Requirement Provided in Manual 1. For split modular transmitters, specific descriptions for secure communications between front-end and control sections, including authentication and restrictions on third-party modifications; also, instructions to third-party integrators on how control is maintained. Details: <example N/A >
- Provided in Separate Cover Letter
- N/A 053019-02a Requirement OEM Integration Manual Guidance KDB 996369 D03 Section 2 Clear and Specific Instructions Describing the Conditions, Limitations, and Procedures for third-parties to use and/or integrate the module into a host device. Is this module intended for sale to third parties?
- YES
- No, If No, and LMA applies, the applicant can optionally choose to not make the following detailed info public. However there still needs to be basic integration instructions for a users manual and the information below must still be included in the operational description. If the applicant wishes to keep this info confidential, this will require a separate statement cover letter explaining the module is not for sale to third parties and that integration instructions are internal confidential documents. Items required to be in the manual See KDB 996369 D03, Section 2 As of May 1, 2019, the FCC requires ALL the following information to be in the installation manual. Modular transmitter applicants should include information in their instructions for all these items indicating clearly when they are not applicable. For example information on trace antenna design could indicate Not Applicable. Also if a module is limited to only a grantees own products and not intended for sale to third parties, the user instructions may not need to be detailed and the following items can be placed in the operational description, but this should include a cover letter as cited above. 1. List of applicable FCC rules. KDB 996369 D03, Section 2.2 a. Only list rules related to the transmitter. 2. Summarize the specific operational use conditions. KDB 996369 D03, Section 2.3 a. Conditions such as limits on antennas, cable loss, reduction of power for point to point 3. Limited Module Procedures. KDB 996369 D03, Section 2.4 systems, professional installation info a. Describe alternative means that the grantee uses to verify the host meets the necessary limiting conditions b. When RF exposure evaluation is necessary, state how control will be maintained such that compliance is ensured, such as Class II for new hosts, etc. 4. Trace antenna designs. KDB 996369 D03, Section 2.5 a. Layout of trace design, parts list, antenna, connectors, isolation requirements, tests for design verification, and production test procedures for ensuring compliance. If confidential, the method used to keep confidential must be identified and information provided in the operational description. 5. RF exposure considerations. KDB 996369 D03, Section 2.6 a. Clearly and explicitly state conditions that allow host manufacturers to use the module. Two types of instructions are necessary: first to the host manufacturer to define conditions (mobile, portable xx cm from body) and second additional text needed to be provided to the end user in the host product manuals. 6. Antennas. KDB 996369 D03, Section 2.7 a. List of antennas included in the application and all applicable professional installer instructions when applicable. The antenna list shall also identify the antenna types
(monopole, PIFA, dipole, etc note that omni-directional is not considered a type) 7. Label and compliance information. KDB 996369 D03, Section 2.8 a. Advice to host integrators that they need to provide a physical or e-label stating Contains FCC ID: with their finished product 8. Information on test modes and additional testing requirements. KDB 996369 D03, Section 2.9 a. Test modes that should be taken into consideration by host integrators including clarifications necessary for stand-alone and simultaneous configurations. b. Provide information on how to configure test modes for evaluation 9. Additional testing, Part 15 Subpart B disclaimer. KDB 996369 D03, Section 2.10
- All Items shown to the left are provided in the Modular Integration Guide (or UM) for Full Modular Approval (MA) or LMA.
- An LMA applies and is approved ONLY for use by the grantee in their own products, and not intended for sale to 3rd parties as provided in a separate cover letter. Therefore the information shown to the left is found in the theory of operation. ______CEO_______________ _______ Jean Anne Booth ___________ Sincerely, By:
053019-02a
(Signature/Title1)
(Print name) 1 - Must be signed by applicant contact given for applicant on the FCC site, or by the authorized agent if an appropriate authorized agent letter has been provided. Letters should be placed on appropriate letterhead. 053019-02a
1 2 3 4 | CP2C RedPine FCC ISED Module Authorization v1 | Cover Letter(s) | 98.90 KiB | March 19 2020 |
Date: 03/18/2020 Declaration of Authorization To whom it may concern, We, the undersigned, hereby authorize Jean Anne Booth of UnaliWear, Inc. to make a Class II permissive change to FCC ID: XF6-M4SB and Class IV permissive change to IC:
8407A-M4SB for the following reason/s: portable operation usage in specific host device. This authorization gives authority to Jean Anne Booth to act on our behalf, as our agent, in the following matters related to the FCC and/or Innovation, Science and Economic Development Canada (ISED) approval of this product: report submittal, related correspondence, the signing of all documents relating to these matters, and any other lawful activity necessary to obtain this Class II permissive change and Class IV permissive change. Any act carried out by Jean Anne Booth within the scope of this authorization shall have the same effect as our own. Sincerely, Sekhar Abburi Vice President Systems & Software Redpine Signals, Inc.
1 2 3 4 | FCC Confidentiality Letter-signed | Cover Letter(s) | 46.40 KiB | March 19 2020 |
UnaliWear, Inc. 3410 Cherry Lane Austin, TX, 78703 Date: 02/28/20 Federal Communications Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 FCC ID: XF6-M4SB Sincerely, Signature:
Jean Anne Booth CEO Confidentiality Letter Pursuant to Sections 0.457 and 0.459 of the Commissions Rules, we hereby request confidential treatment of the information accompanying this application as outlined below:
To whom it may concern, Tune Up Procedure The above materials contain trade secrets and proprietary information not customarily released to the public. The public disclosure of these matters might be harmful to the applicant and provide unjustified benefits to its competitors. The applicant understands that pursuant to Rule 0.457, disclosure of this application and all accompanying documentation will not be made before the date of the Grant for this application.
1 2 3 4 | FCC C2PC Request-signed v1 | Cover Letter(s) | 60.75 KiB | March 19 2020 |
UnaliWear, Inc. 3410 Cherry Lane Austin, TX, 78703 Date: 02/28/2020 Federal Communications Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 FCC ID: XF6-M4SB Request for Class II Permissive Change To whom it may concern, This is a request to file a Class II permissive change for FCC ID: XF6-M4SB, originally granted on 12/31/19. In the new use case, this module is now being used in a portable device. The module has been changed in the following ways from the original authorization: antenna changed, Zig-Bee is disabled, only supporting 2.4GHz Wi-Fi and BLE. The summary changes filed under this application are:
Original Module Present Portable Device FCC ID FCC ID: XF6-M4SB Contains FCC ID: XF6-M4SB Original Grant Date: December 31, 2019 Radio Spec 2.4G Wi-Fi / BLE / Zigbee Only 2.4G Wi-Fi (disable 40MHz BW) / BLE Chip Supply Power 1.8V or 3.3V Only 1.8V Antenna Type Chip Antenna Copper Antenna Antenna Gain 1dBi
-1.78dBi The above changes were made by software, and the hardware was same as the original module. We have performed the SAR evaluation of this portable device and also re-measured the radiated spurious emissions. Sincerely, Signature:
Jean Anne Booth CEO
1 2 3 4 | Individual Product RedPine FCC Lab Authorization-signed | Cover Letter(s) | 44.20 KiB | March 19 2020 |
Unaliwear, Inc. 3410 Cherry Lane Austin, TX, 78703 Date: 02/28/20 Federal Communications Commission Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 Declaration of Authorization To whom it may concern, I the undersigned, hereby authorize, MRT Tehnology (Suzhou) Co., LTD, D8 Building, Youxin Industrial Park, No.2 Tianedang Rd., Wuzhong Economic Development Zone, Suzhou, China
(MRT) to act on our behalf in all manners relating to application for equipment authorization, including signing of all documents relating to these matters, for the following product(s):
Product: Single Band SIP Module, Small Form Factor Single Band 802.11b/g/n, Bluetooth 5.0, Zigbee Module FCC ID: XF6-M4SB IC: 8407A-M4SB Model: M4SB Brand: Redpine Signals Any and all acts carried out by MRT on our behalf, of the named product(s) above, shall have the same effects as acts of our own. I, the undersigned, hereby certify that we are not subject to a denial of federal benefits, that includes FCC benefits, pursuant to Section 5301 of the Anti-Drug Abuse Act of 1988, 21 U.S.C 853(a). This authorization is valid for one hundred and twenty days (120) from 02/28/20. Sincerely, Signature:
Jean Anne Booth CEO
1 2 3 4 | Confidential Authorization | Cover Letter(s) | 95.50 KiB | December 31 2019 |
Redpine Signals, Inc. 2107N,First Street,Suite 540 San Jose , CA95131-2019 Main::+1 408-748-3385 www.redpinesignals.com FCC Confidential Authorization 2019/11/18 FEDERAL COMMUNICATIONS COMMISSIONS Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 Subject: Confidentiality Request regarding application for certification of FCC ID: XF6-M4SB In accordance with Sections 0.457 and 0.459 of the Commissions Rules, Redpine Signals Inc hereby requests long-term confidential treatment of information accompanying this application as outlined below:
Block Diagram Schematics Operation Description As well as short-term (180 days) confidential treatment of information accompanying this application as outlined below:
Internal Photos Users Manual External Photos Test Set-up Photos The above materials contain proprietary and confidential information not customarily released to the public. The public disclosure of these materials provides unjustified benefits to its competitors in the market. Sincerely, ChandraSekhar Abburi Vice President/Systems & Software 2017 N. First Street, Suite 540, San Jose, CA 95131-2019 Redpine Signals, Inc. 2107 N. First Street, Suite #540, San Jose, CA 95131-2019 - Ph: +1 408-748-3385
1 2 3 4 | Modular Approval Letter | Cover Letter(s) | 92.71 KiB | December 31 2019 |
Redpine Signals, Inc. 2107N,First Street,Suite 540 San Jose , CA95131-2019 Main::+1 408-748-3385 www.redpinesignals.com Modular Approval Letter 2019/11/18 FEDERAL COMMUNICATIONS COMMISSIONS Authorization and Evaluation Division 7435 Oakland Mills Road Columbia, MD 21046 The modular transmitter must have its own RF shielding. The modular transmitter must have its own power supply regulator The modular transmitter must have buffered modulation/data inputs The modular transmitter must comply with the antenna requirement of section 15.203 and Subject: Modular Approval Letter The Device, FCC ID: XF6-M4SB , is seeking FCC authorization as a modular transmitter. The EUT meets the requirement for modular approval as detailed in FCC Public Notice DA 00-1407. Compliance to each of the requirements is described below:
1. Reply: YES 2. Reply: YES 3. Reply: YES 4. 15.204(c) Reply: YES 5. Reply: YES 6. Reply: YES 7. the manufacturer must provide adequate instruction along with the module to explain any such requirements Reply: YES 8. Reply: YES The modular transmitter must comply with any applicable RF exposure requirements The modular transmitter must comply with any specific rule or operating requirements and The modular transmitter must be labeled with its own FCC ID number The modular transmitter must be tested in a stand-alone configuration Sincerely Yours, ChandraSekhar Abburi Vice President/Systems & Software 2017 N. First Street, Suite 540, San Jose, CA 95131-2019 Redpine Signals, Inc. 2107 N. First Street, Suite #540, San Jose, CA 95131-2019 - Ph: +1 408-748-3385
1 2 3 4 | Test Setup Photos | Test Setup Photos | 495.52 KiB | December 31 2019 / June 28 2020 | delayed release |
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2022-12-28 | 2412 ~ 2462 | DTS - Digital Transmission System | Class II Permissive Change |
2 | 2021-11-30 | 2412 ~ 2462 | DTS - Digital Transmission System | |
3 | 2020-03-19 | 2412 ~ 2462 | DTS - Digital Transmission System | |
4 | 2019-12-31 | 2412 ~ 2462 | DTS - Digital Transmission System | Original Equipment |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 2 3 4 | Effective |
2022-12-28
|
||||
1 2 3 4 |
2021-11-30
|
|||||
1 2 3 4 |
2020-03-19
|
|||||
1 2 3 4 |
2019-12-31
|
|||||
1 2 3 4 | Applicant's complete, legal business name |
Silicon Labs
|
||||
1 2 3 4 |
Redpine Signals Inc
|
|||||
1 2 3 4 | FCC Registration Number (FRN) |
0018834648
|
||||
1 2 3 4 | Physical Address |
9th Floor, Maximus Towers 2B, Raheja Mindspace IT APIIC Software Layout
|
||||
1 2 3 4 |
2107 N.First Street, Suite 540
|
|||||
1 2 3 4 |
9th Floor, Maximus Towers 2B, Raheja Mindspace IT
|
|||||
1 2 3 4 |
Madhapur, HYDERABAD, N/A
|
|||||
1 2 3 4 |
San Jose, CA
|
|||||
1 2 3 4 |
India
|
|||||
1 2 3 4 |
United States
|
|||||
app s | TCB Information | |||||
1 2 3 4 | TCB Application Email Address |
t******@timcoengr.com
|
||||
1 2 3 4 |
h******@acbcert.com
|
|||||
1 2 3 4 |
b******@baclcorp.com
|
|||||
1 2 3 4 | TCB Scope |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
||||
app s | FCC ID | |||||
1 2 3 4 | Grantee Code |
XF6
|
||||
1 2 3 4 | Equipment Product Code |
M4SB
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 2 3 4 | Name |
S****** A****
|
||||
1 2 3 4 | Title |
Senior Director & Site Manager
|
||||
1 2 3 4 |
Vice President - Systems & Software
|
|||||
1 2 3 4 | Telephone Number |
+91-4********
|
||||
1 2 3 4 |
+1 40********
|
|||||
1 2 3 4 | Fax Number |
+91-4********
|
||||
1 2 3 4 |
+1 40********
|
|||||
1 2 3 4 |
s******@silabs.com
|
|||||
1 2 3 4 |
s******@redpinesignals.com
|
|||||
app s | Technical Contact | |||||
1 2 3 4 | Firm Name |
MRT Technology (Suzhou) Co., Ltd
|
||||
1 2 3 4 | Name |
R******** W********
|
||||
1 2 3 4 | Physical Address |
D8 Building, No.2 Tianedang Rd., Wuzhong Economic
|
||||
1 2 3 4 |
D8 Building, Youxin Industrial Park
|
|||||
1 2 3 4 |
Suzhou
|
|||||
1 2 3 4 |
Suzhou, 215104
|
|||||
1 2 3 4 |
China
|
|||||
1 2 3 4 | Telephone Number |
86-51******** Extension:
|
||||
1 2 3 4 | Fax Number |
86-51********
|
||||
1 2 3 4 |
r******@mrt-cert.com
|
|||||
app s | Non Technical Contact | |||||
1 2 3 4 | Firm Name |
MRT Technology (Suzhou) Co., Ltd
|
||||
1 2 3 4 | Name |
R**** W******
|
||||
1 2 3 4 | Physical Address |
D8 Building, Youxin Industrial Park
|
||||
1 2 3 4 |
Suzhou, 215104
|
|||||
1 2 3 4 |
China
|
|||||
1 2 3 4 | Telephone Number |
86-51******** Extension:
|
||||
1 2 3 4 | Fax Number |
86-51********
|
||||
1 2 3 4 |
r******@mrt-cert.com
|
|||||
app s | Confidentiality (long or short term) | |||||
1 2 3 4 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | Yes | ||||
1 2 3 4 | No | |||||
1 2 3 4 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
1 2 3 4 | Yes | |||||
1 2 3 4 | If so, specify the short-term confidentiality release date (MM/DD/YYYY format) | 06/28/2020 | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 2 3 4 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 2 3 4 | Equipment Class | DTS - Digital Transmission System | ||||
1 2 3 4 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Single Band SIP Module, Small Form Factor Single Band 802.11b/g/n, Bluetooth 5.0, Zigbee Module | ||||
1 2 3 4 | Single Band SIP Module,Small Form Factor Single Band 802.11b/g/n, Bluetooth 5.0, Zigbee Module | |||||
1 2 3 4 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 2 3 4 | Modular Equipment Type | Limited Single Modular Approval | ||||
1 2 3 4 | Single Modular Approval | |||||
1 2 3 4 | Purpose / Application is for | Class II Permissive Change | ||||
1 2 3 4 | Original Equipment | |||||
1 2 3 4 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | No | ||||
1 2 3 4 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 2 3 4 | Grant Comments | Class II Permissive Change as documented in this filing, by installing this module into the wireless device next to body for specific host(Silicon Labs with model of SMSK V2.1). Limited Single Modular Approval. Power Output listed is conducted power. SAR compliance for portable use conditions has been evaluated as described in this filing. The antenna(s) used for this transmitter must not transmit simultaneously with any other antenna or transmitter, except in accordance with FCC multi-transmitter product procedures or as described in this filing. The highest reported SAR value is 0.11W/kg. This device only supports 20MHz bandwidth mode for 2.4G WLAN and it also contains BLE transmitter and Zigbee transmitter. | ||||
1 2 3 4 | Class II Permissive Change as documented in this filing, by installing this module into the portable device for specific host(Kanega Watch with model of KANEGA003). Limited Single Modular Approval. Power Output listed is conducted power. End-users must be provided with transmitter operating conditions for satisfying RF exposure compliance. This device only supports 20MHz bandwidth mode for 2.4G WLAN and it also contains BLE transmitter. | |||||
1 2 3 4 | Class II Permissive Change as documented in this filing, by installing this module in the portable device for specific host (Kanega Watch with model of KANEGA002). Limited Single Modular Approval. Power Output listed is conducted at the antenna terminal. End users must be informed of the body worn requirements for satisfying RF Exposure compliance. The highest reported SAR value (Body-worn) is <0.10 W/kg. This device only supports 20MHz bandwidth mode for WiFi 2.4GHz transmitter. | |||||
1 2 3 4 | Modular Approval. Output power listed is conducted. This transmitter is approved for use in mobile RF exposure category configurations with the antenna(s) installed to provide a separation distance of at least 20 cm from all persons. This grant is valid only when the module is sold to OEM or OEM integrator. Co-location of this module with other transmitters that operate simultaneously is required to be evaluated using the FCC multi-transmitter procedures. The integrator must be provided with specific information required to satisfy RF exposure compliance for final host devices and installations. Compliance of this device in all final host configurations is the responsibility of the Grantee. Installation of this device into portable RF Exposure category host devices requires the submission of a Class II permissive change or new application. This device supports 20 MHz and 40 MHz bandwidth modes. | |||||
1 2 3 4 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 2 3 4 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 2 3 4 | Firm Name |
RF Exposure Lab, LLC
|
||||
1 2 3 4 |
MRT TECHNOLOGY (SHENZHEN) CO., LTD.
|
|||||
1 2 3 4 |
MRT Technology (Suzhou) Co., Ltd.
|
|||||
1 2 3 4 |
Bay Area Compliance Laboratories Corp.(Linkou Lab)
|
|||||
1 2 3 4 | Name |
T**** M****
|
||||
1 2 3 4 |
M******** C********
|
|||||
1 2 3 4 |
M******** C********
|
|||||
1 2 3 4 |
Z******** C****
|
|||||
1 2 3 4 | Telephone Number |
760 4********
|
||||
1 2 3 4 |
+86-5********
|
|||||
1 2 3 4 |
+86-5******** Extension:
|
|||||
1 2 3 4 |
886-2******** Extension:
|
|||||
1 2 3 4 | Fax Number |
+886-********
|
||||
1 2 3 4 |
t******@rfexposurelab.com
|
|||||
1 2 3 4 |
m******@mrt-cert.com
|
|||||
1 2 3 4 |
z******@baclcorp.com
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 15C | 2412 | 2462 | 0.15 | ||||||||||||||||||||||||||||||||||||
1 | 2 | 15C | 2402 | 2480 | 0.108 | ||||||||||||||||||||||||||||||||||||
1 | 3 | 15C | 2405 | 2480 | 0.091 | ||||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
2 | 1 | 15C | 2412 | 2462 | 0.074 | ||||||||||||||||||||||||||||||||||||
2 | 2 | 15C | 2402 | 2480 | 0.052 | ||||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
3 | 1 | 15C | 2412 | 2462 | 0.074 | ||||||||||||||||||||||||||||||||||||
3 | 2 | 15C | 2402 | 2480 | 0.052 | ||||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
4 | 1 | 15C | 2412 | 2462 | 0.15 | ||||||||||||||||||||||||||||||||||||
4 | 2 | 15C | 2402 | 2480 | 0.108 | ||||||||||||||||||||||||||||||||||||
4 | 3 | 15C | 2405 | 2480 | 0.091 |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC