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.

CCS: AWR1843 : Questions about self-calibration fail occurred.

Tool/software: Code Composer Studio

Reference to the document AWR1xxx_Radar_Interface_Control.pdf,  chapter 5.13.20 and 5.2.11

I have below questions

1. If the self-calibration fail occurred, does the fail calibration report keep in the register AWR RUN TIME CALIBRATION CONF AND TRIGGER SB?  or will update the status of next self-calibration result?

2. if the self-calibration fail occurred, is there any suggestion the allow us to have a way to improve this situation?

3. Does the calibration data (5.2.11) allow us to analyze what caused the error occurred?

 Thanks 

  • Hi

    Same questions as in your previous thread.

    What sw are you running?

    thank you
    Cesar


    e2e.ti.com/.../2878085
  • Hi
    Thanks for the reply

    We are using mmwave demo, enable self-calibration, we can monitor the report which report can get from mmwave _link.c (rlRfInitComplete_t / rlRfRunTimeCalibReport_t).

    We want to know what can we do, just in case, the self-calibration failed.

    Can you give a suggestion of above question? thanks a lot.
  • 1) ....will update the status of next self-calibration result?
    The report values are overwritten each time calibration is run.

    2) ...to have a way to improve this situation?
    It depends on the error. Specifically, errors caused by temperature could indicate environmental issues or possibly running a high duty chirp with high Tx power. BSS configuration (eg. Rx/Tx gain) could also result in a cal error.

    3) ...to analyze what caused the error occurred?
    Not specifically. The Restore SB (5.2.11) and Save SB (5.3.2) are used to Write (Restore) and Read (Save) the calibration data so that full calibration does not have to be run at every boot. This is useful for applications that boot from power-up very frequently. This data is not meaningful to any software other than the BSS firmware.