• State TI Thinks Resolved
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 79 views
  • Users 0 members are here
Support feedback
Options
Options
Related

IWRL6432AOP: Regarding rl_rlfecssRfFactoryCal

user4810817
Intellectual 301 points
Part Number: IWRL6432AOP
Other Parts Discussed in Thread: IWRL6432

Tool/software:

We would like to confirm the timing for executing the rl_rlfecssRfFactoryCal API and the meaning of its parameters.

Q1)Regarding execution timing
The manual states the following:
This API function configures and triggers the FECSS RF factory calibrations. The application should use this API to perform one-time RF configuration dependent calibrations (factory calibration) and store the results in non-volatile memory with the help of FECSS Factory Calibration Data Get API.

Is it correct to understand that this API only needs to be executed once before the product is shipped to the market?

Q2)After shipped to the market, is it acceptable to execute this API every time the radar is started ?
If there is any issue with doing so, please explain the reason.

Q3)Regarding the h_CalCtrlBitMask parameter
We have a question about the following description in the manual:bits [5] RX IFA calibration ON/OFF control.
Note: Required only for pre-production samples – to be used with ATE calibration FW build

Does the IWRL6432AOP qualify as a pre-production sample?
Or does this only apply to EVMs?

[Referenced Documents]

MMWAVE_L_SDK_05_05_03_00
mmwave_dfp_interface_control_document.pdf
Section 2.3.5 FECSS Factory Calibration API

  • 0
    TI__Mastermind 20901 points

    Hello, 

    user4810817 said:
    Is it correct to understand that this API only needs to be executed once before the product is shipped to the market?

    Yes this is a valid option. The factory calibrations can be run once in the factory and then saved to flash memory using rl_fecssRfFactoryCalDataSet, then after the product is shipped to the market, after each boot rl_fecssRfFactoryCalDataGet should be used to restore the calibration data that was saved to flash memory instead of rerunning the calibrations every time.

    user4810817 said:
    Q2)After shipped to the market, is it acceptable to execute this API every time the radar is started ?
    If there is any issue with doing so, please explain the reason.

    Yes, an alternative to the factory calibration save / restore method described above would just be to allow the application to rerun the factory calibrations after each boot. This is acceptable for most use cases as long as you do not expect any other 60GHz interferers near to the radar at the time of calibration.

    user4810817 said:
    Does the IWRL6432AOP qualify as a pre-production sample?
    Or does this only apply to EVMs?

    This was required for very early samples of IWRL6432 which did not have ATE calibration data stored in eFuse. This is not applicable for IWRL6432AOP.

    Best regards,

    Josh

  • 0 in reply to Josh Dye
    Intellectual 301 points

    Thank you very much for your response.

    I noticed that there may be a mistake in the information you provided, so I would like to confirm just to be sure.
    My understanding is that the API rl_fecssRfFactoryCalDataGet is used to save the calibration data to flash memory, and rl_fecssRfFactoryCalDataSet is used to restore it during boot to restore the calibration data.
    Could you please confirm if this is correct?

  • 0 in reply to user4810817
    TI__Mastermind 20901 points

    Hello, 

    Yes my apologies, your latest reply is correct. My response has the APIs flipped.

    Regards,

    Josh