SWCU193 April 2023 CC2340R2 , CC2340R5 , CC2340R5-Q1
The RCL automates the low-level operation of the radio for the user, but a description of the usage model is included here for reference. The behavior of the radio is to a large degree firmware defined. The description in this section describes the typical usage model, but other usage models are possible. Before any radio operation can be attempted the radio needs to be configured, this includes:
The configuration is considered static, and does not need to change when changing RF frequency, switching between TX and RX, etc. The configurations for different PHYs can be exported from SmartRF™ Studio, a Windows application that helps in generation of the RF configuration register values and commands, as well as practical testing and debugging of the RF system. A set of predefined configurations for PHYs that are documented in the data sheet are available, and these configurations can be modified in SmartRF Studio to fit the use case. The PHY cannot be changed at run time.
After the radio has been configured, the RCL sends an API command to the PBE. Any parameters that change depending on frequency, role, and packet contents are passed as command parameters. These parameters are setup in the BUFRAM and various HW registers, the FIFO is populated if needed, and then the API command ID is passed to the PBE. The BUFRAM parameters are documented as part of the SDK, as the parameters are fully firmware defined.
The PBE then uses the command ID and the command parameters and does further sequencing with the MDM and RFE. As the command executes, the radio generates data, events and interrupts that can be used by the rest of the system. Once the command finishes execution, the MCE and RFE report that they are done to the PBE, and then the PBE signals to the system side that the command is completed.