User manual

www.ti.com IEEE 802.15.4
23.5.2 Interrupts
The interrupts to be used by the IEEE 802.15.4 commands are listed in Table 23-75. Each interrupt may
be enabled individually in the system CPU. Details for when the interrupts are generated are given in
Section 23.5.4, Radio Operation Commands.
Table 23-75. Interrupt Definitions Applicable to IEEE 802.15.4
Interrupt Number Interrupt Name Description
A background level radio operation command has
0 COMMAND_DONE
finished.
The last background level radio operation command
1 LAST_COMMAND_DONE
in a chain of commands has finished.
2 FG_COMMAND_DONE A foreground radio operation command has finished
The last foreground radio operation command in a
3 LAST_FG_COMMAND_DONE
chain of commands has finished
4 TX_DONE Transmitted frame
5 TX_ACK Transmitted automatic ACK frame
16 RX_OK Frame received with CRC OK
17 RX_NOK Frame received with CRC error
18 RX_IGNORED Frame received with ignore flag set
22 RX_BUF_FULL Frame received that did not fit in the TX queue
23 RX_ENTRY_DONE TX queue data entry changing state to Finished
As part of the boot process, the CM0 has opened
29 MODULES_UNLOCKED
access to RF core modules and memories
30 BOOT_DONE The RF core CPU boot is finished
31 INTERNAL_ERROR The radio CPU has observed an unexpected error
23.5.3 Data Handling
For all the IEEE 802.15.4 commands, data received over the air is stored in a receive queue.
Data to be transmitted is fetched from a buffer given in the transmit command.
23.5.3.1 Receive Buffers
A frame being received is stored in the receive buffer. First, a length byte or word is stored, if configured in
the RX entry, by config.lenSz, and calculated from the length received over the air and the configuration of
appended status information.
The format of the entry elements in the receive queue pointed to by pRXQ is given by the configuration
RXConfig defined in Section 23.6.1.4.
Following the length field, the received PHY header byte is stored if RXConfig.bIncludePhyHdr is 1. If a
length field is present, this byte is redundant except for the reserved bit. The received MAC header and
MAC payload is stored as received over the air. The MAC footer containing the 16-bit frame check
sequence is stored if RXConfig.bIncludeCrc is 1.
If RXConfig.bAppendRssi is 1, a byte indicating the received RSSI value is appended. If
RXConfig.bAppendCorrCrc is 1, a status byte of the type defined in Table 23-74, is appended. If
RXConfig.bAppendSrcInd is 1, a byte giving the index of the first source matching entry that matches the
header of the received packet is appended, or 0xFF if no match. If RXConfig.bAppendTimeStamp is 1, a
timestamp indicating the start of the frame is appended. This timestamp is a four-byte number from the
radio timer. Though the timestamp is multi-byte, no word-address alignment shall be made, so the
timestamp must be written and read byte-wise. The timestamp is captured when SFD is found, but
adjusted to reflect the start of the frame (assuming 8 preamble bytes as per the standard), defined so that
it corresponds to the time of the start trigger used on the transmit side. The adjustment is defined in the
syncTimeAdjust firmware-defined parameter, and may be overridden.
The format of an entry element in the RX queues is shown in Figure 23-6.
1501
SWCU117A–February 2015–Revised March 2015 Radio
Submit Documentation Feedback
Copyright © 2015, Texas Instruments Incorporated