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.

TDA3: Chirp Frame framePeriodicity

Part Number: TDA3

Hi,

I am trying to understand how the data flow and its associated timing from the time the processing chain received SYSTEM_CMD_NEW_DATA  IPC into the issCaptureLink. When I specified the framePeriodicity to be 66ms in TDA3, the issCaptureLink receives IPC of SYSTEM_CMD_NEW_DATA  at 66ms rate. Does the framePeriodicity tell the 1243 to fire the chirp frames at 66ms interval? In another word, if the defined number of chirps in a frame is only takes 4ms (128 chirps 31usec chirp duration), the 1243 will NOT fire the next chirp frame until 66ms elapsed. Please confirm if my understanding is correct.

Thanks,

--Khai

  • Khai,

    The frame periodicity is determined by the Frame Configuration parameters.
    /* When Advanced frame configuration is set this is ignored */
    static rlFrameCfg_t gAr1243FrmArgs =
    {
    .chirpStartIdx = (rlUInt16_t) 0,
    .chirpEndIdx = (rlUInt16_t) CHAINS_RADAR_NUM_TX_ANTENNA - (rlUInt16_t)1,
    .numLoops = (rlUInt16_t) AR1243_RADAR_HEIGHT,
    .numFrames = (rlUInt16_t) 0,
    /* profileCfgArgs[1].numAdcSamples * 2 - 512 * 2*/
    .numAdcSamples = (rlUInt16_t) AR1243_PROFILE1_RADAR_WIDTH * (rlUInt16_t)2,
    .framePeriodicity = (rlUInt32_t) CHAINS_AR1243_TIME_MS_TO_5NS(66U), /* 33 ms / 30 FPS, 20 ms / 50fps */ --> This is the frame periodicity.
    .triggerSelect = (rlUInt16_t) RL_FRAMESTRT_API_TRIGGER, --> This mentions that the frames are triggered from AWR1243 itself based on an AWR1243 internal timer.
    .reserved0 = (rlUInt32_t) 0,
    .reserved1 = (rlUInt32_t) 0,
    .frameTriggerDelay = (rlUInt32_t) 0
    };

    Thanks and Regards,
    Piyali