Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

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.

IWRL6432BOOST: 1D FFT Data Format in IWRL6432 OOB Demo

Part Number: IWRL6432BOOST

Hi expert.

    Customer has question about output of the 1DFFT (range) data.

As the following fig, the comments does not say about DPIF_RADARCUBE_FORMAT_6.

They would like to know what the radar cube format is in DPIF_RADARCUBE_FORMAT_6.

 

 

If they try to change DPIF_RADARCUBE_FORMAT_6  to  DPIF_RADARCUBE_FORMAT_2

 

They get the error of range processing shown below. 

 

Can you please help to provide more information about PIF_RADARCUBE_FORMAT_6???

Regards

Andre

  • Hello,

    You receive the error because DPIF_RADARCUBE_FORMAT_6 is the only valid format in SDK 5. It cannot be changed to any of the other formats. 

    As for more information on the specifics of format 6, allow me some time to look into that for you.

    Regards,

    Luke 

  • Hi Andre, 

    To answer the last portion of your question, the format PIF_RADARCUBE_FORMAT_6 is a 4-dimensional matrix as

    cmplx16ImRe_t x[numDopplerChirps][numTxAnt][numRxAnt][numRangeBins]

  • Hi Luke,

    Thanks for the reply.

    Could you tell me where to find this 4-D matrix? Or how is this 4-D matrix mapped into the memory?

    It seems that I could get from gMmwMssMCB.radarCube[0].data, but this is not an 4-D.

    Best regards,

    ChiaChih

  • Hello,

    The matrix is stored in memory as a static memory pool by the function DPC_ObjDet_MemPoolAlloc, so you cannot simply index it as a 4D array. 

    The DOA DPU uses the radar cube as an input for processing. Study how it access the radarCube in motion_detect.c.

    How it sets up access to the radar cube as an input source in mmwDemo_doaProcConfig, and then how the radar cube is passed into the actual processing function: 

    retVal = DPU_DoaProc_process(gMmwMssMCB.doaProcDpuHandle, &gMmwMssMCB.radarCubeSrc[MMW_DEMO_MAJOR_MODE], &gMmwMssMCB.detMatrix[MMW_DEMO_MAJOR_MODE], &outParmsDoaproc);

    where is &gMmwMssMCB.radarCubeSrc[MMW_DEMO_MAJOR_MODE] of type DPU_DoaProc_RadarCubeSource *radarCubeSrc

    Look at Section 6 in "[SDK5_DIRECTORY]/docs/MotionPresenceDetectionDemo_documentation.pdf" for more information about implementation.

    Regards,

    Luke