• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 1468 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.

AWR1642: Question about profile parameters in SDK 1.1.02

Andy Yin
Genius 9390 points
Part Number: AWR1642

Hi,

I found there are below two new parameters in the new SDK 1.1.02, would u pls let me know the detail meaning and how to configure it? Seems for different frequency, the configuration is different, right?

In the mmw demo, the *.cfg file doesn't support the below configuration.

/**
* @brief Bit Description \n
b0 FORCE_VCO_SEL \n
0 - Use internal VCO selection \n
1 - Forced external VCO selection \n
b1 VCO_SEL \n
0 - VCO1 (76 - 78 GHz) \n
1 - VCO2 (77 - 81 GHz) \n
b7:2 RESERVED \n
*/
rlUInt8_t pfVcoSelect;
/**
* @brief Bit Description \n
b0 RETAIN_TXCAL_LUT \n
0 - Update TX calibration LUT \n
1 - Do not update TX calibration LUT \n
b1 RETAIN_RXCAL_LUT \n
0 - Update RX calibration LUT \n
1 - Do not update TX calibration LUT \n
b7:2 RESERVED \n
If PF_TX_OUTPUT_POWER_BACKOFF is changed then set RETAIN_TXCAL_LUT to 0, \n
else set it to 1 and if PF_RX_GAIN is changed, then set RETAIN_RXCAL_LUT to 0 \n
else set them to 1.
*/
rlUInt8_t pfCalLutUpdate;

BR,

Andy

  • 0
    TI__Guru 69990 points
    Hello Andy,
    These parameters have been added to support invoking profileCfg API during frame-ongoing (i.e. Dynamic Profile setting).

    pfVcoSelect: This option is to select VCO of the device, VCO1: 76-77GHz; VCO2: 77-81GHz. This selection should match with the frequency selected in further parameter (startFreqConst) of profileCfg.
    pfCalLutUpdate: This is the main member which enables dynamic profile configuration while a frame is ongoing. If user wants to update any parameters of profileCfg except Tx_backOff and Rx_gain then set bit0:1 & bit1:1; in this case radarSS won't update LUT (Look up table) for TX/RX calibrations while switching to next frame. In other case if Tx_backOff and/or Rx_gain is changed while invoking profileCfg dynamically then set bit0:0 & bit1:0; then radarSS will update LUT by doing calibration at pre-defined time. This calibration duration user can set (rlRfCalMonTimeUntConf_t: calibMonTimeUnit) or if not set then it's by default 100 worth of frames.

    SDK doesn't support these features via CLI option but internally you can set these values or modify CLI options to take these parameters over CLI.


    Regards,
    Jitendra
  • 0 in reply to Jitendra Gupta
    TI__Genius 9390 points
    Jitendra,
    pfVcoSelect: there is one bit for VCO selection, is it able to use external VCO? And how to do the hardware design if use external VCO?
    1 - Forced external VCO selection \n

    pfCalLutUpdate: Before BU has ever told me it is not able to do profile dynamic reconfiguration when a frame is ongoing. Based on your description if Tx_backOff and Rx_gain are not changed, then it is able to reconfig the profile while a frame is still ongoing, right?

    BR,
    Andy
  • 0 in reply to Andy Yin
    TI__Genius 9390 points
    Jitendra,

    Would u pls help give any more comments on my pre and below queries, thanks.
    For the pfVcoSelect parameter, i found its value is zero in the mmw demo, in profile_2d.cfg the startFreqConst is 77GHz, the freqSlopeConst=68MHz/us, rampEndTime=58us, the total bandwidth = 68*58=3.994GHz, so the frequency range is 77~81GHz, so should set the pfVcoSelect bit1:1, right?
    If the pfVcoSelect is not matched with the frequency, is there any problem?

    Thanks & BR,
    Andy
  • 0 in reply to Andy Yin
    TI__Guru 69990 points

    Hello Andy,

    For frequency range 77-81 GHz you need to choose VCO2 (pfVcoSelect bit1:1), you are right with that assumption.

    If pfVcoSelect doesn't match then device's functionality may not work.

    Answers to the last post-

    pfVcoSelect:bit0 : 1 -

    VCO1 has better phase noise and VCO2 has a wider bandwidth.

    For the frequency range, 77-78 GHz user has an option to choose VCO1 to get the better phase noise compare to VCO2. So when user forces to choose VCO1 for this range, RadarSS forced to choose externally defined VCO selection not internally defined VCO selection (this feature is not related to external HW, but external selection option).

    Dynamic Profile configuration-

    Yes, if Tx_backOff and Rx_gain are not changed then the user can update profile during a frame is ongoing, else new setting will come into effect at next frame duration only.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    TI__Genius 9390 points
    Jitendra,

    Thanks and still not very clear about the VCO selection.
    Based on your description, seems if choose VCO1, it is need to use forced external VCO selection; if choose VCO2, should use internal VCO selection; right?
    BR,
    Andy
  • 0 in reply to Andy Yin
    TI__Guru 69990 points
    Hello Andy,
    There is an overlap region of 77-78 GHz in which any of the VCOs can be used, for other regions use only the VCO which can work in that region. For e.g. for 76-77 GHz use only VCO1 and for 78-81GHz use only VCO2, for 77-78 GHz, any VCO can be used.
    Also note that users should not inter-mix chirps from different VCOs within the same frame.

    So this forced VCO is applicable for [77-78] GHz where user can choose any VCO.
    For this [77-78]GHz VCO2: default-VCO/internal-VCO (pfVcoSelect bit1:0), VCO1: force-VCO/external-VCO (pfVcoSelect bit1:1).

    As [77-78]GHz band VCO1 has better phase noise so user can opt to VCO1 by setting [pfVcoSelect bit1:1], which effetively saying RadarSS to choose/force to VCO1.


    Regards,
    Jitendra