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.

AWR1843BOOST: Want to known more on self-Calibrations

Part Number: AWR1843BOOST
Other Parts Discussed in Thread: AWR1843

Hello TI Team,

Greetings from Miit Prajapati,

I m using AWR1843Boost for my project, I have question regarding calibration.

1. If ADC DC Offset calibration will turn OFF. This will impact on the Range and velocity detection of the Boost..?

2.TI mentioned in self-calibration document that AWR1843 will create a lookup table for the TX power calibration and RX gain calibration. How AWR1843Boost will store it and where..?

3.Ti mentioned in self-calibration document that The LUT can also be replaced with a user-programmed LUT for TX power calibration and RX gain calibration, Who user will replace the LUT..?

4.I want to know more about  TX Phase Shifter Calibration, How it is working and what is a significance of this calibration..?

Thanks & Regards

Miit Prajapati.

  • Hi,

    1) There will be a very mild impact on range and other parameters.

    2) The AWR1843 device will store it in a memory internally. 

    3) The user if required can replace the current LUT values with a user programmed LUT (for example, with an LUT that was previously read back from the
    device). There are APIs available to read and write to these LUTs.

    4) Tx Phase Shifter Calibrations is explained in the below app note. Will request you to go through it once. 

    ti.com/lit/an/spracv2/spracv2.pdf?ts=1691669244905

    Thanks,

    Pradipta.

  • Hello Pradipta,

    Can you please give me some reference or example code for the LUT table replacing.?.

    Thanks & Regards.

    Miit Prajapati.

  • Hi,

    We do not have an exact example code just for that purpose. 

    Can point to example code for AWR1843 which makes use of all the API's that will be required for this. 

    Please refer to the below path: ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\control\mmwavelink\test\common

    Refer to link_test.c and mmwavelink_test_common.c files for the implementation.

    /* mmWave Link Get RX Gain Temperature LUT configuration */
            if (mmwaveLink_RxGainTempLutRead() < 0)
            {
                MCPI_setFeatureTestResult ("Get mmWave Link RX Gain Temperature LUT config", MCPI_TestResult_FAIL);
                return;
            }
            MCPI_setFeatureTestResult ("Get mmWave Link RX Gain Temperature LUT config", MCPI_TestResult_PASS);
    
            /* mmWave Link Get TX Gain Temperature LUT configuration */
            if (mmwaveLink_TxGainTempLutRead() < 0)
            {
                MCPI_setFeatureTestResult ("Get mmWave Link TX Gain Temperature LUT config", MCPI_TestResult_FAIL);
                return;
            }
            MCPI_setFeatureTestResult ("Get mmWave Link TX Gain Temperature LUT config", MCPI_TestResult_PASS);
    
            if (platformType != RL_AR_DEVICETYPE_68XX)
            {
                /* mmWave Link Set RX Gain Temperature LUT configuration */
                if (mmwaveLink_RxGainTempLutConfig() < 0)
                {
                    MCPI_setFeatureTestResult ("Set mmWave Link RX Gain Temperature LUT config", MCPI_TestResult_FAIL);
                    return;
                }
                MCPI_setFeatureTestResult ("Set mmWave Link RX Gain Temperature LUT config", MCPI_TestResult_PASS);
    
    
                /* mmWave Link Set TX Gain Temperature LUT configuration */
                if (mmwaveLink_TxGainTempLutConfig() < 0)
                {
                    MCPI_setFeatureTestResult ("Set mmWave Link TX Gain Temperature LUT config", MCPI_TestResult_FAIL);
                    return;
                }
                MCPI_setFeatureTestResult ("Set mmWave Link TX Gain Temperature LUT config", MCPI_TestResult_PASS);
            }
    

    This should help you out in your custom code formation. 

    Thanks,

    Pradipta.