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 typeReference title
DatasheetDS - IW416 - Dual-band 1x1 Wi-Fi 4 and Bluetooth 5.1 Combo SoC
Design packageRD-IW416-QFN-WIB3-1A-V2: design package for IW416 reference design
Design packageRD-IW416-QFN-WIB3-2A-V2: design package for IW416 reference design
Design packageRD-IW416-CSP-WIB3-1A-V1: design package for IW416 reference design
Design packageRD-W8978-CSP-WIB3-2A-V1: design package for IW416 reference design
User manualUM11350 - IW416 Reference Design Kit User Guide
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
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:
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.
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.
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.
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:
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.
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:
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.
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
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.
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
6.11 Command 31: Clear Rx packet count
This command clears the packet count register (start Rx Frame Error Rate (FER) test).
The receiver continuously counts the received multi-cast packets.
Syntax: 31
Return data:
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
6.12 Command 32: Get and clear Rx packet count
This command gets the counts for Rx, multi-cast and error packets, and clears the Rx
packet counter (stop Rx FER test).
Syntax: 32
Return data: Displays the received multi-cast packet count
This command transmits a specific number of multicast packets. It is used for measuring
Rx sensitivity if connected to another radio module, such as a receiver
This command continuously transmits standard 802.11 packets with an adjustable time
gap specified by a configurable Short Interframe Space (SIFS) interval of 0 to 250 µs.
SLPService location protocol (SLP) parameter used to enable/disable
SignalBwSignal bandwidth
PowerIDPower ID
BSSIDBasic Service Set ID
UM11434
IW416 Labtool User Guide
Default is 0x400.
Default is 0x64.
See Section 8.2 "Data rates" for mapping.
Some data rates are only available in some channel bandwidth modes.
Default is 4.
Default is 0xB496DEB6 for MFG testing
0 = disable (default)
1 = enable
steering
0 = disable
1 = enable (default)
0 = 20 MHz
1 = 40 MHz
-1 = follow deviceBW as in Section 6.26 "Command 111: Get channel
bandwidth" and Section 6.27 "Command 112: Set channel bandwidth"
(default)
Set to -1. See Section 6.7 "Command 22: Set power at antenna using
calibration data" for Power ID mapping
The format is xx.xx.xx.xx.xx.xx. If is not set, all 0xFs will be used.
Example
38 400 64 4 AA 1 1 -1 -1 00.50.43.11.22.33 // Transmits 100 unicast
packets with 1024-byte payload at data rate of 11 Mbps, data pattern “AA”, enables SLP,
and MAC is 00.50.43.11.22.
Return data:
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
This command sets the 8-bit crystal calibration offset to adjust the frequency offset when
viewed on a Vector Signal Analyzer (VSA), a spectrum analyzer, or a frequency counter.
Syntax: 96 <XTAL offset value>
Where:
Command parameterDescription
XTAL offset valueCrystal offset value comprised between 0x00 and 0xFF
Example(s)
96 AA // Sets crystal offset value to 0xAA.
Return data:
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
UM11434
IW416 Labtool User Guide
6.25 Command 99: Exit Labtool application
This command exits either the Wi-Fi or Bluetooth menu. A second Command 99 will exit
the Labtool and close the command prompt window.
Syntax: 99
Return data: --
6.26 Command 111: Get channel bandwidth
This command returns the channel bandwidth in use.
This command checks and returns the free lines in OTP.
Syntax: 147
Return data: Free lines on OTP
6.31 Command 148: Write patch block to OTP
This command writes the special binary file patch into OTP. For example, the regulatory
power table bin file is programmed into OTP using this command.
Syntax: 148 <Bin File>
Where:
Command parameterDescription
Bin FileName of the binary file to be written into OTP
UM11434
IW416 Labtool User Guide
If left blank, default patch block file “PatchBlockFileOTP.bin” is used.
Return data:
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
6.32 Command 149: Write user data to OTP
This command writes the user data bin file into OTP.
Syntax: 149 <User Data>
Where:
Command parameterDescription
User DataUser Bin File to be Written into OTP
If left blank, default user data file “UserDataFileOTP.bin” is used.
Return data:
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
6.34 Command 199: Stop RSSI data collection and report result
This command is used to stop RSSI measurement and report the RSSI result. The RSSI
measurement report includes the number of packets received, the measured RSSI value,
and the measured noise floor (NF) value.
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
7.13 Command 88: Get firmware/hardware version
This command returns the firmware, hardware, and Labtool versions.
Syntax: 88
Return data:
• DLL version: 1.0.0.10
• Labtool version: 1.0.0.10
• Firmware version: 16.80.10.127
• Mfg Version: 1.0.0.10
UM11434
IW416 Labtool User Guide
7.14 Command 99: Exit Labtool application
This command exits either the Wi-Fi or Bluetooth menu. Enter the command 99 a second
time to exit the Labtool application and close the command prompt window.
Syntax: 99
Return data: --
7.15 Command 113: Get power control class
This command gets the power control class in use.
Syntax: 113
Example(s)
114 0 // Sets the power control class to Class 2
Return data: Value for the power control class
• 0 = Class 2
• 1 = Class 1
Note: For Class 1 operation, IW416 max transmit power is 13 dBm at pin.
This command stops the Bluetooth LE Tx/Rx test. It is always used after the Bluetooth
LE Tx/Rx test (Section 7.19 "Command 125: Set Bluetooth LE Tx test" and Section 7.21
"Command 127: Set Bluetooth LE Rx test", respectively).
Syntax: 129
Return data:
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
7.23 Command 133: Set Bluetooth LE Tx power
This command sets the Bluetooth LE Tx power level value.
Syntax: 133 <pwr>
Where:
Command parameterDescription
pwrTx Power (dBm) - Default is 0.
Example(s)
133 6 // Sets Bluetooth LE power level as 6 dBm
Return data:
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
IntervalUser-defined test interval. The default is 1
WhiteningWhitening whole packet
ChannelAccessModeChannel access mode
Return data: xx or
UM11434
IW416 Labtool User Guide
1 = random hopping
0 = disable (default)
1 = enable
Specify if a channel hopped into a hop mode.
Default is 0x7FFFFFFFFFFFFFFFFFFF (all on)
Bit[78]: Ch 78
...
Bit[0]: Ch 0
0 = off
1 = on
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
7.25 Command 234: Reload Bluetooth calibration data
This command reloads the Bluetooth calibration data to make the modified Bluetooth
calibration data valid after the Bluetooth calibration data in “WlanCalData_ext.conf” is
modified.
Syntax: 234
Return data:
• Successful command: all-0 status byte (0x00000000)
• Failed command: non-0 status byte (0x00000001 to 0xFFFFFFFF)
Draft — A draft status on a document indicates that the content is still
under internal review and subject to formal approval, which may result
in modifications or additions. NXP Semiconductors does not give any
representations or warranties as to the accuracy or completeness of
information included in a draft version of a document and shall have no
liability for the consequences of use of such information.
10.2 Disclaimers
Limited warranty and liability — Information in this document is believed
to be accurate and reliable. However, NXP Semiconductors does not
give any representations or warranties, expressed or implied, as to the
accuracy or completeness of such information and shall have no liability
for the consequences of use of such information. NXP Semiconductors
takes no responsibility for the content in this document if provided by an
information source outside of NXP Semiconductors. In no event shall NXP
Semiconductors be liable for any indirect, incidental, punitive, special or
consequential damages (including - without limitation - lost profits, lost
savings, business interruption, costs related to the removal or replacement
of any products or rework charges) whether or not such damages are based
on tort (including negligence), warranty, breach of contract or any other
legal theory. Notwithstanding any damages that customer might incur for
any reason whatsoever, NXP Semiconductors’ aggregate and cumulative
liability towards customer for the products described herein shall be limited
in accordance with the Terms and conditions of commercial sale of NXP
Semiconductors.
Right to make changes — NXP Semiconductors reserves the right to
make changes to information published in this document, including without
limitation specifications and product descriptions, at any time and without
notice. This document supersedes and replaces all information supplied prior
to the publication hereof.
Suitability for use — NXP Semiconductors products are not designed,
authorized or warranted to be suitable for use in life support, life-critical or
safety-critical systems or equipment, nor in applications where failure or
malfunction of an NXP Semiconductors product can reasonably be expected
to result in personal injury, death or severe property or environmental
damage. NXP Semiconductors and its suppliers accept no liability for
inclusion and/or use of NXP Semiconductors products in such equipment or
applications and therefore such inclusion and/or use is at the customer’s own
risk.
Applications — Applications that are described herein for any of these
products are for illustrative purposes only. NXP Semiconductors makes
no representation or warranty that such applications will be suitable
for the specified use without further testing or modification. Customers
are responsible for the design and operation of their applications and
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
customer’s third party customer(s). Customers should provide appropriate
design and operating safeguards to minimize the risks associated with
their applications and products. NXP Semiconductors does not accept any
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
UM11434
IW416 Labtool User Guide
the application or use by customer’s third party customer(s). Customer is
responsible for doing all necessary testing for the customer’s applications
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
customer’s third party customer(s). NXP does not accept any liability in this
respect.
Export control — This document as well as the item(s) described herein
may be subject to export control regulations. Export might require a prior
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
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
entire risk as to the quality, or arising out of the use or performance, of this
product remains with customer. In no event shall NXP Semiconductors, its
affiliates or their suppliers be liable to customer for any special, indirect,
consequential, punitive or incidental damages (including without limitation
damages for loss of business, business interruption, loss of use, loss of
data or information, and the like) arising out the use of or inability to use
the product, whether or not based on tort (including negligence), strict
liability, breach of contract, breach of warranty or any other theory, even if
advised of the possibility of such damages. Notwithstanding any damages
that customer might incur for any reason whatsoever (including without
limitation, all damages referenced above and all direct or general damages),
the entire liability of NXP Semiconductors, its affiliates and their suppliers
and customer’s exclusive remedy for all of the foregoing shall be limited to
actual damages incurred by customer based on reasonable reliance up to
the greater of the amount actually paid by customer for the product or five
dollars (US$5.00). The foregoing limitations, exclusions and disclaimers shall
apply to the maximum extent permitted by applicable law, even if any remedy
fails of its essential purpose.
Translations — A non-English (translated) version of a document is for
reference only. The English version shall prevail in case of any discrepancy
between the translated and English versions.
Security — Customer understands that all NXP products may be subject
to unidentified or documented vulnerabilities. Customer is responsible
for the design and operation of its applications and products throughout
their lifecycles to reduce the effect of these vulnerabilities on customer’s
applications and products. Customer’s responsibility also extends to other
open and/or proprietary technologies supported by NXP products for use
in customer’s applications. NXP accepts no liability for any vulnerability.
Customer should regularly check security updates from NXP and follow up
appropriately. Customer shall select products with security features that best
meet rules, regulations, and standards of the intended application and make
the ultimate design decisions regarding its products and is solely responsible
for compliance with all legal, regulatory, and security related requirements
concerning its products, regardless of any information or support that may
be provided by NXP. NXP has a Product Security Incident Response Team
(PSIRT) (reachable at PSIRT@nxp.com) that manages the investigation,
reporting, and solution release to security vulnerabilities of NXP products.
10.3 Trademarks
Notice: All referenced brands, product names, service names and
trademarks are the property of their respective owners.
NXP — wordmark and logo are trademarks of NXP B.V.
9Acronyms and abbreviations ...........................63
10Legal information .............................................. 65
UM11434
IW416 Labtool User Guide
Please be aware that important notices concerning this document and the product(s)
described herein, have been included in section 'Legal information'.