DUT
Overview
It is introduced how to start a Bluetooth DUT test, including BLE non-signaling test and BT signaling and non-signaling test.
Introduction
BLE non-signaling test
- test environment
Connect the rf port of the test board to the rf port of the test equipment (such as CMW270), and connect the serial cable on the test board to the test equipment.
- Enter ATE mode
First connect the ATE jumper cap of the serial port cable, and then power on to enter the ATE mode
- open test path
Send
ble dut
command to serial port
- start test
Perform BLE non-signaling test according to the test equipment instructions
BT signaling test
- test environment
Connect the rf port of the test board to the rf port of the test equipment (such as CMW270), and connect the serial cable on the test board to the test equipment.
- Enter ATE mode
First connect the ATE jumper cap of the serial port cable, and then power on to enter the ATE mode
- open test path
Send
ble dut
command to serial port
- start test
Perform BT signaling test according to the test equipment instructions
BT non-signaling test
- test environment
Connect the rf port of the test board to the rf port of the test equipment (such as CMW270), and connect the serial cable on the test board to the test equipment.
- Enter ATE mode
First connect the ATE jumper cap of the serial port cable, and then power on to enter the ATE mode
- open test path
Send
ble dut
command to serial port
- start test
The test equipment is in RX mode, send TX command through the serial port to perform the TX test, and send the end command to stop the TX testThe test equipment is in TX mode, send RX command through the serial port to perform the RX test, and send the end command to stop the RX test
- [TX/RX command format]
01 E0 FC 0C FD UAP LAP2 LAP1 LAP0 Test_Scenarios Hop_mode TX_chnl RX_chnl Interval Packet_Type Tx_Power
01 E0 FC 0C FD
fixed command header
UAP LAP2 LAP1 LAP
Test equipment address, valid is in rx mode
Test_Scenarios
- test mode
01 : Repeated ‘00000000’ (in transmission order) sequence02 : Repeated ‘11111111’ (in transmission order) sequence03 : Repeated ‘10101010’ (in transmission order) sequence04 : PN9 sequence (in transmission order)07 : rx test09 : Repeated ‘11110000’ (in transmission order) sequenceHop_mode
- hop
00 : off01 : onTX_chnl
- tx channel
0-78,corresponding frequency 2402-2480RX_chnl
- rx channel
0-78,corresponding frequency 2402-2480Interval
currently unused
Packet_Type
- package type
0 : NULLpkt1 : POLLpkt2 : FHSpkt3 : DM14 : DH15 : HV16 : HV27 : HV38 : DV9 : AUX110 : DM311 : DH312 : EV413 : EV514 : DM515 : DH516 : IDpkt20 : EDR_2DH121 : EV322 : EDR_2EV323 : EDR_3EV324 : EDR_3DH125 : EDR_AUX126 : EDR_2DH327 : EDR_3DH328 : EDR_2EV529 : EDR_3EV530 : EDR_2DH531 : EDR_3DH5Tx_Power
currently inactive
- [end command format]
01 E0 FC 01 90
After sending this command, the serial port will receive an end resp- [end resp format]
04 0E 18 01 E0 FC 90 TxTotolPackets RxTotolPackets RxValidPackets RxHECErrorCntr RxCRCErrorCntr
04 0E 18 01 E0 FC 90
response fixed header
TxTotolPackets
- The total number of packets sent, valid in tx mode
This parameter is 4 bytes, displayed in little endianRxTotolPackets
- The total number of packets received, valid in rx mode
This parameter is 4 bytes, displayed in little endianRxValidPackets
- The total number of packets correctly received, valid in rx mode
This parameter is 4 bytes, displayed in little endianRxHECErrorCntr
- The number of HEC error packets received, valid in rx mode
This parameter is 4 bytes, displayed in little endianRxCRCErrorCntr
- The number of CRC error packets received, valid in rx mode
This parameter is 4 bytes, displayed in little endianNote: All command parameters are in hexadecimal format
- [Test Case]
tx :01 e0 fc 0c fd 12 34 56 12 09 00 00 00 01 04 7f
rx :01 e0 fc 0c fd 9c bd 35 9c 07 00 00 00 01 04 7f
end tx/rx :01 E0 FC 01 90
Received end resp :04 0E 18 01 E0 FC 90 DD 13 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00