Texas Instruments SimpleLink CC2620 Technical Reference Manual page 1566

Bluetooth Low Energy
23.6.4.4.4 Scannable Undirected-Advertiser Command
A scannable undirected-advertiser operation is started by a CMD_BLE_ADV_SCAN command. In the
command structure, it has a pParams parameter of the type defined in
parameter of the type defined in
operates as described in
A scannable undirected-advertiser operation ends with one of the statuses listed in
status field of the command structure after the operation is ended indicates the reason why the operation
ended. In all cases, a COMMAND_DONE interrupt is raised. In each case, it is indicated if the result is
TRUE, FALSE, or ABORT, which decides the next action.
Table 23-121. End of Scannable Undirected-Advertiser Operation
Condition
Performed Action Number1 after running receiver
Performed Action Number2 and transmitted SCAN_RSP
Performed Action Number3 after running receiver
Performed Action Number5 after running receiver
Observed trigger indicated by pParams->endTrigger, then performed
Action Number1, 2, 3, or 5
Observed CMD_STOP, then performed Action Number1, 2, 3, or 5
Received CMD_ABORT
No space in RX buffer to store received packet
Illegal value of channel
Advertising data or scan response data length field has illegal value
23.6.4.5 Scanner Command
A scanner operation is started by a CMD_BLE_SCANNER command. In the command structure, it has a
pParams parameter of the type defined in
Table 23-100. At the start of a scanner operation, the radio CPU waits for the start trigger, then programs
the frequency based on the channel parameter of the command structure. The channel parameter is not
allowed to be in the range 0–36, as these are data channels. The radio CPU sets up the advertising
channel access address and uses the CRC initialization value 0x55 5555. The whitener is set up as
defined in the whitening parameter. The radio CPU then configures the receiver.
Tuned to the correct channel, the radio CPU starts listening for an advertising-channel packet. If sync is
obtained on the demodulator, the message is received into the RX queue. The header is checked, and if it
is not an advertising packet, reception stops and sync search restarted. The bCrcErr and bIgnore bits are
set according to the CRC result and the received message. Depending on the scanning filter policy, given
by pParams->scanConfig.scanFilterPolicy, the received AdvA field in the message, along with the TXAdd
bit of the received header is checked against white list as described in
ADV_DIRECT_IND messages, the received InitA field and RXAdd bit are checked against pParams-
>deviceAddr and pParams->scanConfig.deviceAddrType, respectively. Depending on this, and whether
the scan is active or passive as signaled in pParams->scanConfig.bActiveScan, the actions taken are as
shown in Table 23-122, where the definition of each action, including the value used on bCrcErr and
bIgnore, is given in
compliant with the BLE specification are considered valid. For an ADV_DIRECT_IND, valid means a
length field of 12, and for other ADV*_IND messages it means a length field in the range 6–37. If
pParams->advConfig.bStrictLenFilter is 0, all received packets with a length field less than or equal to the
maximum length of an advertiser packet (37, but can be overridden) are considered valid. If the length is
not valid, the receiver stops.
1566 Radio
Table 23-99. The operation starts with transmission operation and
Section 23.6.4.4.
Table
Table 23-123. If pParams->scanConfig.bStrictLenFilter is 1, only length fields
Copyright © 2015, Texas Instruments Incorporated
Table
Status Code
BLE_DONE_OK
BLE_DONE_OK
BLE_DONE_RXERR
BLE_DONE_NOSYNC
BLE_DONE_ENDED
BLE_DONE_STOPPED
BLE_DONE_ABORT
BLE_ERROR_RXBUF
BLE_ERROR_PAR
BLE_ERROR_PAR
23-94, and a pOutput parameter of the type defined in
Section
SWCU117C – February 2015 – Revised September 2015
www.ti.com
23-93, and a pOutput
Table 23-121. The
Result
TRUE
TRUE
TRUE
TRUE
FALSE
FALSE
ABORT
FALSE
ABORT
ABORT
23.6.4.9. For
Submit Documentation Feedback