I would like to start this discussion to talk about FCC/ETSI certification software we use to provide for connectivity customer boards. FCC/ETSI are mandatory certifications we need to pass in order to be able to ship our boards worldwide and it basically regulates that there is no violation to the way our devices are using the frequency spectrum space. Talking specifically about the 2.4GHz products, we have IEEE 802.15.4 and BLE radios that need to pass this certification. Basic functionality is required by the test houses to run this certification, they basically set the radio in Tx/Rx mode in the lowest, middle and highest channels (i.e. for IEEE 802.15.4, typical channels for this certification are 11, 17/18 and 26).
When talking about the IEEE 802.15.4 only supported radio, we used to provide our SMAC connectivity test, which allows the customer/test houses to set the radio in Tx/Rx in any IEEE 802.15.4 desired channel at any power output, power output used to be at 0dBm. Then, the test house run all the required test to validate the HW does not violate any regulations in terms of the frequency spectrum use.
When talking about the BLE supported radio, we used to provide the BLE HCI Application which basically allows the tester to set the radio in Tx/Rx mode by using HCI transmitter/receiver test commands. These commands are part of the BLE specifications at the HCI level.
Hence, whenever a new board is produced, besides the normal validation/test software required to validate all peripheral and GPIOs are functional in the board, we need to send SMAC Connectivity Test and the BLE HCI App depending on the supported application, for the multi-protocol radio we sent both applications. This way, the manufacturer can proceed with FCC/ETSI certification.
In order to know how to play with the Connectivity Test application. You can refer to the "SMACDAUG" document included in the connectivity software package of your desired device.
For the BLE HCI App. A document is available in the community in the next link:
This document describes the command that need to be sent to the HCI App to configure the radio in Tx/Rx mode in the desired channel.
Finally, it is very important that the board contains proper XTAL trimming value, so, we can have optimum RF performance.
To know more abou XTAL trimming on KW devices. Please, see the next links:
New "Receiver Blocking" tests have been added to the ETSI EN 300 328 V2.1.1 ( see sections 126.96.36.199 and 5.4.11). Here is the definition of these tests : " Receiver blocking is a measure of the ability of the equipment to receive a wanted signal on its operating channel without exceeding a given degradation in the presence of an unwanted signal (blocking signal) at frequencies other than those of the operating band3". The tests are based on the Packet Error Rate (PER) measurements. Please let me know if you need more information.
In order to do this test, which binary we have to load to KW41Z (hci_app.bin?). We are just wondering how we can do this test in the lab? If you can provide some hints, it world be useful (in the context of kw41z).
If you are interested on BLE. There are two options to perform this:
1. Using HCI application (aka as hci_blackbox or hci_app). For this, you need to have a Bluetooth tester (i.e. R&S CBT) to be able to run PER test using this test. You can refer to http://www.nxp.com/assets/documents/data/en/application-notes/AN5179.pdf to learn how to make PER using CBT tool and HCI app.
2. You can use the "GFSK Connectivity Test" application included in the KW41Z connectivity software. Please, refer to the
"Generic FSK Link Layer Quick Start Guide" document included in the KW41Z Connectivity Software.
If you are interested on IEEE 802.15.4. You can use the "SMAC Connectivity Test" included in the KW41Z Connectivity Software. Please, refer to the "Kinetis SMAC Demo Applications User's Guide" included in the KW41Z Connectivity Software.
Connectivity Test application includes a PER test demo that can be used for this purpose.