For regulatory approval testing it is typically required to configure the radio for static receiver and transmitter operation at certain frequencies. To facilitate such testing, the TI Bluetooth Low Energy/Bluetooth Low Energy 5 protocol stack implements the following HCI vendor-specific test commands:

• HCI_EXT_ModemTestTxCmd
• HCI_EXT_ModemTestRxCmd

For a full overview of the applicable HCI extension commands, parameters and associated events, see the HCI Vendor Specific Guide included with the Bluetooth Low Energy protocol stack documentation in the SDK.

The above commands can be invoked in a few different ways:

• Through HCI extension commands over a UART interface using the HostTest project as described in the previous “Bluetooth RF-PHY testing” section. A tool such as BTool or HCITester can be used to enter test commands to the Bluetooth Low Energy-Stack.
• Through Production Test Mode as described in the previous “Bluetooth RF-PHY testing” section.
• Implementing a stand-alone test sequence or test mode in your embedded application which calls the appropriate HCI extension command APIs directly from the application code. This can be, for example, controlled by a timer or push button interface.

Additionally, the SmartRF Studio tool can be used to perform some of these tests. SmartRF™ Studio software does not rely upon any firmware on the device and instead directly controls the radio over a test interface (JTAG). However, for some regulatory testing purposes, the actual protocol stack firmware may be required.

Since regulatory testing requirements can vary from jurisdiction to jurisdiction, consult your test lab on specific test requirements based on where your product is sold.