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.

IWRL6432:ATE calibration problem

Part Number: IWRL6432

HI.

When I was using MMWAVE_L_SDK_05_03_00_02, I found that after wiping the whole flash with uiflash, I reported an error without ATE calibration after re-burning mmwave_demo firmware. At this time, you need to re-burn the ATE firmware to run normally. If this is the case, you will need to burn the firmware twice during mass production. It's one more time than before, which affects efficiency. However, I found that running ATE firmware is to write some values on the address 0x80000, and every time after burning ATE firmware to run, I found that the value on the address 0x80000 will be different. During mass production, can we judge whether there is an ATE calibration value in flash through the program? If not, the ATE calibration value is directly written to the address 0x80000. This eliminates the need to burn the ATE calibration firmware. One question I have is whether each radar can write the same ATE calibration value?

best wishes

  • Hi,

    In the production samples, you need not run the ATE firmware. ATE calibration values need not be stored in Flash. 

    The current samples that your are using is a RF-untrimmed part. In order to eliminate device to device variations and RF calibration, ATE values are needed and they differ from sample to sample.

    The production samples will have the calibration values already set inside the device(RF trimmed part), so, the firmware will not fetch the ATE calibration values from Flash.

    So, at production, only firmware needs to be loaded into flash.

    Regards,

    Abhishek