Texas Instruments CC2650DK 사용자 설명서
RF Core HAL
An RX entry that is in the Active or Busy state may be read by the system CPU, but cannot be freed or
written to, except for data already committed by the radio CPU (in other words, finished). The system CPU
may read and modify the data in the RXData buffer up to nextIndex-1, while these bytes are not modified
by the radio CPU.
written to, except for data already committed by the radio CPU (in other words, finished). The system CPU
may read and modify the data in the RXData buffer up to nextIndex-1, while these bytes are not modified
by the radio CPU.
When the radio CPU changes the status of the entry from Pending to Busy, it initializes numElements and
nextIndex to 0.
nextIndex to 0.
Each entry element may start with a length indicator as specified by config.lenSz. If this value is 2 so that
a 16-bit length word is used, the length word may not be half-word aligned, and must be read byte by
byte.
a 16-bit length word is used, the length word may not be half-word aligned, and must be read byte by
byte.
Two (or more) RX queue entries may be set up in a ring buffer fashion. If so, pCurrEntry of the queue
must be initialized to one of the RX queue entries when setting up the radio operation command, and
pLastEntry must be NULL. pNextEntry of each RX queue entry must be set up to point to the other entry.
Whenever a packet is received, an RX interrupt is raised to the system CPU. The system CPU may then
read the corresponding entry element. If the status of the RX queue entry that the system CPU is reading
from has changed to Finished, the radio CPU writes its next entry element to the other entry, and after
finishing processing the received data in the first entry, the system CPU must reset the status field of that
entry to Pending. If this is not done prior to the radio CPU finishing with the other entry, the radio
operation assumes it is out of buffer space.
must be initialized to one of the RX queue entries when setting up the radio operation command, and
pLastEntry must be NULL. pNextEntry of each RX queue entry must be set up to point to the other entry.
Whenever a packet is received, an RX interrupt is raised to the system CPU. The system CPU may then
read the corresponding entry element. If the status of the RX queue entry that the system CPU is reading
from has changed to Finished, the radio CPU writes its next entry element to the other entry, and after
finishing processing the received data in the first entry, the system CPU must reset the status field of that
entry to Pending. If this is not done prior to the radio CPU finishing with the other entry, the radio
operation assumes it is out of buffer space.
23.3.2.8 External Signaling
The radio CPU controls the signals CPEGPO0 and CPEGPO1. For control of an external front-end,
CPEGPO0 is high when the LNA must be enabled and low otherwise. CPEGPO1 is high when the PA
must be enabled and low otherwise. The radio CPU also controls the signal CPEGPO2 to go high when
synth calibration starts, and low when the calibration is done. This control can be used for debugging. The
control of these signals may be disabled with the radio firmware configuration parameter gpoConto.
CPEGPO0 is high when the LNA must be enabled and low otherwise. CPEGPO1 is high when the PA
must be enabled and low otherwise. The radio CPU also controls the signal CPEGPO2 to go high when
synth calibration starts, and low when the calibration is done. This control can be used for debugging. The
control of these signals may be disabled with the radio firmware configuration parameter gpoConto.
Two of the output signals from the radio timer have automatic configuration that may be used for
observation. The signal RATGPO0 goes high when transmission of a packet is initiated and low when
transmission is done. This signal may be observed for accurate timing of packet transmission, as the
same signal is used internally. The signal is very similar to CPEGPO1, but it goes high some
microseconds earlier, and the timing is more accurate compared to the first transmitted symbol out of the
modem. However, CPEGPO1 is recommended for control of external PA to avoid turning it on too early.
The signal RATGPO1 may be configured to go high when sync is found in the receiver, and low when the
packet is received or reception aborted (this will not work for the IEEE 802.15.4 receiver command). This
signal is configured with the radio firmware configuration parameter gpoContol. The other radio timer
outputs may be configured to generate events as required, using CMD_SET_RAT_OUTPUT.
observation. The signal RATGPO0 goes high when transmission of a packet is initiated and low when
transmission is done. This signal may be observed for accurate timing of packet transmission, as the
same signal is used internally. The signal is very similar to CPEGPO1, but it goes high some
microseconds earlier, and the timing is more accurate compared to the first transmitted symbol out of the
modem. However, CPEGPO1 is recommended for control of external PA to avoid turning it on too early.
The signal RATGPO1 may be configured to go high when sync is found in the receiver, and low when the
packet is received or reception aborted (this will not work for the IEEE 802.15.4 receiver command). This
signal is configured with the radio firmware configuration parameter gpoContol. The other radio timer
outputs may be configured to generate events as required, using CMD_SET_RAT_OUTPUT.
By default, the radio CPU maps CPEGPO0 to the signal RFC_GPO0, CPEGPO1 to the signal
RFC_GPO1, CPEGPO2 to the signal RFC_GPO2, and RATGPO0 to the signal RFC_GPO3 at boot time.
This mapping can be modified by writing to RFC_DBELL:SYSGPOCTL.
RFC_GPO1, CPEGPO2 to the signal RFC_GPO2, and RATGPO0 to the signal RFC_GPO3 at boot time.
This mapping can be modified by writing to RFC_DBELL:SYSGPOCTL.
The RFC_GPO signals can be mapped to output pins using the system I/O controller.
23.3.3 Command Definitions
There is a set of commands independent of the current RF protocol. These commands are related to the
low-level operations of the radio.
low-level operations of the radio.
23.3.3.1 Protocol-Independent Radio Operation Commands
For radio operation commands listed here, the operation ends due to one of the causes listed in
, or by additional statuses listed for each command. After the operation has ended, the status
field of the command structure indicates the reason why the operation ended. In each case, it is indicated
if the result is True, False, or Abort (see
if the result is True, False, or Abort (see
, Conditional Execution). This result indicates
whether to start the next command (if any) indicated in pNextOp, or to return to an idle state.
1468
Radio
SWCU117A – February 2015 – Revised March 2015
Copyright © 2015, Texas Instruments Incorporated