User manual

www.ti.com Bluetooth Low Energy
Table 23-120. Actions on Received Packets by Scanner (continued)
AdvA
Filter AdvA to be Active Action
PDU Type CRC Result Present in InitA Match
Policy Ignored Scan Number
White List
ADV_SCAN_IND OK 0 No X N/A Yes 3
ADV_SCAN_IND OK X Yes X N/A X 1
ADV_SCAN_IND NOK X X X N/A X 4
ADV_NONCONN_IND OK 1 No No N/A X 1
ADV_NONCONN_IND OK 1 No Yes N/A X 2
ADV_NONCONN_IND OK 0 No X N/A X 2
ADV_NONCONN_IND OK X Yes X N/A X 1
ADV_NONCONN_IND NOK X X X N/A X 4
ADV_DIRECT_IND OK 1 No No X X 1
ADV_DIRECT_IND OK 1 No Yes No X 1
ADV_DIRECT_IND OK 1 No Yes Yes X 2
ADV_DIRECT_IND OK 0 No X No X 1
ADV_DIRECT_IND OK 0 No X Yes X 2
ADV_DIRECT_IND OK X Yes X X X 1
ADV_DIRECT_IND NOK X X X X X 4
ADV*_IND with invalid length X X X X X X 5
Other X X N/A N/A N/A X 5
Table 23-121. Descriptions of the Actions to Take on Packets Received by Scanner
Action Number bCrcErr bIgnore Description
1 0 1 Continue scanning.
Continue scanning or end operation with BLE_DONE_OK
2 0 0
status.
Perform backoff procedure and send SCAN_REQ and receive
3 0 0 SCAN_RSP if applicable. Then continue scanning or end
operation.
4 1 0 Continue scanning.
5 – – Stop receiving packet, then continue scanning.
If the packet being received did not fit in the RX queue, the packet is received to the end, but the received
bytes are not stored. If the packet would normally not have been discarded from the RX buffer, the
operation ends.
If the action from the received packet is #3, a SCAN_REQ is transmitted if allowed after a backoff
procedure. This procedure starts with decrementing pParams ->backoffCount. If this variable is 0 after the
decrement, a SCAN_REQ is transmitted. If not, the operation ends. If the action from the received packet
is #2 or #3, the next action may either be to continue scanning, or to end the operation. This is configured
with pParams ->scanConfig.bEndOnRpt; if 1, the operation ends, otherwise scanning continues.
When transmitting a SCAN_REQ, the radio CPU constructs this packet. In the header, the PDU Type bits
are 0011b. The TXAdd bit is as shown in pParams ->scanConfig.deviceAddrType. The RXAdd bit is as
shown in the TXAdd field of the header of the received ADV_IND or ADV_SCAN_IND message. The
length is calculated from the size of the scan request data, pParams->scanReqLen + 12. The RFU bits are
0. The payload starts with the 6-byte device address, which are read from pParams ->pDeviceAddress,
followed by the 6-byte peer address read from the AdvA field of the received message. By the BLE
specification, there is no more payload, but a non-compliant message may be constructed by setting
pParams->scanReqLen to a nonzero value. If so, the rest of the payload is read from the pParams-
>pScanData buffer.
1537
SWCU117A–February 2015–Revised March 2015 Radio
Submit Documentation Feedback
Copyright © 2015, Texas Instruments Incorporated