Preliminary Technical Data UG-1828
Rev. PrC | Page 217 of 338
to be 3 for the set of LTE profiles, then LTE 61.44MSPS, 30.72MSPS and 15.36MSPS profiles are enabled for DPS. Each profile has a
profile index associated with it. Index 0 denotes the profile with the lowest bandwidth and sampling rate and Index 5 denotes the profile
with the highest bandwidth and sampling rate. During initialization, user could enable Rx PFIR for each profile by using either the default
PFIR coefficients or providing a set of custom PFIR coefficients.
ADRV9001 is first calibrated with the main profile similarly as in the regular operation mode without DPS. Then it is further calibrated
for all the dynamic profiles using the API function adi_adrv9001_cals_Dynamic_profiles_calibrate(). When calibration is completed, the
main profile is set as the initial profile to operate. Note the SSI rate is configured based on the main profile and it does not change during
the entire profile switching operation.
Figure 203 described the initial calibration procedure when DPS is enabled.
Load Main Profile
Run Initial
Calibration
More Dynamic Profile
to Calibrate?
Initialization
Done
Load Next Profile
N
Y
Figure 203: Initial Calibration with DPS
PERFORM DPS ON THE FLY
As mentioned earlier, after initialization, ADRV9001 operates on the main profile with the fixed SSI rate which does not change during
the entire profile switching operation. To prepare for operating with the next profile, BBIC should properly configure the ratio between
the interface rate and the new sampling rate before requesting profile switching. It should also notify ADRV9001 about the next profile by
calling the API command adi_adrv9001_arm_NextDynamicProfile_Set(). Furthermore, as an option, BBIC could also set the Rx and Tx
PFIR coefficients associated with the next profile on the fly by calling the API command adi_adrv9001_arm_NextPfir_Set(). Note these 2
APIs could be called in different channel states including “Standby”, “Calibrated”, “Primed” and “RF_enabled”. When BBIC is ready to
perform profile switching, it should first move all Tx and Rx channels from “RF_enabled” state to “Primed” state and call the API
command adi_adrv9001_arm_Profile_Switch () to request ADRV9001 to switch to the new profile. Once receiving this command from
BBIC, ADRV9001 starts to perform switching by applying the new profile and PFIR coefficients BBIC set earlier and it will not respond to
any signals on Tx_enable and Rx_enable pins. ADRV9001 takes about 50us to complete the switch. After that, BBIC can move the
channels from “Primed” state back to “RF_enabled” state and continue the transmit and receive operations with the new profile.
Figure 204 shows the procedure of performing DPS and the communication between BBIC and ADRV9001.
To Next Page
Loading...
Need help?
General
