UM11563 WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS Rev. 1 - 31 March 2021
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX
8M Quad EVK Running Android OS
Rev. 1 — 31 March 2021
Document information
Information Content
Keywords Wi-Fi Alliance (WFA), certification, 88W8997, i.MX 8M Quad EVK, Android 10,
WTS programs
Abstract Provides the step-by-step procedure of WFA certification for 88W8997-based
wireless modules on i.MX 8M Quad EVK running Android 10.NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
Revision history
Rev Date Description
v.1 20210331 Initial version
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
2 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
1 About this document
1.1 Purpose and scope
This document describes the test setup and procedure used for WFA certification of Wi-
Fi features like 802.11ac, 802.11n, protected management frames (PMF), WPA3, and
security vulnerability detection (SVD) of 88W8997 wireless SoC. This document applies
to 88W8997-based wireless module connected to i.MX 8M Quad EVK running Android
OS, and configured as a station (STA). The instructions apply to other similar platforms
and wireless SoC.
The users should be familiar with the user manuals reference UM11558 and UM11490.
1.2 References
Table 1. Reference documents
Document type Document title
User manual Getting Started with NXP-based Wireless Modules on i.MX 8M Quad
EVK Running Android 10 OS (UM11558) - User manual
User manual Feature Configuration Guide for NXP-based Wireless Modules on i.MX
8M Quad EVK (UM11490) - User manual
User manual Quick Start Guide i.MX 8M Quad Evaluation Kit (MCIMX8M-EVK) -
User manual
1.3 Considerations
The readers should have some knowledge of Wi-Fi terminologies and certification.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
3 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
2 Test setup
Figure 1 illustrates the test setup.
Figure 1. Test setup
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
4 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
2.1 Set up Linux host
Prepare the host laptop. You only need to do this once. Refer to Section 4.6 "Flashing
Android 10 image to eMMC" and Section 4.7.4 "Using scrcpy tool" in UM11558.
2.2 Compile i.MX image and flash the board
Follow the instructions in UM11558 to set up i.MX 8M Quad EVK Android image and
flash Android 10 image to eMMC.
2.3 Set up i.MX 8M Quad EVK board for testing
• Open a terminal on the Linux host with root access:
$ sudo su
• Run the following commands to enable adb
$ adb reboot bootloader
$ fastboot oem unlock #this command will take some time
$ fastboot reboot
$ adb root
$ adb disable-verity
$ adb reboot
$ adb root
$ adb remount
The driver is stored at the following location on i.MX 8M Quad EVK board: /vendor/lib/
modules
The firmware is stored at the following location on i.MX 8M Quad EVK board: /vendor/
firmware
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
5 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
3 WFA certification test procedure
This section shows the sequence of operations to run in order to test the Wi-Fi features.
3.1 Set up the serial console
Set up the test. See Section 2 "Test setup".
Follow these steps to setup the serial console and access the i.MX 8M Quad device
terminal:
• Open the serial console and login into the device
ubuntu@ubuntu-desktop:/# sudo minicom -s -D /dev/ttyUSBx
• ttyUSB0 or ttyUSB01 are the serial devices. The minicom setup configuration is given
below:
A - Serial Device : /dev/ttyUSBx
E - Bps/Par/Bits : 115200 8N1
F - Hardware Flow Control : No
G - Software Flow Control : No
• Save and exit.
3.2 Copy the required files
• Connect the device to the host machine (Linux/Windows) using a type C USB-OTG
cable.
• Use adb to push NXP_WTS_AGENT_U16_bin directory to i.MX 8M Quad EVK board:
The command on Linux host is as follows:
adb push /NXP_WTS_AGENT_U16_bin /data/
• Set the permission to the files within NXP_WTS_AGENT_U16_bin directory copied to
i.MX 8M Quad EVK board using the command:
evk_8mq:/ # chmod 777 * -Rf
• Copy the driver file set [bin_wlan/*] to NXP_WTS_AGENT_U16_bin directory
• Copy the utility and config file set [bin_wlan/*] to [/data/NXP_WTS_AGENT_U16_bin/]
on i.MX 8M Quad EVK board
• Copy the firmware file set [FW_Image/*] to /lib/firmware/nxp/ directory of i.MX 8M Quad
EVK board
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
6 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
3.3 Load the driver
Use the cd command to go to NXP_WTS_AGENT_U16_bin directory where the driver
files are located on i.MX board.
Note: By default the turbo mode is enabled in the firmware. Four WTS programs: VHT-
STAUT, VHT-APUT-HOSTAPD, 11N-STAUT, and 11N-APUT-HOSTAPD, require turbo
mode to be disabled. See Section 3.3.1 "Disable Turbo mode".
Run the shell script load.sh script to install the driver located in
NXP_WTS_AGENT_U16_bin directory.
evk_8mq:/ # ./load.sh
Note: The shell script changes with the feature being tested. Refer to the program
specific data for the script to use.
Check the version of the build with the following command:
evk_8mq:/ # ./mlanutl mlan0 version
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
7 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
3.3.1 Disable Turbo mode
• Convert the Turbo mode configuration file turbo_mode.conf to a binary format (.bin) so
the wireless driver can use it.
Configuration file:
#File : turbo_mode.conf
## WMM turbo mode config command
turbo_mode_set={
CmdCode=0x0016 # do NOT change this line
Action:2=0 # 1 - SET
OID:2=0x27 # OID_WMM_TURBO_MODE
Size:2=128
Value:128=5 # 1 -- Enable turbo_mode_1; 2 -- Enable
turbo_mode_2; otherwise, disable turbo_mode
}
The following command uses mlanutl utility to convert the configuration file to a binary
format. mlanutl utility is stored in /data/NXP_WTS_AGENT_U16_bin/ directory
./mlanutl hostcmd generate_raw
For Turbo mode:
evk_8mq:/ # ./mlanutl mlan0 hostcmd config/turbo_mode.conf
generate_raw turbo_mode.bin
• Copy the newly generated binary file turbo_mode.bin into the wireless firmware
directory. For Android operating systems, the directory is: /vendor/firmware/
• Change the driver load parameters:
– Go to NXP_WTS_AGENT_U16_bin directory where the load.sh script file is stored
– Use the insmod command to update the load.sh script file
– Add the driver load parameter init_hostcmd_cfg=turbo_mode.bin to load.sh
script
Note: Make sure to remove the driver load parameter
init_hostcmd_cfg=turbo_mode.bin from the load.sh script for the other WTS
programs than VHT-STAUT, VHT-APUT-HOSTAPD, 11N-STAUT, and 11N-APUT-
HOSTAPD.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
8 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
3.4 Start Sigma
Sigma automation test suite formerly named Wi-Fi Test Suite (WTS) is an automation
framework provided by Wi-Fi Alliance. All the test bed devices including Access Points,
test bed STAs, Sniffers and Traffic generator are controlled through the Unified CAPI
(Control API) Console (UCC). The CA and DUT control agents (wfa_ca and wfa_dut) are
components of the automation test suite.
3.4.1 Start Sigma for the DUT agent (wfa_dut)
• Open an scrcpy.adb shell to access the i.MX 8M Quad EVK board
• Go to NXP_WTS_AGENT_U16_bin directory where you have copied wfa_dut and
wfa_ca agents earlier
• Run the command to start wfa_dut DUT agent:
Syntax: ./wfa_dut
Where:
Command parameter Description
interface Interface name
dut_port Port number for the DUT
program_index Program index value. See Table 2.
Example
./wfa_dut lo 8000 2 // starts VHT-STAUT program for DUT port number 8000 and
lo interface
Command to get the DUT agent version:
wfa_dut -v (version)
Table 2 lists the program index values.
Table 2. WTS program index values
Program index WTS program
1 HE-STAUT
2 VHT-STAUT
3 VHT-STAUT-MWIFIEX
4 VHT-APUT-UAPUTL
5 VHT-APUT-HOSTAPD
6 TDLS
7 WMM-PS-STAUT
8 P2P-MWU
9 P2P-WS
10 PMF-STAUT
11 PMF-STAUT-MWIFIEX
12 PMF-APUT-UAPUTL
13 PMF-APUT-HOSTAPD
14 11N-STAUT
15 11N-STAUT-MWIFIEX
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
9 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
Table 2. WTS program index values...continued
Program index WTS program
16 11N-APUT-UAPUTL
17 11N-APUT-HOSTAPD
18 HS2-R1
19 HS2-R2
20 V-E-STAUT
21 WPA3-STAUT
22 WPA3-APUT-HOSTAPD
3.4.2 Start Sigma for the CA control agent (wfa_ca)
• Open another an scrcpy.adb shell
• Go to NXP_WTS_AGENT_U16_bin directory where you have copied wfa_ca
component files earlier
• Run the command to start wfa_ca CA agent:
Syntax: ./wfa_ca.sh
Where:
Command parameter Description
control interface Network control interface name
Example
./ca.sh eth0 // starts the control agent for eth0
3.4.3 Configure the traffic
Once the CA and DUT agents are running, run the following commands to forward traffic
from the host eth0 that is connected to i.MX 8M Quad EVK via a type C USB-OTG cable:
scrcpy.adb forward tcp:9002 tcp:9000
socat TCP4-LISTEN:9000,fork TCP4:localhost:9002
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
10 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
3.5 Access and configure i.MX 8M Quad EVK
This section describes the two ways to access and configure i.MX 8M EVK:
• Using the command-line interface (CLI)
• Using a graphical user interface (GUI)
Some Wi-Fi features are tested using GUI, other features are tested with CLI and some
features are tested using a combination of both GUI and CLI. Refer to Section 5 "Android
10 known limitations and workarounds".
3.5.1 Access and configure the device using CLI
Open a terminal window on the Linux host
Use adb to access the device. See Section 2.3 "Set up i.MX 8M Quad EVK board for
testing"
scrcpy.adb shell
Go to /data/NXP…bin/ directory
Run the script to load the driver:
./load.sh
3.5.2 Access and configure the device using GUI
• Open a terminal on the Linux host
• Run the command to open the GUI:
scrcpy -m 768
• Go to Settings > Network and Internal > Wi-Fi > Enable the Wi-Fi.
• Select the SSID of the desired AP.
• Enter the passphrase.
• Go to Advanced settings.
• Select DHCP for ip configuration and use Device MAC setting for the association.
• Select ok.
• Connect to the AP.
Once you have associated the device to the AP and used DHCP to send the ip to the
device, use the adb shell terminal and ping to the PC end point.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
11 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4 Certification program execution
4.1 PMF certification using CLI and GUI
4.1.1 Change the PMF settings using GUI
• Access the DUT. See Section 3.5.2 "Access and configure the device using GUI".
• Open the configuration file wpa_supplicant_overlay.conf located in /vendor/etc/wifi/
directory
• Add pmf=1 or pmf=2 according to the test case.
4.1.2 Change the PMF settings using CLI
• Use GUI to disable the Wi-Fi. See Section 3.5.2 "Access and configure the device
using GUI".
• Open a terminal window on the Linux host
• Create the configuration file wpa_supplicant_overlay.conf on the Linux host:
cat /vendor/etc/wifi/wpa_supplicant_overlay.conf
• Add pmf=1 or pmf=2 according to the test case.
• Push the configuration file to adb:
scrcpy.adb push wpa_supplicant_overlay.conf /data/
• Go to scrcpy.adb shell
• Copy the configuration file wpa_supplicant_overlay.conf from /data/ directory to /
vendor/etc/wifi/ directory.
• Use GUI to enable the Wi-Fi. See Section 3.5.2 "Access and configure the device using
GUI".
4.1.3 PMF test case 5.1
Associate STAUT to AP
• Edit wpa_supplicant_overlay.conf configuration file located in /vendor/etc/wifi/
• Add pmf=1. See Section 4.1.1 "Change the PMF settings using GUI" or Section 4.1.2
"Change the PMF settings using CLI"
• Associate to AP. See Section 3.5 "Access and configure i.MX 8M Quad EVK"
• Ping the PC-end point ip:
ping
Note: Repeat these steps for each scenario.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
12 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.1.4 PMF test case 5.2
Associate STAUT to AP
• Edit wpa_supplicant_overlay.conf configuration file located in /vendor/etc/
• Add pmf=2. See Section 4.1.1 "Change the PMF settings using GUI" or Section 4.1.2
"Change the PMF settings using CLI"
• Associate to AP. See Section 3.5 "Access and configure i.MX 8M Quad EVK"
• Ping the PC-end point ip:
ping
Note: Repeat these steps for each scenario.
4.1.5 PMF test case 5.3.3.1
Associate STAUT to AP
• Edit wpa_supplicant_overlay.conf configuration file located in /vendor/etc/wifi/
• Add pmf=1. See Section 4.1.1 "Change the PMF settings using GUI" or Section 4.1.2
"Change the PMF settings using CLI"
• Associate to AP. See Section 3.5 "Access and configure i.MX 8M Quad EVK"
• Ping the PC-end point ip:
ping
4.1.6 PMF test case 5.3.3.2
Associate STAUT to AP
• Edit wpa_supplicant_overlay.conf configuration file located in /vendor/etc/wifi/
• Add pmf=2. See Section 4.1.1 "Change the PMF settings using GUI" or Section 4.1.2
"Change the PMF settings using CLI"
• Associate to AP. See Section 3.5 "Access and configure i.MX 8M Quad EVK"
• Ping the PC-end point ip:
ping
4.1.7 PMF test case 5.3.3.3
Associate STAUT to AP
• Edit wpa_supplicant_overlay.conf configuration file located in /vendor/etc/wifi/
• Add pmf=1. See Section 4.1.1 "Change the PMF settings using GUI" or Section 4.1.2
"Change the PMF settings using CLI"
• Ping the PC-end point ip:
ping
Disable the Wi-Fi using GUI to send deauth frame to AP
• See Section 3.5.2 "Access and configure the device using GUI".
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
13 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.1.8 PMF test case 5.3.3.4
Associate STAUT to AP
• Edit wpa_supplicant_overlay.conf configuration file located in /vendor/etc/wifi/
• Add pmf=1. See Section 4.1.1 "Change the PMF settings using GUI" or Section 4.1.2
"Change the PMF settings using CLI"
• Associate to AP. See Section 3.5 "Access and configure i.MX 8M Quad EVK"
• Ping the PC-end point ip:
ping
4.1.9 PMF test case 5.3.3.5
Associate STAUT to AP
• Edit wpa_supplicant_overlay.conf configuration file located in /vendor/etc/wifi/
• Add pmf=1. See Section 4.1.1 "Change the PMF settings using GUI" or Section 4.1.2
"Change the PMF settings using CLI"
• Associate to AP. See Section 3.5 "Access and configure i.MX 8M Quad EVK"
• Ping the PC-end point ip:
ping
4.1.10 PMF test case 5.4.3.1
Associate STAUT to AP
• Edit wpa_supplicant_overlay.conf configuration file located in /vendor/etc/wifi/
• Add pmf=1. See Section 4.1.1 "Change the PMF settings using GUI" or Section 4.1.2
"Change the PMF settings using CLI"
• Associate to AP. See Section 3.5 "Access and configure i.MX 8M Quad EVK"
• Ping the PC-end point ip:
ping
4.1.11 PMF test case 5.4.3.2
Associate STAUT to AP
• Edit wpa_supplicant_overlay.conf configuration file located in /vendor/etc/wifi/
• Add pmf=1. See Section 4.1.1 "Change the PMF settings using GUI" or Section 4.1.2
"Change the PMF settings using CLI"
• Associate to AP. See Section 3.5 "Access and configure i.MX 8M Quad EVK"
• Ping the PC-end point ip:
ping
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
14 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.2 WPA3 SAE certification using CLI
Open a terminal window on the Linux host
Use adb to access the device. See Section 2.3 "Set up i.MX 8M Quad EVK board for
testing"
scrcpy.adb shell
Go to /data/NXP…bin/ directory
Run the script to load the driver:
./load.sh
4.2.1 WPA3 test case 5.2.1
Associate STAUT to AP using group 19
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 19
add_network
set_network 0 ssid "Wi-Fi-5.2.1"
set_network 0 ieee80211w 2
set_network 0 key_mgmt SAE
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "0123456789abcdef0123456789abcde"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
Re-association using PMK caching
• Disconnect the STAUT from the AP
disconnect
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
15 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
• Re-associate the STAUT to the AP
reassociate
• Delete the profile once you have finished the test case
remove_network 0
4.2.2 WPA3 test case 5.2.2
Associate STAUT to AP using group 19
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 19
add_network
set_network 0 ssid "Wi-Fi-5.2.2"
set_network 0 ieee80211w 2
set_network 0 key_mgmt SAE
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
16 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.2.3 WPA3 test case 5.2.3
Associate STAUT to AP using group 19
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 19
add_network
set_network 0 ssid "Wi-Fi-5.2.3"
set_network 0 ieee80211w 2
set_network 0 key_mgmt SAE
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
17 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.2.4 WPA3 test case 5.2.4
Associate STAUT to AP using group 19
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 19
add_network
set_network 0 ssid "Wi-Fi-5.2.4"
set_network 0 ieee80211w 1
set_network 0 key_mgmt SAE WPA-PSK
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678123456781234567812345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
18 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.2.5 WPA3 test case 5.2.5
Associate STAUT to AP using group 20
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 20
add_network
set_network 0 ssid "Wi-Fi-5.2.5"
set_network 0 ieee80211w 2
set_network 0 key_mgmt SAE
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
19 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
Associate STAUT to AP using group 21
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 21
add_network
set_network 0 ssid "Wi-Fi-5.2.5"
set_network 0 ieee80211w 2
set_network 0 key_mgmt SAE
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
20 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.2.6 WPA3 test case 5.2.6
Associate STAUT to AP[1]
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 19
add_network
set_network 0 ssid "Wi-Fi-5.2.6"
set_network 0 ieee80211w 2
set_network 0 key_mgmt SAE
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
21 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
Associate STAUT to AP[2]
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 19
add_network
set_network 0 ssid "Wi-Fi-5.2.6"
set_network 0 ieee80211w 2
set_network 0 key_mgmt SAE
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
22 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
Associate STAUT to AP[3]
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 19
add_network
set_network 0 ssid "Wi-Fi-5.2.6"
set_network 0 ieee80211w 2
set_network 0 key_mgmt SAE
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
23 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
Associate STAUT to AP[4]
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
SET sae_groups 19
add_network
set_network 0 ssid "Wi-Fi-5.2.6"
set_network 0 ieee80211w 2
set_network 0 key_mgmt SAE
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
24 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.3 Security improvement/enhancement certification using CLI
Open a terminal window on the Linux host
Use adb to access the device. See Section 2.3 "Set up i.MX 8M Quad EVK board for
testing"
scrcpy.adb shell
Go to /data/NXP…bin/ directory
Run the script to load the driver:
./load.sh
Follow the workaround in Section 5.2 "MAC randomization" for the scanning procedure.
4.3.1 Security improvement test case 5.2.2
Associate STAUT to AP
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
scan
scan_results
add_network
set_network 0 ssid "WiFi-5.2.2"
set_network 0 key_mgmt WPA-PSK
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
25 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
Repeat these steps for each scenario.
4.3.2 Security improvement test case 5.2.3
Associate STAUT to AP
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
scan
scan_results
add_network
set_network 0 ssid "Wi-Fi-5.2.3"
set_network 0 key_mgmt WPA-PSK
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
Repeat these steps for each scenario.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
26 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.3.3 Security improvement test case 5.2.4
Associate STAUT to AP
• Start wpa_supplicant utility located in /vendor/bin/hw/ directory
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP…bin/
wpa_supplicant.conf
• Open another adb shell.
• Go to /data/NXP..bin/
• Start wpa_cli
./wpa_cli
• Run the commands to configure the DUT through CLI:
scan
scan_results
add_network
set_network 0 ssid "Wi-Fi-5.2.4"
set_network 0 key_mgmt WPA-PSK
set_network 0 proto RSN
set_network 0 pairwise CCMP
set_network 0 group CCMP
set_network 0 psk "12345678"
enable_network 0
select_network 0
• Give the static ip to the wireless interface:
ifconfig wlan0
• Ping the PC end-point ip
ping -I wlan0
• Delete the profile once you have finished the test case
remove_network 0
Repeat these steps for each scenario.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
27 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.4 Wi-Fi 4 (802.11n) certification using GUI and CLI
• For 802.11n test suite, run the test cases with the following settings:
– Set WTS control agent to 0.
– Keep WTS traffic agent set to 1.
– Edit the files allinit_config.txt and Dut_Info.txt to use only WTS traffic agent for this
test suite.
• Open a terminal window on the Linux host
• Use adb to access the device. See Section 2.3 "Set up i.MX 8M Quad EVK board for
testing"
scrcpy.adb shell
• Go to /data/NXP…bin/ directory
• Run the script to load the driver:
./load_11N.sh
• Manually connect the DUT through GUI and get the ip address through DHCP. Refer to
Section 3.5.2.
4.4.1 Test case N-5.2.2
Disable the probe request check (set as comment).
Run the command on STAUT after the AP configuration:
iw dev wlan0 set power_save on
4.4.2 Test case N-5.2.14
Run the command to add the multicast route:
ip route add table wlan0 224.0.0.0/24 dev wlan0
4.4.3 Test case N-5.2.19
Manually add the network by setting the security as WPA2-PSK.
4.4.4 Test case N-5.2.26
Follow procedure provided in Section 5 "Android 10 known limitations and workarounds"
4.4.5 Test cases N-5.2.27
• Run the commented probe request check.
• Manually verify the probe request in the sniffer
4.4.6 Test case N-5.2.28
• Run the commented probe request check.
• Manually verify the probe request in the sniffer
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
28 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.4.7 Test case N-5.2.29
• Run the commented probe request check.
• Manually verify the probe request in the sniffer
4.4.8 Test case N-5.2.30
• Run the commented probe request check.
• Manually verify the probe request in the sniffer
4.4.9 Test case N-5.2.31
• Run the commented probe request check.
• Manually verify the probe request in the sniffer
4.4.10 Test case N-5.2.32
• Run the commented probe request check.
• Manually verify the probe request in the sniffer
4.4.11 Test case N-5.2.33
• Run the commented probe request check.
• Manually verify the probe request in the sniffer
4.4.12 Test case N-5.2.47
• Send ADDBA request from STAUT to AP1 on TID0:
ping -s 1000 -Q 192
4.4.13 Test case N-5.2.52
Run the commented probe response check.
4.4.14 Test case N-5.2.53
Manually associate for each scenario.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
29 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.5 Wi-Fi 5 (802.11ac) certification using GUI and CLI
• As there is no provision for using WTS_Traffic agent, the DUT configuration will be
commented out from the UCC scripts.
• Open a terminal window on the Linux host
• Use adb to access the device. See Section 2.3 "Set up i.MX 8M Quad EVK board for
testing"
scrcpy.adb shell
• Go to /data/NXP…bin/ directory
• Run the script to load the driver:
./load_11AC.sh
• Manually connect the DUT through GUI and get the ip address through DHCP. Refer to
Section 3.5.2.
4.5.1 Test case VHT-5.2.1
Comment the DUT configuration and use the following APIs:
• pause!assoc!
• wfa_control_agent_dut!device_list_interfaces,interfaceType,802.11!INTERFACEID,
$DUT_IF
• wfa_control_agent_dut!sta_get_bssid,interface,$DUT_IF!ID,$assoc_bssid
4.5.2 Test case VHT-5.2.26
• Use the API: pause!assoc!
• Refer to Section 5 "Android 10 known limitations and workarounds".
4.5.3 Test case VHT-5.2.27
• Use the API: pause!assoc!
• Run the commented probe request check
• Manually verify the probe request in the sniffer
4.5.4 Test case VHT-5.2.28
• Use the API: pause!assoc!
• Run the commented probe request check
• Manually verify the probe request in the sniffer
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
30 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.5.5 Test case VHT-5.2.51
Comment the DUT configuration and use the following APIs:
• pause!assoc!
• wfa_control_agent_dut!
traffic_send_ping,destination,wfa_console_tg,framesize,1000,frameRate,1,duration,10!
STREAMID,$DUT_PING
• sleep!10!
• wfa_control_agent_dut!traffic_stop_ping,streamID,$DUT_PING!ID,$P_SENT,$P_RECV
4.5.6 Test case VHT-5.2.52
Comment the DUT configuration and use the following APIs:
• pause!assoc!
• wfa_control_agent_dut!
traffic_send_ping,destination,wfa_console_tg,framesize,1000,frameRate,1,duration,10!
STREAMID,$DUT_PING
• sleep!10!
• wfa_control_agent_dut!traffic_stop_ping,streamID,$DUT_PING!ID,$P_SENT,$P_RECV
4.5.7 Test case VHT-5.2.57
Manually Associated and Disconnected for every scenario.
4.5.8 Test case VHT-5.2.62
The STAUT needs to reconnect with the AP after the AP changes the bandwidth and SS
switch (BW=20 MHz, SS=1) within the Operation Notification information element in the
beacon.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
31 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
4.6 Security vulnerability detection (SVD) (VU) certification
• Open a terminal window on the Linux host
• Use adb to access the device. See Section 2.3 "Set up i.MX 8M Quad EVK board for
testing"
scrcpy.adb shell
• Go to /data/NXP…bin/ directory
• Run the script to load the driver:
./load.sh
4.6.1 SVD test case 5.2.1
Select the static IP method in Advanced settings while associating through GUI and
assign a static IP address in a valid range.
4.6.2 SVD test case 5.2.5
Select the static IP method in Advanced settings while associating through GUI and
assign a static IP address in a valid range.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
32 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
5 Android 10 known limitations and workarounds
5.1 Wired and wireless interface concurrency not working
Limitation: Wired and wireless interface concurrency is not working
Issues with the certification execution
• The ping command with the static IP does not work without -I option.
• WTS Sigma Traffic Agent does not work
Workarounds
For 802.11n test suite:
• Run the test cases with WTS control agent support set to 0
• Keep WTS Traffic agent support set to 1
• Manually connect the DUT through GUI and get the ip address through DHCP
For 802.11ac test suite:
WTS does not consider WTS Traffic support unless the control agent support is available.
• Keep both WTS control agent support and WTS traffic agent support set to 1
• Comment out the DUT configuration from the UCC scripts.
The DUT connection will be done through GUI and DHCP ip address will be used.
5.2 MAC randomization
Limitation: MAC randomization
Issues with the certification execution
• The DUT every time uses random MAC for SCAN and association every time
• The probe request check is not possible through automation
• The DUT gets a new IP address for every new association
Workarounds
• For 802.11n and 802.11ac test cases, verify the probe request manually, even for test
cases where the probe response from the AP is verified.
• During the association through GUI, select Device MAC setting to ensure that the
device uses the same MAC in the association requests and gets the same IP address
from the DHCP server.
• For the security improvement/enhancement test cases, follow the procedure detailed
below to make sure that the DUT is transmitting the probe request:
– Check that Device MAC setting was selected in the previous testing done using
GUI. If not, associate to any AP through GUI by selecting use Device MAC setting.
– Reboot the device. Login using adb or minicom. Load the device.
– Start wpa_supplicant
./wpa_supplicant -Dnl80211 -i wlan0 -c /data/NXP...-Sigma-bin/
wpa_supplicant.conf
– Start wpa_cli
– Run the scan command from wpa_cli and then run the scan_results command.
– Repeat this 2 to 3 times.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
33 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
5.3 No auto connection when internet is not present
Limitation: No auto connection (re-association/roaming) when internet is not present.
Issues with the certification execution
• All the test cases involving re-association or roaming are impacted
Workarounds
• Reboot the adb device. Login using minicom or adb. Load the device
• Open the GUI and forget the saved networks if any
• Enable the Wi-Fi through GUI. Configure the AP, select the SSID of the AP and
associate by entering the passphrase. Select DHCP and use Device MAC for the
connection.
• Once the AP is associated, wait for a minute until the message pops up on the screen
asking if you want to save the network. Click Yes and associate.
• Disable the Wi-Fi.
• Enable the Wi-Fi again. If it doesn't associate to the SSID automatically, click on the
SSID and associate.
• Repeat this step until after disabling and enabling the Wi-Fi, the device doesn't
associate on its own.
• Once the device associates to the saved network just by disabling and enabling the Wi-
Fi, resume the test case.
5.4 DHCPD service is disabled as soon as Wi-Fi is disabled
Limitation: DHCPD service gets disabled as soon as Wi-Fi is disabled from the GUI
Issues with the certification execution
• Test cases where DHCP address cannot be tested using CLI, for example security
vulnerability detection SVD (VU).
Workarounds
For security vulnerability detection (SVD) (VU) certification:
• Use GUI for association
• Use the static IP for WPA3 test case 5.2.1 and WPA3 test case 5.2.5 as the DUT
is getting disconnected from the AP as it is not able to get DHCP IP for these two test
cases.
For the other certification programs:
• Use DHCP.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
34 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
5.5 The association requires the GUI and CLI combination
Limitation: Need to use the combination of GUI and CLI for the association
Issues with the certification execution
This limitation is not specific to Android 10 but as a specific configuration cannot be done
through GUI, a different approach is required for some test suites.
Workarounds
• Wi-Fi 4: Connection through GUI, DHCP IP address
• Wi-Fi 5: Connection through GUI, DHCP IP address
• WPA3-SAE: Connection through CLI, static IP address, ping with -I option
• Security improvement/enhancement: Connection through CLI, static IP address, ping
with -I option
• SVD (VU): Connection through GUI, DHCP & static IP address
• PMF: Connection through GUI, but manually modify wpa_supplicant.conf file to set
specific PMF settings, DHCP IP address.
5.6 wfaping script not working in roaming test case 5.2.26 on Android 10
STAUT
Limitation: wfaping script is not working in the roaming test case VHT-5.2.26 on Android
10 STAUT
Issues with the certification execution
• The Android 10 DUT removes the IP address including the Gateway details as soon as
it disconnects with the AP.
• wfaping terminates if the device does not have a valid gateway
• While roaming from one AP to another, the UCC starts the ping traffic immediately
• If the STAUT is taking longer (20-30sec) to connect to the new AP, as there is no IP
address and Gateway configured on the STAUT, wfaping terminates and ping does not
work. The ping is working manually but not through sigma.
Workarounds
Use WFA approval/Waiver to modify the UCC script for 11AC-5.2.26 test case by adding
40 sec sleep between the time when the AP is turned off and ping is run from the STAUT.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
35 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
6 Acronyms and abbreviations
Table 3. Abbreviations
Acronym Description
ADB Android debug bridge
BSP Board support package
AP Access point
CA Control agent
CAPI Control API
CLI Command line interface
DHCP Dynamic host configuration procedure
DUT Device under test
eMMC Embedded multimedia card
GUI Graphical user interface
PMF Protected management frames
SAE Simultaneous authentication of equals
STA Station
STAUT Station under test
SVD Security vulnerability detection
UCC Unified control API (CAPI) console
UUU Universal Update Utility
WAR Work around
WFA Wi-Fi Alliance
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
36 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
7 Contact information
Use the following links for more product details, queries and support.
Home page: www.nxp.com
Web support: nxp.com/support
NXP community: community.nxp.com
iMX community: community.nxp.com/community/imx
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
37 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
8 Legal information
the application or use by customer’s third party customer(s). Customer is
responsible for doing all necessary testing for the customer’s applications
8.1 Definitions and products using NXP Semiconductors products in order to avoid a
default of the applications and the products or of the application or use by
Draft — A draft status on a document indicates that the content is still customer’s third party customer(s). NXP does not accept any liability in this
under internal review and subject to formal approval, which may result respect.
in modifications or additions. NXP Semiconductors does not give any
representations or warranties as to the accuracy or completeness of Export control — This document as well as the item(s) described herein
information included in a draft version of a document and shall have no may be subject to export control regulations. Export might require a prior
liability for the consequences of use of such information. authorization from competent authorities.
Evaluation products — This product is provided on an “as is” and “with all
faults” basis for evaluation purposes only. NXP Semiconductors, its affiliates
8.2 Disclaimers and their suppliers expressly disclaim all warranties, whether express,
implied or statutory, including but not limited to the implied warranties of
non-infringement, merchantability and fitness for a particular purpose. The
Limited warranty and liability — Information in this document is believed
entire risk as to the quality, or arising out of the use or performance, of this
to be accurate and reliable. However, NXP Semiconductors does not
product remains with customer. In no event shall NXP Semiconductors, its
give any representations or warranties, expressed or implied, as to the
affiliates or their suppliers be liable to customer for any special, indirect,
accuracy or completeness of such information and shall have no liability
consequential, punitive or incidental damages (including without limitation
for the consequences of use of such information. NXP Semiconductors
damages for loss of business, business interruption, loss of use, loss of
takes no responsibility for the content in this document if provided by an
data or information, and the like) arising out the use of or inability to use
information source outside of NXP Semiconductors. In no event shall NXP
the product, whether or not based on tort (including negligence), strict
Semiconductors be liable for any indirect, incidental, punitive, special or
liability, breach of contract, breach of warranty or any other theory, even if
consequential damages (including - without limitation - lost profits, lost
advised of the possibility of such damages. Notwithstanding any damages
savings, business interruption, costs related to the removal or replacement
that customer might incur for any reason whatsoever (including without
of any products or rework charges) whether or not such damages are based
limitation, all damages referenced above and all direct or general damages),
on tort (including negligence), warranty, breach of contract or any other
the entire liability of NXP Semiconductors, its affiliates and their suppliers
legal theory. Notwithstanding any damages that customer might incur for
and customer’s exclusive remedy for all of the foregoing shall be limited to
any reason whatsoever, NXP Semiconductors’ aggregate and cumulative
actual damages incurred by customer based on reasonable reliance up to
liability towards customer for the products described herein shall be limited
the greater of the amount actually paid by customer for the product or five
in accordance with the Terms and conditions of commercial sale of NXP
dollars (US$5.00). The foregoing limitations, exclusions and disclaimers shall
Semiconductors.
apply to the maximum extent permitted by applicable law, even if any remedy
fails of its essential purpose.
Right to make changes — NXP Semiconductors reserves the right to
make changes to information published in this document, including without
Translations — A non-English (translated) version of a document is for
limitation specifications and product descriptions, at any time and without
reference only. The English version shall prevail in case of any discrepancy
notice. This document supersedes and replaces all information supplied prior
between the translated and English versions.
to the publication hereof.
Security — Customer understands that all NXP products may be subject
Suitability for use — NXP Semiconductors products are not designed,
to unidentified or documented vulnerabilities. Customer is responsible
authorized or warranted to be suitable for use in life support, life-critical or
for the design and operation of its applications and products throughout
safety-critical systems or equipment, nor in applications where failure or
their lifecycles to reduce the effect of these vulnerabilities on customer’s
malfunction of an NXP Semiconductors product can reasonably be expected
applications and products. Customer’s responsibility also extends to other
to result in personal injury, death or severe property or environmental
open and/or proprietary technologies supported by NXP products for use
damage. NXP Semiconductors and its suppliers accept no liability for
in customer’s applications. NXP accepts no liability for any vulnerability.
inclusion and/or use of NXP Semiconductors products in such equipment or
Customer should regularly check security updates from NXP and follow up
applications and therefore such inclusion and/or use is at the customer’s own
appropriately. Customer shall select products with security features that best
risk.
meet rules, regulations, and standards of the intended application and make
the ultimate design decisions regarding its products and is solely responsible
Applications — Applications that are described herein for any of these for compliance with all legal, regulatory, and security related requirements
products are for illustrative purposes only. NXP Semiconductors makes concerning its products, regardless of any information or support that may
no representation or warranty that such applications will be suitable be provided by NXP. NXP has a Product Security Incident Response Team
for the specified use without further testing or modification. Customers (PSIRT) (reachable at PSIRT@nxp.com) that manages the investigation,
are responsible for the design and operation of their applications and reporting, and solution release to security vulnerabilities of NXP products.
products using NXP Semiconductors products, and NXP Semiconductors
accepts no liability for any assistance with applications or customer product
design. It is customer’s sole responsibility to determine whether the NXP
Semiconductors product is suitable and fit for the customer’s applications
and products planned, as well as for the planned application and use of 8.3 Trademarks
customer’s third party customer(s). Customers should provide appropriate
design and operating safeguards to minimize the risks associated with Notice: All referenced brands, product names, service names and
their applications and products. NXP Semiconductors does not accept any trademarks are the property of their respective owners.
liability related to any default, damage, costs or problem which is based
on any weakness or default in the customer’s applications or products, or NXP — wordmark and logo are trademarks of NXP B.V.
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
38 / 40NXP Semiconductors
UM11563
WFA Certification for NXP-based Wireless Modules on i.MX 8M Quad EVK Running Android OS
Tables
Tab. 1. Reference documents ....................................... 3 Tab. 3. Abbreviations ...................................................36
Tab. 2. WTS program index values ...............................9
Figures
Fig. 1. Test setup ..........................................................4
UM11563 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2021. All rights reserved.
Rev. 1 — 31 March 2021
39 / 40You can also read
