SWRA601L April 2019 – October 2024 CC1350 , CC1352P , CC1352P7 , CC1352R , CC2340R5 , CC2540 , CC2540T , CC2541 , CC2541-Q1 , CC2640 , CC2640R2F , CC2640R2F-Q1 , CC2642R , CC2642R-Q1 , CC2650 , CC2650MODA , CC2652P , CC2652R , CC2652R7 , CC2652RB , CC2652RSIP
Bluetooth RF-PHY testing is performed by placing and controlling the device under test (DUT) in Direct Test Mode (DTM). Through DTM, an external Bluetooth RF test instrument can issue standardized HCI test commands to the DUT over a 2-wire universal asynchronous receiver/transmitter (UART) interface in order to execute required receiver and transmitter tests. An overview of the DTM interface is provided in the Bluetooth specification, Volume 6, Part F. DTM is only intended for lab test purposes. When DTM is activated, normal Bluetooth Low Energy protocol communication is not permitted.
Note that if your product does not normally provide a UART interface for performing DTM RF-PHY testing, it is usually acceptable to modify your product to expose these pins provided the modification does not interfere with or alter RF/antenna performance.
The TI Bluetooth Low Energy protocol stack supports the DTM interface and required HCI test commands natively as part of the HostTest network processor project that is supplied within the respective SDK. For standalone embedded projects (for example, simple_peripheral) that do not normally expose a UART/HCI interface, a special Production Test Mode (PTM) can be added to the application in order to expose the required DTM interfaces. With PTM, the required IO pins are reserved for the UART HCI interface; however, the DTM interface is only activated by the application in response to a software API function call. For details on how to add PTM to your application, see the documentation in the corresponding SDK.
Since the Bluetooth receiver and transmitter radio performance is a function of the Bluetooth Low Energy protocol stack and radio configuration, it is possible to use the HostTest network processor project for RF-PHY testing of end products that utilize a standalone/embedded project. The use of HostTest for RF-PHY testing purposes is acceptable provided that both your protocol stack and radio configuration are identical to the corresponding standalone/embedded project used by your end product.