Texas Instruments SimpleLink CC2620 Technical Reference Manual page 1483

www.ti.com
Relative timing can either be relative to the time of submitting the command chain, to the start of the
command, to the start of the previous or first command, or to certain observed events inside the
command, to be defined for each command. The following rules apply:
• For the first command in a chain, if the start trigger is any of the types 5 through 9, the start is
immediate. If another trigger referenced in the first command in a chain is any of the types 5 through 9,
the trigger time is relative to the time the command was submitted.
• If the start trigger of a command is TRIG_REL_START, an error is produced.
• If the start trigger of a command is TRIG_NEVER and bEnaCmd is 0, an error is produced.
• Some radio operation commands define events 1 and 2. These are context-dependent events that can
be observed by the radio CPU. See the description of each command for a definition in that context. If
undefined, these events are the time of the start of the command.
If bEnaCmd is 1, the action may also be triggered with a command (CMD_TRIGGER command, see
Section 23.3.4.5). The triggerNo parameter identifies the trigger number of this command.
If a trigger occurs in the past when evaluated, the behavior depends on the pastTrig bit. If this bit is 0, the
trigger does not occur, or for start triggers, an error is produced. If this bit is 1, the trigger occurs as soon
as possible. If the pastTrig bit is 1 for start triggers, timing relative to the start of the command is relative to
the programmed start time, not the actual start time.
For an external trigger, the radio CPU sets the RAT to use the selected input event as a one-capture
trigger; the CPU then uses this capture interrupt to trigger the action. If the event occurs before the setup
occurs, the event is not captured, and the pastTrig bit is ignored.
23.3.2.5.2 Conditional Execution
The execution of a command may be conditional on the result of the previous command. For each
command, three results are possible:
• TRUE
• FALSE
• ABORT
The criteria are defined for each command. If not defined, the result is TRUE unless the command ended
with an error, in which case the result is ABORT.
Each command structure contains a condition for running the next command. The condition byte is as
given in Table 23-6. If the rule is COND_SKIP_ON_FALSE or COND_SKIP_ON_TRUE, the number of
commands to skip is signaled in the nSkip field. If the number of skips is zero, rerun the same command.
If the number of skips is one, run the next command in the chain. If the number of skips is two, run the
command after the next, and so forth. If the rule is COND_NEVER and no previous commands use
skipping, the next command pointer is ignored and may be NULL.
Bit Index Field Name
0–3 rule
4–7 nSkip
SWCU117C – February 2015 – Revised September 2015
Submit Documentation Feedback
Table 23-6. Format of Condition Byte
Description
Rule for how to proceed, as defined in
Number of skips if skipping is an option
Copyright © 2015, Texas Instruments Incorporated
RF Core HAL
Table 23-7
1483
Radio