NXP UM11434, IW416 User Manual

UM11434

IW416 Labtool User Guide

Rev. 2 — 2 February 2021 User manual

Document information

Information Content

Keywords Labtool test setup, Device under test (DUT) setup, driver, firmware, Labtool

application installation and usage, calibration data, Wi-Fi and Bluetooth Labtool commands, Bluetooth RF test sequences, Wi-Fi RF test sequences

Abstract Explains how to set up the Labtool test environment, how to install the driver

and firmware, and how to use the Labtool software application.

NXP Semiconductors

Revision history

Rev Date Description

v.1 20190917 Initial version v.2 20210202

Modifications

• Applied NXP branding and version numbering

• Section 1.1 "Purpose and scope": updated

• Section 2 "Labtool test setup": updated

• Section 3.1 "Linux Ubuntu installation": updated

• Section 3.3 "Software download": updated

• Section 3.4 "Building IW416 drivers": renamed (no change in the content)

• Section 3.5 "Building MFG bridge application and copying MFG firmware": renamed

and updated

• Section 3.6 "Loading IW416 driver and executing the firmware and bridge": renamed

and updated

• Section 4.1 "Labtool setup on Windows PC": renamed and updated

• Section 4.2 "Calibration data": updated

• Section 6.1 "Command 9: Get Tx/Rx antenna configuration (valid when Antenna

diversity is supported)": added

• Section 6.2 "Command 10: Set Tx/Rx antenna configuration (valid when Antenna

diversity is supported)": added

• Section 6.3 "Command 11: Get RF channel configuration": updated

• Section 6.5 "Command 13: Get RF data rate": added

• Section 6.14 "Command 34: Enable/disable BSSID filter": added

• Section 6.29 "Command 146: Get the number of calibrations done on OTP": added

• Section 6.33 "Command 198: Start RSSI data collection": added

• Section 6.34 "Command 199: Stop RSSI data collection and report result": added

• Section 6.35 "Wi-Fi RF test examples": added test examples for RSSI measurement

• Section 7.26 "Bluetooth RF test examples": updated

UM11434

IW416 Labtool User Guide

User manual Rev. 2 — 2 February 2021

2 / 68

NXP Semiconductors

1 Introduction

This document provides guidance for the installation and usage of IW416 Labtool application. The Labtool is a software test tool used to control and run various RF and regulatory compliance tests.

1.1 Purpose and scope

This document explains how to set up the IW416 Labtool test environment including the installation of IW416 driver, loading manufacturing firmware, and using Labtool software application. The Wi-Fi and Bluetooth radio Labtool commands are detailed along with some RF test examples.

1.2 References

Table 1 lists the references.

Table 1. References

Reference type Reference title

Datasheet DS - IW416 - Dual-band 1x1 Wi-Fi 4 and Bluetooth 5.1 Combo SoC

Design package RD-IW416-QFN-WIB3-1A-V2: design package for IW416 reference design

Design package RD-IW416-QFN-WIB3-2A-V2: design package for IW416 reference design

Design package RD-IW416-CSP-WIB3-1A-V1: design package for IW416 reference design

Design package RD-W8978-CSP-WIB3-2A-V1: design package for IW416 reference design

User manual UM11350 - IW416 Reference Design Kit User Guide

Application note AN12794 - IW416 Calibration Structure

UM11434

IW416 Labtool User Guide

with QFN package and one antenna

with QFN package and two antennas

with CSP package and one antenna

with CSP package and two antennas

User manual Rev. 2 — 2 February 2021

3 / 68

NXP Semiconductors

2 Labtool test setup

The Labtool is a test tool that enables RF testing for IW416 device. The Labtool is used for the following:

• Measurement of RF parameters such as transmit power, EVM, and receiver sensitivity

• Regulatory compliance testing (EMC/EMI)

The Labtool is part of the Manufacturing Software (MFG SW) package which includes the following components:

• Labtool application: this tool runs on a Windows PC

• IW416 device driver for Ubuntu Linux

• IW416 manufacturing (MFG) firmware: specialized firmware build that enables the

manufacturing test mode on IW416 device.

• Manufacturing bridge application: this application runs on the device under test (DUT). The bridge application enables Labtool application running on the Windows PC to communicate with the DUT over an ethernet interface.

Figure 1 shows a block diagram of a test setup running the Labtool. The test setup

includes:

UM11434

IW416 Labtool User Guide

1. Device Under Test (DUT): The DUT is a system that includes IW416 device. The DUT

needs the following software components:

• IW416 device driver and manufacturing firmware

• Manufacturing bridge application

If you are testing IW416 evaluation board using SDIO/UART interface or an IW416based wireless module, then connect the board or module to a PC/platform running Linux.

2. Windows PC: The Labtool application runs on a Windows PC

3. The RF tester, that is the test instrument

4. Ethernet switch

Windows PC running

Labtool

Device Under Test

(DUT)

RF Tester

Ethernet Switch

Ethernet Cable RF Cable

Figure 1. Labtool Test Setup

User manual Rev. 2 — 2 February 2021

4 / 68

NXP Semiconductors

3 Device under test setup

The host system provides the means for the Labtool to communicate with the DUT that runs on Linux Ubuntu.

This section details the installation of Linux Ubuntu on the (Linux) Bridge computer and the configuration setup prior to the download and build of the driver and firmware.

3.1 Linux Ubuntu installation

Install the Linux Ubuntu 16.04 along with the required tools and applications packages on the (Linux) Bridge computer. Perform this initial setup once. Subsequent releases will only require to copy IW416 firmware and driver files to their respective locations on the Bridge computer.

The procedure to set up a Bridge computer is as follows:

Step 1: Install Linux Ubuntu 16.04 system. The following command installs the 64-bit Linux Ubuntu system and is given as an example. You can also install the 32-bit Linux Ubuntu.:

UM11434

IW416 Labtool User Guide

$ Ubuntu-16.04.-desktop-amd64.iso

Step 2: Set up the environment.

Create a super-user or root administrator with the following command:

$ sudo bash # <user password>

Update the kernel and install the related patch with the following commands:

Ask your local NXP FAE for the kernel update package (Ubuntu_16.tgz) or download the

4.8.0 kernel from the internet.

Note: In case of a new requirement for the kernel or patch with the new release driver package, check the driver release notes included in the driver release package available on IW416 Tools and Software tab on NXP website.

$ tar -zxvf Ubuntu_16.tar $ cd Ubuntu_16 $ bash install.sh $ reboot

Step 3 - Check the kernel version and install the Ubuntu packages:

$ uname -r $ apt-get install vim $ apt-get install gawk $ apt-get install openssh-server $ apt-get install libnl-3-dev $ apt-get install libnl-gen1-3-dev $ apt-get install libreadline6-dev $ apt-get install libssl-dev $ apt-get install libbluetooth-dev $ apt-get install libncurses5-dev $ apt-get install libpcsclite-dev $ apt-get install libc6-dev-i386

User manual Rev. 2 — 2 February 2021

5 / 68

NXP Semiconductors

3.2 Linux bridge computer configuration

Step 1 - Disable the Linux firewall temporarily with the following command:

$ service iptables stop

Step 2 – Disable the open-source driver (mwifiex) to avoid a mutual conflict with NXP driver.

Execute the following commands to disable the open-source driver:

$ cd /lib/modules/`uname -r`/kernel/drivers/net/wireless/marvell/ mwifiex $ for f in `find -name '*mwifi*'`;do mv "$f" `echo "$f" | sed s/.ko/ _none/`;done $ cd /lib/modules/`uname -r`/kernel/drivers/BT $ for f in `find -name '*mrvl*'`;do mv "$f" `echo "$f" | sed s/.ko/ _none/`;done

3.3 Software download

UM11434

IW416 Labtool User Guide

The software packages are available for download on IW416 Tools and Software tab on NXP website.

Make sure to download the two software packages:

• IW416 production software release package

• IW416 MFG software release package

Note: Ask your local NXP FAE for specific software packages.

3.3.1 Production software release package

The production software release package includes the Wi-Fi and Bluetooth driver source code. Both the Wi-Fi and Bluetooth drivers are needed for Labtool testing.

IW416 production software is available for download on IW416 Tools and Software tab on NXP website.

Note: Ask your local NXP FAE for specific software packages.

3.3.2 MFG software release package

The MFG software release package includes the MFG firmware, the Labtool executable (.exe file), and the MFG bridge application. All three software items are needed for Labtool testing.

The MFG software release is published on IW416 Tools and Software Tab on NXP website.

User manual Rev. 2 — 2 February 2021

6 / 68

NXP Semiconductors

3.4 Building IW416 drivers

This section explains how to build both the Wi-Fi and Bluetooth drivers once you have downloaded the production software package published on IW416 Tools and Software

tab).

Note: IW416 device was formerly named 88W8978. The firmware and driver still refer to 8978 or 88W8978.

Step 1 – Open a terminal window on the (Linux) Host PC and use the cd command to the folder where the software is downloaded.

Step 2: Unzip the driver release package and all other files in it with the following commands:

$ tar -xvf SD-WLAN-SD-BT-8978-U16-MMC...pxx-GPL.tar $ tar -xzvf SD-BT-8978-U16-MMC-...-GPL-src.tgz $ tar -xzvf SD-BT-CHAR-8978-U16-MMC-...-GPL-src.tgz $ tar -xzvf SD-UAPSTA-8978-U16-MMC-...-mlan-src.tgz $ tar -xzvf SD-UAPSTA-8978-U16-MMC-...-app-src.tgz $ tar -xzvf SD-UAPSTA-8978-U16-MMC-...-GPL-src.tgz

The folder named SD-UAPSTA-UART-BT-8978-U16-MMC-...-GPL includes the WiFi and Bluetooth driver source code.

UM11434

IW416 Labtool User Guide

Step 3: Navigate to wlan_src directory and run the following commands to compile the

driver for Wi-Fi:

$ cd wlan_src $ make clean $ make build

After the compilation, the folder bin_sd8978 is created. It includes the Wi-Fi driver files mlan.ko and sd8xxx.ko.

Step 4: Navigate to mbt_src directory and run the following commands to compile the Bluetooth driver:

$ mbt_src $ make clean $ make build

After the compilation, the folder bin_sd8978_bt is created and includes the Bluetooth driver file bt8xxx.ko.

User manual Rev. 2 — 2 February 2021

7 / 68

NXP Semiconductors

3.5 Building MFG bridge application and copying MFG firmware

This section provides the steps for the installation of the MFG firmware and the build of the Bridge application.

Step 1: Navigate to the directory where the MFG software release package was downloaded and use the following command to extract the file:

$ cd <path-to-folder-with-mfg-software-release-package> $ unzip MFG-W8978-MF-WiFi-BT-BRG-FC-...-bin.zip

The extracted release package includes the following:

• The FwImage directory which includes the MFG Firmware

• The Bridge directory with the source code for the bridge application

• The release directory containing the Labtool executable for the Windows computer

Figure 2 shows the content of FwImage directory.

UM11434

IW416 Labtool User Guide

Figure 2. FwImage directory content

Step 2: Navigate to the FwImage directory and select the MFG firmware bin file that

matches the host interface type and copy it to the Linux firmware path /lib/firmware/nxp/.

For example, the firmware binary file sdio8978_sdio_combo.bin supports both Wi-Fi and Bluetooth over an SDIO interface. Run the commands to copy the bin file:

$ cd MFG_W8978...pxx/bin/FwImage $ cp sdio8978_sdio_combo.bin /lib/firmware/nxp/

If there is no folder with the name nxp under /lib/firmware/ path, run the commands to create the folder:

$ cd /lib/firmware/ $ mkdir nxp

Step 3: Go to the Bridge folder and compile the bridge application:

$ cd MFG_W8xxx...pxx/Bridge $ tar -xzvf bridge_linux_xx.xx.xx.xx-src.tgz $ cd bridge_linux_xx.xx.xx.xx/bridge $ make build

The mfgbridge application executable is created in the bin_mfgbridge directory.

User manual Rev. 2 — 2 February 2021

8 / 68

NXP Semiconductors

3.6 Loading IW416 driver and executing the firmware and bridge

The procedure to load the Wi-Fi and Bluetooth drivers and to run the Bridge application is as follows:

Step 1: Install Wi-Fi and Bluetooth drivers.

Go to the folder which includes the Wi-Fi driver files (mlan.ko and sd8xxx.ko), and run the following commands:

$ insmod mlan.ko $ insmod sd8978.ko mfg_mode=1 drv_mode=1 fw_name=nxp/ sdio8978_sdio_combo.bin cal_data_cfg=none $ dmesg $ iwconfig

Use the dmesg command to check the driver and firmware load status. If the status is correct the command output is as shown below. No message returns if either the firmware or driver did not load correctly.

WLAN FW is active wlan: Driver loaded successfully

UM11434

IW416 Labtool User Guide

Use the iwconfig command to confirm that the Wi-Fi device is defined as the mlan0 interface with the following messages:

mlan0 IEEE 802.11-DS ESSID:”” Mode:Auto channel=0 Access Point:Not-Associated Bit Rate:0 kb/s Tx_Power=off Retry limit:0 RTS thr=0 Fragment thr:off Power Management:off Link Quality=0/5 Signal level=0 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

Similarly, navigate to the folder which includes the Bluetooth driver file (bt8xxx.ko) and execute the following commands:

$ insmod bt8xxx.ko $ dmesg $ hciconfig

If the status is correct the command output is as shown below. No message returns if either the firmware or driver did not load correctly.

BT FW is active (0) BT: Driver loaded successfully

Use the hciconfig command to confirm that the Bluetooth device is defined as the hci0 interface with the following messages:

hci0 Type: BR/EDR Bus:SDIO BD Address: C0:95:DA:00:43:61 ACL MTU: 1021:7 SCO MTU: 120:6 UP RUNNING PSCAN RX bytes:824 acl:0 sco:0 events:41 errors:0 TX bytes:1168 acl:0 sco:0 events:41 errors:0

User manual Rev. 2 — 2 February 2021

9 / 68

NXP Semiconductors

If the Bluetooth is down, try to reset the Bluetooth interface to hci0 or disconnect IW416 board. Unload the drivers with the following commands:

$ rmmod sd8xxx.ko $ rmmod mlan.ko $ rmmod bt8xxx.ko

Step 2: Configure the DUT IP address.

We use the following IP addresses as examples in the commands shown for this step:

• (Linux) Bridge computer IP address: 192.168.0.10

• (Windows) Host computer IP address: 192.168.0.58

In the Linux system, configure the Ethernet IP address with the following command:

>ifconfig -a

Check the Ethernet name. The following command assumes the Ethernet name is ethx :

>ifconfig ethx 192.168.0.10

UM11434

IW416 Labtool User Guide

Check the Ethernet connection state between the (Windows) Host computer and the (Linux) Bridge computer using the ping command.

In the Windows Terminal window, execute the following command:

>ping 192.168.0.10

In the Linux platform terminal execute the following command:

>ping 192.168.0.58

Ensure that both the (Windows) Host computer and (Linux) Bridge computer IP addresses are under the same subnet.

Step 3: Run the bridge application.

Go to the bridge folder under the MFG release package where the bridge application was compiled previously, and run the bridge application with the following command:

$./mfgbridge

To terminate the bridge application, type CTRL+C in the bridge window.

To restart the bridge application, execute the ./mfgbridge command again.

User manual Rev. 2 — 2 February 2021

10 / 68

NXP Semiconductors

4 Windows PC setup

4.1 Labtool setup on Windows PC

The Host computer runs on Windows operating system (64 bit and 32 bit). The procedure to set up the environment is as follows:

Step 1: Download the MFG software release package MFG-W8xxx...pax.bin published on IW416 Tools and Software tab on NXP website. The MFG software release package includes the MFG firmware, the Labtool executable (.exe file), and the MFG bridge application. All three software items are needed for Labtool testing.

Step 2: Unzip the MFG firmware software release.

Step 3 - Copy the ...bin/release/labtool folder to the Host computer and make sure the

path length has less than 255 characters. Figure 3 shows the labtool repository content:

UM11434

IW416 Labtool User Guide

Figure 3. Labtool Repository Content

Step 4: Disable the Windows firewall.

Step 5: Open the Network and Sharing Center on the Windows PC. Change the network

address of the Ethernet port to the same subnet as the (Linux) Bridge computer. The following IP addresses are used in this document:

• (Windows) Host computer: 192.168.0.58

• (Linux) Bridge computer: 192.168.0.10

User manual Rev. 2 — 2 February 2021

11 / 68

NXP Semiconductors

Step 6: Open the SetUp.ini file using a text editor. The value of the parameter

DutIpAddress is the IP address of the DUT. The parameter HostIpAddress is the IP address of the Windows PC. Edit the file as follows:

[DutIp] DutIpAddress = 192.168.0.10 HostIpAddress = 192.168.0.58 Protocol = TCP

Step 7: In the SetUp.ini file, the parameter NO_EEPROM is used to specify the calibration data storage option. The default value is 1 (Use calibration data from the external configuration file).

For general RF evaluation and test, set the file option to 1 to use the calibration data from an external file. If the calibration data is already stored in the OTP memory of IW416 device, set the value to 2.

[DutInitSet] 0 = EEPROM support 1 = No_EEPROM support 2 = OTP support NO_EEPROM = 1 NoEepromBtFlexFileName = WlanCalData_ext.conf NoEepromWlanFlexFileName = WlanCalData_ext.conf

UM11434

IW416 Labtool User Guide

Note: No_EEPROM support refers to the calibration data from the external configuration file.

Step 8: Save the “SetUp.ini” file after making the changes.

User manual Rev. 2 — 2 February 2021

12 / 68

NXP Semiconductors

4.2 Calibration data

The DUT requires calibration data for optimal performance. The calibration data is included in the .conf file or programmed into the on-chip OTP memory of IW416 device. The .conf file is included in the reference design package for the WLCSP and QFN packages available on IW416 Tools and Software tab. See Figure 4.

Before launching the Labtool, copy the .conf file into the Labtool working directory and rename the file as WlanCalData_ext.conf (see Figure 5).

Figure 4. Calibration data file (.conf)

UM11434

IW416 Labtool User Guide

Figure 5. WlanCalData_Ext.conf in Labtool directory

User manual Rev. 2 — 2 February 2021

13 / 68

NXP Semiconductors

5 Labtool usage

5.1 Starting Labtool

Ensure the bridge application is running prior to starting the Labtool application. The procedure to start the Labtool application is as follows:

Step 1: Double-click on DutApiSisoBt.exee. Figure 6 shows the Labtool start window:

UM11434

IW416 Labtool User Guide

Figure 6. Labtool start window

Step 2: At the command prompt, enter “1” to start the Wi-Fi radio operation or “2” to start

the Bluetooth radio operation.

Step 3: To confirm whether the bridge and host setups are working properly, issue the command 88 to check the firmware and Labtool version number.

• If the correct version numbers are returned, start the RF test procedure.

• If the version numbers are incorrect, check the host, DUT, and bridge connections.

Confirm the Wi-Fi and Bluetooth drivers are installed correctly.

Figure 7 shows the correct state of command 88 execution.

User manual Rev. 2 — 2 February 2021

14 / 68

NXP Semiconductors

UM11434

IW416 Labtool User Guide

Figure 7. Command 88 execution

User manual Rev. 2 — 2 February 2021

15 / 68

NXP Semiconductors

5.2 Running commands

Each time a Labtool command is executed, the console returns a status byte. A successful command execution is indicated by a status byte with all 0s (Figure 8).

Figure 8. Status – Successful command execution

A failed command returns invalid data and is indicated by a non-0 status byte (0x00000001 to 0xFFFFFFFF). This could indicate a problem with the communication to the DUT, incorrect firmware, no firmware download, wrong version of Labtool/firmware, and so on.

UM11434

IW416 Labtool User Guide

Figure 9. Status – Failed command execution

When using the transmit commands (25, 33, 35), note that all the Very High Throughput (VHT) rates are not available for all bandwidth and antenna path combinations. An error code in the returned status byte of 0xE indicates that the rate is not supported by the DUT. Enter a “?” at the Labtool prompt to list all the available commands.

5.3 Closing Labtool

To close Labtool, issue Command 99 once.

To quit Labtool, issue command 99 twice.

5.4 Getting help

The Labtool application realizes its functions (such as enable Tx/Rx tests) through the related Labtool commands. Labtool commands are listed in the Command Line Interface (CLI) menu.

Enter ? at the command prompt in the main window to get the CLI menu.

Enter <command number>? for the detailed usage and help menu for the respective command.

For example, enter 10?.to get the detailed Command 10 usage (including the command options) and related help file are shown in the main window.

User manual Rev. 2 — 2 February 2021

16 / 68

NXP Semiconductors

6 Wi-Fi Labtool commands

Table 2. Wi-Fi Labtool command summary

Command

Command 9: Get Tx/Rx antenna configuration (valid when Antenna diversity is supported)

Command 10: Set Tx/Rx antenna configuration (valid when Antenna diversity is supported)

Command 11: Get RF channel configuration

Command 12: Set RF channel configuration

Command 13: Get RF data rate

Command 18: Set transmitter in CW mode

Command 22: Set power at antenna using calibration data

Command 25: Transmit with duty cycle Tx mode

Command 29: Get RF band configuration

Command 30: Set RF band configuration

Command 31: Clear Rx packet count

Command 32: Get and clear Rx packet count

Command 33: Transmit multicast packets

Command 34: Enable/disable BSSID filter

Command 35: Transmit with SIFS gap

Command 38: Transmit unicast packet

Command 44: Storage type get/set function

Command 45: Read MAC address from OTP

Command 46: Write MAC address to OTP

Command 53: Set calibration data to storage from text file

Command 54: Get calibration data from storage into file

Command 88: Get firmware/hardware version

Command 95: Get XTAL calibration offset

Command 96: Set XTAL calibration offset

Command 99: Exit Labtool application

Command 111: Get channel bandwidth

Command 112: Set channel bandwidth

Command 144: Read OTP raw data

Command 146: Get the number of calibrations done on OTP

Command 147: Get free lines in OTP

Command 148: Write patch block to OTP

Command 149: Write user data to OTP

Command 198: Start RSSI data collection

Command 199: Stop RSSI data collection and report result

UM11434

IW416 Labtool User Guide

User manual Rev. 2 — 2 February 2021

17 / 68

NXP Semiconductors

6.1 Command 9: Get Tx/Rx antenna configuration (valid when Antenna diversity is supported)

This command is used to check which antenna is connected to the Wi-Fi radio when more than one antenna is used for Antenna diversity application.

Syntax: 9

Return data: GetTxAntenna: Antenna X (where X = 1 or 2)

6.2 Command 10: Set Tx/Rx antenna configuration (valid when Antenna diversity is supported)

This command is used to set the desired antenna to the Wi-Fi radio when more than one antenna is used for Antenna diversity application

Syntax: 10 <antenna number>

Where:

Command parameter Description

antenna number Number used to qualify the Tx/Rx antenna

UM11434

IW416 Labtool User Guide

1 = Main 2 = Aux

Example

10 1 // Sets the main antenna

Return data:

• Successful command: all-0 status byte (0x00000000)

• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)

User manual Rev. 2 — 2 February 2021

18 / 68

NXP Semiconductors

6.3 Command 11: Get RF channel configuration

This command returns the values of the current RF channel, such as channel and offset.

Syntax: 11

Return data

Channel: Current channel number (see Section 8.1 "RF channels")

Offset: Boundary (applicable to non-20 MHz bandwidth channel)

• 0x1 = lower boundary of channel

• 0x3 = upper boundary of channel

Offset = 1 indicates that the channel number displayed (or set, in the case of Command

12) is the lower boundary of the channel.

If the channel bandwidth is 40 MHz (2.4 GHz band) and the channel center is 8, the Labtool reports Ch 6 with offset 1 or Ch 10 with offset 3.

6.4 Command 12: Set RF channel configuration

UM11434

IW416 Labtool User Guide

This command sets the RF channel. Specify the RF channel in the appropriate band (2.4 GHz or 5 GHz) or an error will occur.

Syntax: #23 <channel>

Where:

Command parameter Description

Channel Channel number

When 40 MHz bandwidth is enabled, then the channel specified is the left most/lower channel.

Examples

12 6 // Sets Ch 6 in 20 MHz bandwidth mode

112 1 // Sets to 40 MHz bandwidth 12 36 // Sets Ch 36 with offset 1 (Ch 36 + Ch 40 boned pair)

12 6 // Sets Ch 6 in 20 MHz bandwidth mode

112 1 // Sets to 40 MHz bandwidth 12 40 // Sets Ch 40 with offset 3 (Ch 36 + Ch 40 bonded pair)

Return data:

• Successful command: all-0 status byte (0x00000000)

• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)

User manual Rev. 2 — 2 February 2021

19 / 68

NXP Semiconductors

6.5 Command 13: Get RF data rate

This command is used to check the current data rate set for the Wi-Fi radio.

Syntax: 13

Example(s)

13 // reads back current data rate for Wi-Fi radio

Return data: DataRate: X // Where X is the number associated with the data rate. See

Table 3

Table 3. RF data rates

UM11434

IW416 Labtool User Guide

DataRate (X) RF data rate

1 1M 2 2M 3 5.5M 4 11M 5 22M 6 6M 7 9M 8 12M

9 18M 10 24M 11 36M 12 48M 13 54M 14 72M 15 MCS0 16 MCS1 17 MCS2 18 MCS3 19 MCS4 20 MCS5 21 MCS6 22 MCS7 47 MCS32

User manual Rev. 2 — 2 February 2021

20 / 68

NXP Semiconductors

6.6 Command 18: Set transmitter in CW mode

This command transmits an un-modulated carrier as a Continuous Wave (CW) tone.

Syntax: 18 <Enable>

Where:

Command parameter Description

Enable Mode enable

Examples

18 1 // Turns on transmission

18 0 // Turns off transmission

Return data:

• Successful command: all-0 status byte (0x00000000)

• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)

UM11434

IW416 Labtool User Guide

0 = disable (default) 1 = enable

6.7 Command 22: Set power at antenna using calibration data

This command sets the Tx power at the antenna using stored calibration data.

Syntax: 22 <channel> <power level> <modulation> <forceCalData>

Where:

Command parameter Description

channel Tx Channel

See Section 8.1. Default = Ch 6.

power level Tx Power Level (dBm)

modulation Modulation

00 = 802.11b CCK (default) 01 = 802.11g/a/p OFDM 10 = 802.11n MCS

forceCalData Force calibration data

Valid only for NO_EEPROM mode 0 = download calibration data only if not downloaded yet (default) 1 = force configuration file to be downloaded

Example

22 6 13 1 1 // Sets power for Ch 6, 13 dBm transmit power with OFDM modulation rates, and forces the configuration file download

Return data:

• Successful command: all-0 status byte (0x00000000)

• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)

User manual Rev. 2 — 2 February 2021

21 / 68

+ 47 hidden pages