AWR2944: LODIST calibration failure

Part Number: AWR2944

Hi Expert,

During the startup phase, sometimes our board encounters an error with “Error code -3122 and subsys 124."

Refer to the 'mmWave-Radar-Interface-Control.pdf', this issue is caused by the failure of LO distribution during boot calibration.

The value of calibrationStatus is 0xFEE and LODIST calibration bit is 0.

What could be the reasons causing this error?

Additionally, we currently do not enable restoreEnable. Is it a better approach to perform an RF boot calibration in a stable environment and then restore the calibration values upon power-up?

Wu Bin

  • Hi,

    Can you please add the following information as well

    1) What is the DFP version you are using.

    2) Is the LODIST calibration enabled during boot time

    3) What happens if you issue a RF_INIT again after this failure. Do you observe the same calibration status flags or different flags.

    Thanks,

    Pradipta.

  • Hello Pradipta,

    1. DFP Version: 02.04.05.03

    2. Yes, the LODIST calibration was enabled and most of the boots are successful for LODIST calibration.

    3.If the LODIST calibration fails, the watchdog will reset 2944, and the LODIST calibration will be successful upon the next boot.

    Regards,

    Wu Bin

  • Hello Pradipta,

    We modified the code to call RF_init again after calibration failure, the result is that LODIST calibration will be successful after several re_init.

  • We have programed the sdk(04_06_00_01) to our board and found the same issue.

  • Hi,

    Let me check this internally within the team and provide a resolution to you over email. If that resolves the issue, we can close this ticket. 

    Thanks,

    Pradipta.

  • Hello Pradipta,

    I just conducted a test and there are still some issues, but the occurrence rate has decreased compared to before(before 1 minute; now: 10+ minutes)

    Strangely, when I tried other boards (with the previous firmware), I didn't experience this issue.

    Could you please inform me of the modifications made in the new firmware?

    I placed the radar board on a foam board (with the antenna facing the film board) to more easily reproduce this issue.

    What could be the possible cause of this issue? Is it related to the antenna or temperature? 

     

    Wu Bin

  • Hi,

    I just conducted a test and there are still some issues, but the occurrence rate has decreased compared to before(before 1 minute; now: 10+ minutes)

    Please clarify the testing procedure here so that it is clearer to us. Can you share the portion of the code where the workflow or code flow can be understood better?

    In your test application do you perform the boot time calibration and observe failure or are you performing boot time calibration repeatedly and observing failure or are you performing boot time calibration once and performing run time calibrations and observing failure there.

    Strangely, when I tried other boards (with the previous firmware), I didn't experience this issue.

    So, are you observing the LO DIST failure only on one device? Can you also specify your failure rate?

    I placed the radar board on a foam board (with the antenna facing the film board) to more easily reproduce this issue.

    What could be the possible cause of this issue? Is it related to the antenna or temperature? 

    We need to first pinpoint the issue and then we can provide the cause of it. Currently some points still need clarification. 

    Thanks,

    Pradipta.

  • Hello Pradipta,

    1. Based on mmwave_mcuplus_sdk_04_06_00_01, I have modified two places:
    • Open CLI_BYPASS macro and change radar configuration as show in the below image.
     
    • Add the below code to MmwDemo_transmitProcessedOutput() interface to reset AWR2944 after power on 2s
    Then, execute "gmake mmwDemoDDM" to build and genrate image file.
     So, the test is performing boot time calibration repeatedly and observe failure. 
    2. We have observed the LO DIST failure on more than one device. However, currently, we can only reproduce the issue by performing the above  test on one device. 
  • Hello, Pradipta

    Share our recent testing results. Before open_sensor, we add debug code to output the informations of RF related temperatures.

    then we found:

    Using new firmware you provided, Radar failed to power on  when Tx temperature is approximately 91 deg.

    Using old firmware from mmwave_mcuplus_sdk_04_06_00_01 package, Radar failed to power on when Tx temperature is approximately 81 deg.

    However, we make same test using the other radar board. Even if the temperature is greater than 100 degrees, radar can still start normally.

    Did you modify the threshold for LODIST failure judgment? Where can we find LODIST calibration detail decriptions?  Understanding the calibration feature can assist us in identifying the cause of the failure.

    Thanks,

    Wu Bin

  • Please clarify the testing procedure here so that it is clearer to us.

    The test case is to use AWR2944 pull down enable pin of PMIC every 2s. So AWR2944 will power on/off every 2 seconds.

    Thanks,

    Chris