This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

IWR1443: APLL calibration status

Part Number: IWR1443
Other Parts Discussed in Thread: MMWAVE-L-SDK

Hi,

I have modified the SDK 2.1.0.4 demo to monitor the rlRfRunTimeCalibReport_t.calibUpdateStatus and rlRfInitComplete_t.calibUpdate values in RL_RF_AE_RUN_TIME_CALIB_REPORT_SB and RL_RF_AE_INITCALIBSTATUS_SB.

The APLL update flag bit for both RF init and Run time is always 0 and I have never seen it set to 1. Is this correct behavior? I check these values while sweeping the temperature from 0℃ to 40℃ in a constant temperature chamber.

Best Regards,

Hiroyuki

  • Hello.

    Do you mean the return value for the rlRfInit function when you say APLL update flag?  From the documentation, it mentions that the return value for the initialization functions return 0 if the calibration was successful, and 1 if there is a failure.  Seeing all 0s indicate that you are not running into any failures upon front-end initialization/calibration.

    Sincerely,

    Santosh

  • Hi, Santosh,

    What I am referring to are the structures

    typedef struct rlRfInitComplete {...,rlUInt32_t calibStatus,...}

    and

    typedef struct rlRfRunTimeCalibReport {...,rlUInt32_t calibUpdateStatus,...}

    in mmwavelink.h.

    According to the comments in mmwavelink.h, these flags are set to 1 when the correction values are updated.

    This APLL updated flag is always 0 for both RF init calibration and runtime calibration, so I was curious and asked this question.

    Regards,

    Hiroyuki

  • Understood.

    Looking through those structs, I do not see the APLL update flag you are mentioning.  Are you referring to the calibStatus field in those two structs?  If so, those flags are set to 1 only if those calibrations failed or not performed at least once.  The calibUpdate/calibUpdateStatus flags only get set to 1 if the calibration requires a reconfiguration of the RF.  If you are talking about the calibUpdate flag, then I think it would only change to 1 if the values are changing.  If you run the device in debug mode, you can maybe check the values that you are expecting change in to see if they are actually changing.  I would suspect that they are not.

    Sincerely,

    Santosh

  • HI Santosh,

    Sorry, I'm referring to The calibUpdate/calibUpdateStatus flags.

    I understood that these flags are set to 1 if a reconfiguration occurs due to a temperature change.

    Bit1 (APLL flag) is never set to 1 even during RF init clibration or run time calibration where there is a temperature change of 10 degrees or more. Is this correct operation?

    Regards,

    Hiroyuki

  • Hello.

    After looking through the mmwavelink.h file, I noticed that you may have confused the temperature field and the calibUpdateStatus flag.  There is no runtime calibration feature for the 1443 device that does calibration for every 10 degree delta, and the calibUpdateStatus flag is just indicating that calibration resulted in reconfiguring the RF front-end.  This temperature delta recalibration is something done in the MMWAVE-L-SDK, but this SDK is not used for the 1443 device.

    Sincerely,

    Santosh