ble test - Low-level BLE Tests

Perform Low-level BLE tests.

Usage:

- command: ble test recv <channel>
  [retry: <retryCount>]

- command: ble test xmit <channel> [<length> [<payload>]]
  [retry: <retryCount>]

- command: ble test stop
  [extractKey: <key>]
  [retry: <retryCount>]

Argument	Description
channel	BLE link-layer test channel (0…39). Maps to RF channel frequency as `2402 MHz + 2*channel` (channel 0 = 2402 MHz, channel 39 = 2480 MHz).
length	Length in bytes of payload data in each packet (0…255; default: 0 if omitted).
payload	Test packet payload type (0…255; default: 0 if omitted). Defined values: 0: PRBS9, 1: 0xF0, 2: 0xAA, 3: PRBS15, 4: 0xFF, 5: 0x00, 6: 0x0F, 7: 0x55.
key	Key in which to store the `ble test stop` result: the number of packets received since the test started (only meaningful after `ble test recv` was running).
retryCount	Number of times to retry the test step (optional)

ble test xmit and ble test recv start a continuous LE transmitter or receiver test on the adapter’s radio; they do not by themselves stop or time out. Use ble test stop to end the active test — for recv, this also returns the number of packets received.

Examples

BLE Interaction

Note

Using the ble test commands on a PLT-300A requires a supported BLE test dongle.

Note

ble test drives the BLE radio directly (HCI-level LE transmitter/receiver test) to validate RF performance — it does not connect to the DUT’s GATT server. Use ble gatt for functional tests of the DUT’s BLE application, and bledis to confirm the DUT is advertising and discoverable.