Why LOL tracking calibration is not completed?

Can you please share the TX LOL calibration status log using TALISE_getTxLolStatus() API , please print the error Code, iterCount and update count as well .

Are you enabling the TX LOL tracking cal using enableTrackingCals() API and also the radio must be in ON state while enabling the calibration.

Please refer to "ADRV9009 Transmitter LO Leakage Tracking Calibration" page 179 and "System Considerations for Tracking Calibrations" section for more details from UG.

Yes, I enabled the TX LOL tracking cal. And the Radio was turned on after talise_setup was called.  

The status returned from TALISE_getTxLolStatus is always:
Cal Status: error: 0, percentage 0, iterCount: 53, update count: 53

Is the iter and update count incrementing while checking the TALISE_getTxLolStatus() API or stuck with iter and update count of 53? If its incrementing , it means that the LOL cal is running.

Kindly ignore the percentage parameter , we should consider the error , iter and update count to ensure that the cal is running.

It stuck with the iter and update count of 53. 

Is there any sugguestion?

The Arm processor scheduler must know which feedback is currently available so to schedule the correct transmitter LO leakage tracking calibrations.

We will need the feedback path for the external LOL cal to run and to get the specified performance of LO leakage level.

Is the TX to ORx mapping set properly as per your desired configuration? Also, please crosscheck the mapping as shown below 

Is the iter count incrementing alone incrementing, can you run the LOL cal for few iterations say 20, and check the TX LOL status.

Can you please go through the ARM GPIO PINS" and "ADRV9008-2 and ADRV9009 Transmitter LO Leakage Tracking Calibration" section in the UG (PAGE 181)  and crosscheck the required configuration.

As I said, I used TALISE_setTxToOrxMapping(pd, 1, TAL_MAP_TX1_ORX, TAL_MAP_NONE) so ARM knows the Tx1 to Orx1 path is established. And I also enabled the transmitter LO leakage tracking calibration. But I can't see iter counter incrementing.

You requested me the run LOL cal for few iterations, I don't know how to control it.

Also, the iter count and update count was locked to 53. That means it did finish a number of calibrations. But why it stopped incrementing. Again I never see the iter count incrementing.

Another question: Does the LOL tracking calibration support both internal and external LO calibration? Or it only do for the external. 

XYing816 said:

You requested me the run LOL cal for few iterations, I don't know how to control it.

Can you try implementing  below block of code in python in your system and send me the log of the LOL status.

XYing816 said:

Does the LOL tracking calibration support both internal and external LO calibration? Or it only do for the external. 

It supports both internal and external LO calibration . Refer to Figure 108 and 109 for more details.

I did the equivalent C code of your python code after the adrv9009 setup done and radio was turned on and result is,
Tx LOL Trackign Cals Status ErrorCode 0 PercentComplete 0 VarianceMetric 0 IterCount 53 UpdateCount 53

It repeated the same for each iteration of the loop.

I was using my custom adrv9008-2 board for the test. 

XYing816 said:

I used TALISE_setTxToOrxMapping(pd, 1, TAL_MAP_TX1_ORX, TAL_MAP_NONE) so ARM knows the Tx1 to Orx1 path is established

Can you try setting the orx mapping to TAL_MAP_TX1_ORX and see if the cal runs?

Are you using external LO or Internal LO calibration? Is the Tx fed back to Orx path?

As the QEC cal is running , this seems to be mostly a mapping issue . 

Can you please have a look at page 173 in UG  for running the calibrations.