Texas Instruments SimpleLink CC2620 Technical Reference Manual page 1572

Bluetooth Low Energy
connection event are any whole multiple of connection intervals from pParams->connectTime, which may
be in the past or the future from the start of the initiator command. The radio CPU inserts a WinOffset
parameter in the transmitted CONNECT_REQ, such that the first connection event is signaled to be at the
first connection event that comes sufficiently long enough after the end of the CONNECT_REQ packet to
be transmitted. The radio CPU is set up the transmit window (WinOffset and WinSize) so that there is
margin both between the start of the transmit window and the start of the first master packet, and between
the start of the first master packet and the end of the transmit window. The inserted WinSize is either 1 or
2; ensuring such a margin. The radio CPU writes the calculated values for WinSize and WinOffset into the
corresponding locations in the pParams->pConnectData buffer. The start time of the first connection event
used to transmit the first packet within the signaled transmit window is written back by the radio CPU in
pParams->connectTime. If no connection is made, the radio CPU adds a multiple of connection intervals
to pParams->connectTime, so that it is the first possible time of a connection event after the operation
ended.
The output structure pOutput contains fields which give information on the command being run. The radio
CPU does not initialize the fields, so this must be done by the system CPU when a reset of the counters is
desired. The fields are updated by the radio CPU as described below. The list also indicates when
interrupts are raised in the system CPU.
• If a CONNECT_REQ packet has been transmitted, nTXConnectReq is incremented and a TX_DONE
interrupt is raised.
• If an ADV*_IND packet is received with CRC OK and the bIgnore flag cleared, nRXAdvOk is
incremented, an RX_OK interrupt is raised, and timeStamp is set to a timestamp of the start of the
packet.
• If an ADV*_IND packet is received with CRC OK and the bIgnore flag set, nRXAdvIgnored is
incremented and an RX_IGNORED interrupt is raised.
• If an ADV*_IND packet is received with CRC error, nRXAdvNok is incremented and an RX_NOK
interrupt is raised.
• If an ADV*_IND packet is received and did not fit in the RX queue, nRXAdvBufFull is incremented and
an RX_BUF_FULL interrupt is raised.
• If a packet is received, lastRssi is set to the RSSI of that packet
• If the first RX data entry in the RX queue changed state to Finished after a packet was received, an
RX_ENTRY_DONE interrupt is raised.
An initiator operation ends with one of the statuses listed in
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.
Condition
Performed Action Number2 (transmitted CONNECT_REQ)
Observed trigger indicated by pParams->timeoutTrigger while waiting for
sync on ADV*_IND
Observed trigger indicated by pParams->timeoutTrigger, then performed
Action Number1, 2, 3, 4, or 5.
Observed trigger indicated by pParams->endTrigger while waiting for sync
on ADV*_IND
Observed trigger indicated by pParams->endTrigger, then performed Action
Number1, 2, 3, or 4
Observed CMD_STOP while waiting for sync on ADV*_IND
Observed CMD_STOP, then performed Action Number1, 2, 3, or 4
Received CMD_ABORT
No space in RX buffer to store received packet
Illegal value of channel
LLData length field has illegal value
1572
Radio
Table 23-129. End of Initiator Operation
Copyright © 2015, Texas Instruments Incorporated
Table 23-129. The status field of the
Status Code
BLE_DONE_CONNECT
BLE_DONE_RXTIMEOUT
BLE_DONE_RXTIMEOUT
BLE_DONE_ENDED
BLE_DONE_ENDED
BLE_DONE_STOPPED
BLE_DONE_STOPPED
BLE_DONE_ABORT
BLE_ERROR_RXBUF
BLE_ERROR_PAR
BLE_ERROR_PAR
SWCU117C – February 2015 – Revised September 2015
Submit Documentation Feedback
www.ti.com
Result
FALSE
TRUE
TRUE
FALSE
FALSE
FALSE
FALSE
ABORT
FALSE
ABORT
ABORT