|Structure that represents one of the channels that is part of a RAIL_BLE_TxChannelHoppingConfig_t sequence of channels used in channel hopping. |
|Wrapper struct that will contain the sequence of RAIL_BLE_TxChannelHoppingConfigEntry_t that represents the channel sequence to use during TX Channel Hopping. |
|A configuration structure for repeated transmits. |
|RAIL_Status_t||RAIL_BLE_SetNextTxRepeat (RAIL_Handle_t railHandle, const RAIL_BLE_TxRepeatConfig_t *repeatConfig)|
|Set up automatic repeated transmits after the next transmit. |
|const RAIL_BLE_TxRepeatConfig_t *||
Set up automatic repeated transmits after the next transmit.
A RAIL instance handle. [in]
The configuration structure for repeated transmits.
- Status code indicating a success of the function call.
Repeated transmits will occur after an application-initiated transmit caused by calling one of the Packet Transmit APIs. The repetition will only occur after the first application-initiated transmit after this function is called. Future repeated transmits must be requested by calling this function again.
If a TX error occurs during the repetition, the process will abort and the TX error transition from RAIL_SetTxTransitions will be used. If the repetition completes successfully, then the TX success transition from RAIL_SetTxTransitions will be used.
Any call to RAIL_Idle or RAIL_StopTx will clear the pending repeated transmits. The state will also be cleared by another call to this function. To clear the repeated transmits before they've started without stopping other radio actions, call this function with a RAIL_BLE_TxRepeatConfig_t::iterations count of 0. A DMP switch will clear this state only if the initial transmit triggering the repeated transmits has started.
The application is responsible for populating the transmit data to be used by the repeated transmits via RAIL_SetTxFifo or RAIL_WriteTxFifo. Data will be transmitted from the TX FIFO. If the TX FIFO does not have sufficient data to transmit, a TX error will be caused and a RAIL_EVENT_TX_UNDERFLOW will occur. In order to avoid an underflow, the application should queue data to be transmitted as early as possible.
This function will fail to configure the repetition if a transmit of any kind is ongoing, including during the time between an initial transmit and the end of a previously-configured repetition.