• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 394 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.

TDA2EXEVM: Understanding TXBF Use Case in Processor SDK

Khai Trinh
Genius 4140 points

Part Number: TDA2EXEVM

Hi,

The Document for this use case is not complete in ProcessorSDKRadar_UserGuide.pdf. If there is better more complete doc, please provide. I have following questions about the use case:

1. Why wasn't there a rlFrameCfg_t for this use case? frameCfgArgs in Bsp_Ar12xxConfigObj is set to NULL

2. Where is the 2 fps rate come from if rlFrameCfg_t is not configured in the use case?

3. CHAINS_CASCADE_BF_RADAR_FRAME_PERIODICITY_MS is not being used other than using to check for error at compile time

4. .txChannelEn in Bsp_Ar12xxConfigObj is set to 7 which means all 3 TXes for each AWR are turned ON while gChains_cascadeRadarBfChirpCfgArgsMaster.txEnable is set to 0. Which one has higher precedence?

5. All 3 slave AWRs' rlChirpCfg_t.txEnable are set to 7 (all 3 TXes are turned ON). Wasn't there a note  about only 2 TXes can be enabled for a chirp?

6. Bsp_Ar12xxConfigObj.rxChannelEn are all enabled. If I would like to only turn ON a certain number of rx channels on an AWR, is this is right parameter to not set to 15 or 1111 binary?

7. gChains_cascadeRadarBfChirpCfgArgsMaster.chirpEndIdx and the 3 slaves are all set to 20 which correspond to the 21 chirps variations against single defined profile. This use case uses 9 TXes, how are the 21 chirps index being transmitted out of the 9 TXes across 3 sensors?

Thanks,

--Khai

  • 0
    TI__Genius 14305 points

    Hi,

    I will check with team & get back

    Thanks

    Gaviraju

  • 0 in reply to Gaviraju Doddabettahalli Bettegowda
    Genius 4140 points

    Hi Gaviraju,

    I have more questions on TXBF. In the chains_common_cascade_ar12xx_config_bf.c with Sub-Frame configuration below:

    .subFrameCfg = {
    {
    .forceProfileIdx = (rlUInt16_t) 0,
    .chirpStartIdx = (rlUInt16_t) 0,
    .numOfChirps = (rlUInt16_t) CHAINS_CASCADE_BF_RADAR_NUM_CHIRPS,
    .numLoops = (rlUInt16_t) CHAINS_CASCADE_BF_RADAR_RADAR_HEIGHT,
    .burstPeriodicity = (rlUInt32_t) CHAINS_AR1243_TIME_MS_TO_5NS(500U),
    .chirpStartIdxOffset = (rlUInt16_t) 1,
    .numOfBurst = (rlUInt16_t) CHAINS_CASCADE_BF_RADAR_NUM_BURSTS,
    .numOfBurstLoops = (rlUInt16_t) CHAINS_CASCADE_BF_RADAR_NUM_BURST_LOOPS,
    .reserved0 = (rlUInt16_t) 0,
    .subFramePeriodicity = (rlUInt32_t) CHAINS_AR1243_TIME_MS_TO_5NS(500U),
    .reserved1 = (rlUInt32_t) 0,
    .reserved2 = (rlUInt32_t) 0
    },

    1. There is 1 subframe in this frame and 1 burst in a subframe and each burst contains 21 chirps (each corresponds to one steered angle). There are 2 periodicity parameters in burstPeriodicity and subFramePeriodicity . Which of these two dictate the actual fps?

    2. If there are more than 1 subframe in a frame and more than 1 burst in a subframe, how are these two parameters be set?

    3. Would the final fps be the product of number of subframes * number of burst in a subframe?

    Thanks,

    --Khai

  • 0 in reply to Khai Trinh
    TI__Guru 50045 points

    1. When advanced frame config is enabled, frameCfgArgs is not used.

    2. subFramePeriodicity = 500 ms so 2 fps.

    3. Correct. It is not used in configuration.

    4. txChannelEn is for sensor channel config. gChains_cascadeRadarBfChirpCfgArgsMaster.txEnable is for chirp config.

    5. Need to double check on this.

    6. You can do this in chirp config.

    7. 21 chirps on each radar use the same chirp config.

  • 0 in reply to Stanley Liu
    Genius 4140 points

    Question on 4. if rxChannelEn is set to 0 (disable all TX channels), this supersedes all settings and setting gChains_cascadeRadarBfChirpCfgArgsMaster.rxEnable in the chirp config does not have any affect. No chirps will be going out of the Txes on that sensor. Am i correct?

    Thanks,

    --Khai

  • 0 in reply to Khai Trinh
    TI__Guru 50045 points

    The best way to test the radar configuration is to use mmWave studio. It would sanity check the radar setting and report issue if there is any conflict.

    Once you get the desired configurations, it will be easy to convert that to the use case configuration in SDK.