User manual

www.ti.com Bluetooth Low Energy
A master operation ends due to one of the causes listed in Table 23-112. The 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-112. End of Master Operation
Condition Status Code Result
Successfully received packet with MD=0 after having transmitted
BLE_DONE_OK True
packet with MD=0
Received packet which did not fit in RX queue after having transmitted
BLE_DONE_OK True
packet with MD=0
Received a packet after nPkt had counted to 0. BLE_DONE_OK True
No sync obtained on receive operation after transmit BLE_DONE_NOSYNC True
Two subsequent packets in the same operation were received with
BLE_DONE_RXERR True
CRC error
The internal counter nNack counted down to 0 after a packet was
BLE_DONE_MAXNACK True
received
Received a packet after having observed trigger indicated by pParams
BLE_DONE_ENDED False
>endTrigger
Received a packet after having observed CMD_STOP BLE_DONE_STOPPED False
Received CMD_ABORT BLE_DONE_ABORT Abort
Illegal value of channel BLE_ERROR_PAR Abort
TX data entry length field has illegal value BLE_ERROR_PAR Abort
23.6.4.4 Advertiser
At the start of an advertiser operation of any kind, 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 transmitter. Except for an
advertiser that is not connectable, the operation goes on with reception after transmission, and if a
SCAN_REQ is received, another transmission of a SCAN_RSP may occur.
In BLE, advertising is usually done over all three advertising channels. To set this up, three command
structures can be chained using the pNextOp parameter. Typically, the parameter and output structures
can be the same for all channels.
The first packet transmitted is always an ADV*_IND packet. This packet consists of a header, an
advertiser address, and advertising data, except for the ADV_DIRECT_IND packet used in directed
advertising. The radio CPU constructs these packets as follows (the ADV_DIRECT_IND packet is
described in Section 23.6.4.4.2, Connectable Directed Advertiser Command). In the header, the PDU
Type bits are as shown in Table 23-113. The TXAdd bit is as shown in pParams-
>advConfig.deviceAddrType. The length is calculated from the size of the advertising data, meaning that it
is pParams->advLen + 6. The RXAdd bit is not used and is 0, along with the RFU bits. The payload starts
with the 6-byte device address, which are read from pParams->pDeviceAddress. The rest of the payload
is read from the pParams->pAdvData buffer (if pParams->advLen is nonzero).
1531
SWCU117A–February 2015–Revised March 2015 Radio
Submit Documentation Feedback
Copyright © 2015, Texas Instruments Incorporated