ROOT CAUSE : Error code to convey that the external path delay calibration was not run prior to enabling DPD tracking cal
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error code to convey that post PA data fed back into ORx has a very low signal to noise ratio for DPD tracking cal to perform correlations with Tx data and therefore adaptation will not be performed.
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error code to convey that the ORx signal received by DPD is saturating
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error code to convey that the Tx signal is too small to perform DPD adaptation
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error code to convey that the Tx signal is too small to perform DPD adaptation
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error code to convey that the Tx signal exceeds the maximum ADC code and could be potentially clipped causing spectral distortion
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error code to convey that the DPD adaptation has encountered too many AM-AM outliers (i.e. Big difference in Tx and ORx samples). This could be caused due to memory effect of the PA or Tx attenuation and ORx gain settings. A misalignment in Tx and ORx samples due to a bad path delay estimation could also cause this error.
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : The DPD model supplied to guide the internal DPD adaptation via DpdModelConfigSet() contains memory terms that cannot be accomodated due to hardware limitations
RECOMMENDED RECOVERY ACTIONS
Please refer to the DPD actuator LUT limitations in the ADRV9029 user guide while generating DPD models.
ROOT CAUSE : The degree of non-linearity for the DPD model supplied to guide the internal DPD adaptation via DpdModelConfigSet() cmd cannot be synthesized into the actuator Look Up Tables
RECOMMENDED RECOVERY ACTIONS
Please refer to the DPD actuator LUT limitations in the ADRV9029 user guide while generating prior DPD models to guide adaptation
ROOT CAUSE : The DPD model supplied to guide internal DPD adaptation via DpdModelConfigSet() violates the restrictions imposed by the DPD actuator hardware for memory(i) and cross terms(i)
RECOMMENDED RECOVERY ACTIONS
Please refer to the DPD actuator LUT limitations in the ADRV9029 user guide while generating prior DPD models to guide adaptation
ROOT CAUSE : The DPD model supplied to guide internal DPD adaptation via DpdModelConfigSet() violates the restrictions imposed by the DPD actuator hardware for LUT usage
RECOMMENDED RECOVERY ACTIONS
Please refer to the DPD actuator LUT limitations in the ADRV9029 user guide while generating prior DPD models to guide adaptation
ROOT CAUSE : The DPD model supplied to guide internal DPD adaptation via DpdModelConfigSet() violates the restrictions imposed by the DPD actuator hardware for roaming LUTs.
RECOMMENDED RECOVERY ACTIONS
Please refer to the DPD actuator LUT limitations in the ADRV9029 user guide while generating prior DPD models to guide adaptation
ROOT CAUSE : Error code to convey that the firmware could not update the DPD actuator look up tables. This could be due to other transactions in the system which have occupied the AHB bus and as a result the transaction cannot be performed.
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error code to convey that the DPD hardware is in use by another feature. Typical root cause of this error might be due to correlators being in use by another hardware. This error should not occur since the scheduler in the firmware takes care of scheduling various tracking cals competing for resources.
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error code to convey that there was a DPD data capture failure. This might be caused due to TX/ORx signal paths not being enabled to capture data OR the capture engine paused due to other systemic issues
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error code to convey that the cross correlation caused an error due to a timeout in the hardware correlator. This is typically observed when there is not enough headroom in the signal to perform DPD adaptation.
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : The DPD algorithm has encountered one or more of the following
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE :A semaphore based synchronization mechanism was introduced b/w DPD and CLGC algorithms in SW 3.0 to ensure that there is no race condition between the two. With the synchronization mechanism, CLGC is always guarenteed to finish execution before DPD. The DPD-CLGC syncrhonization error indicates that DPD and CLGC semaphores were not exchanged successfully causing this error.
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE :This error occurs when the degree of GMP polynomial (especially the power term 'k') plus the Tx sample magnitude is high causing an overlflow of the calculated LUT entry.
RECOMMENDED RECOVERY ACTIONS
The user can try modifying the DPD model programmed via DpdModelConfigSet() command to reduce the no. of Sum of Product terms in the GMP polynomial used to model the PA(DPD Model) assigned to a LUT.
ROOT CAUSE :This error occurs when the degree of GMP polynomial (especially the power term 'k') plus the Tx sample magnitude is high causing an overlflow of the calculated LUT entry.
RECOMMENDED RECOVERY ACTIONS
The user can try modifying the DPD model to reduce the no. of Sum of Product terms in the GMP polynomial used to model the PA(DPD Model).
ROOT CAUSE :This error occurs when the Inter-processor communication between ARM-C to ARM-D fails.
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : This error occurs when DPD and CLGC are both enabled. The DPD and CLGC tracking cals are internally synchronized through a semaphore mechanism.
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error to convey that the DPD capture has timed out waiting for 1 second or more for a scheduled DPD capture to finish.
RECOMMENDED RECOVERY ACTIONS
ROOT CAUSE : Error to convey that the coefficient decomposition hardware is unable to resolve coefficients from auto-correlation / cross-correlation outputs during DPD adaptation
RECOMMENDED RECOVERY ACTIONS