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.

IWR6843ISK-ODS: 68xx_area_scanner

Part Number: IWR6843ISK-ODS

About  labs: 68xx_area_scanner 

Why doesn't it need to be execute Range FFT?

Do you have the algorithm documentation to us?

Like the following document  http://www.ti.com/tool/TIDEP-01000

objectdetection.c , line2437

/*==============================================
Chirp Processing
===============================================*/
#ifndef OBJDET_NO_RANGE
if (((objDetObj->chirpIndex % subFrmObj->staticCfg.numChirpsPerFrame)== 0) &&
(processCallBack->processFrameBeginCallBackFxn != NULL))
{
(*processCallBack->processFrameBeginCallBackFxn)(objDetObj->subFrameIndx);
}
retVal = DPU_RangeProcDSP_process(subFrmObj->dpuRangeObj, &outRangeProc);
if (retVal != 0)
{
goto exit;
}

objDetObj->chirpEndTime = Cycleprofiler_getTimeStamp();

/* Chirp is processed, increse chirpIndex */
objDetObj->chirpIndex += numChirpsPerChirpEvent;

if (outRangeProc.endOfChirp == true)
#endif

  • Please refer to C:\ti\mmwave_sdk_03_03_00_03\docs\mmwave_sdk_user_guide.pdf  figure 10:Scalable data processing chain using mmWave SDK

    It shows that the range processing can happen either on DSP or HWA.

    If  pre-processor OBJDET_NO_RANGE is defined, that means the Range FFT is happening on R4 instead of DSP.

    Let me know if you need more information.

    Thanks

    Yogesh