• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 510 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

AWRL1432：ATE calibration & Factory calibration difference

AWRL1432：Factory parameter setting

ZHU CHEN
Prodigy 30 points
Part Number: AWRL1432
Other Parts Discussed in Thread: AWR1843,

Hi Ti team,

Thank you for your previous replies,
The article content is: AWRL1432：ATE calibration & Factory calibration difference.


In my last reply, you suggested that I need to set both saveEnable and restoreEnable to "1 0" first, and then change them back to "0 1" later.

Later, I checked to see if other ICs had factory parameter settings like 1432, but I found that their settings were not the same.
Taking AWR1843 as an example,
It was found that their calibData parameters were set to "0 0" in saveEnable and restoreEnable.

I would like to ask why only 1432 needs to execute the saveEnable and restoreEnable steps respectively?
Is it because 1432 itself is different from other ICs that it can only be set separately during calibration?

AWR1432 sdk version is 5.3.0.2
AWR1843 sdk version is 3.5.0.4

Best Wishes,

YAN ZHU CHEN

  • 0
    TI__Expert 3760 points

    Hi Yan Zhu Chen,

    The calibration strategy is different for AWR1843 and AWRL1432.

    If you don't enable both save and restore the MMIC AWR1843 performs self-calibration at every bootup which is not the same in AWRL1432.

    Thanks,
    Kundan

  • 0 in reply to Kundan Somala
    Prodigy 30 points

    Hi Kundan,

    Can 1432 set save and restore to 0 0 like AWR1843?

    Would you recommend me to set it up this way? If not, can you please tell me why?

    Thank you.

    YAN ZHU CHEN

  • 0 in reply to ZHU CHEN
    TI__Expert 3760 points

    Hi Yan Zhu Chen,

    As mentioned earlier also Factory calibrations are recommended to be performed only once in the factory in a controlled environment(at certain temp & no Interference) and whatever factory calibration data which we save to flash memory after performing needs to be restored in the infield operation.

    So we recommend to set it to save enable=1 for the very first time in the factory and restore enable=1 during the infield operation.

    If you do both save enable=0 and restore enable=0 the application code triggers factory cals at every bootup which is not recommended as there might be significant change in temperature within successive boot cycles.

    Hope this information is clear. 

    Thanks,
    Kundan