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.

MMWCAS-DSP-EVM: What is the output data structure?

Part Number: MMWCAS-DSP-EVM
Other Parts Discussed in Thread: TDA2

Hi, in the processor sdk radar datasheet page 17 the data flow is shown:

but in the doc the format/structure of the output data sent to matlab is not shown (in the awr series radar each lab had documentation about the tlv format), where could I find this info for the TDA2?, thanks

  • Hello Jairo, 

    Please refer to the below linked FAQ page for this : 

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/925288/faq-mmwcas-rf-evm-cascade-board-related-queries (#6) 

    Hope this helps. Let us know if you need further assistance. 

    Regards,

    Ishita

  • Hi ,

    I have read the posts of the link but I think is not what we are looking for, the posts are questions about how to work with the raw data of the sensor, we want the processed data (range, speed, angle, etc), I found this .m script where mentions the tlvs but inside that folder there is no documentation about the tlv format, we need that documentation and also the name of the .c file which generates the packet in the tlv format and send it over ethernet to matlab to know what is the format of the processed data

    file: radar_cascade_demo.m

    source: C:\PROCESSOR_SDK_RADAR_03_08_00_00\vision_sdk\apps\src\rtos\radar\src\usecases\cascade_radar_object_detect

    this is a piece of the  radar_cascade_demo.m code where mentions the TLVs :

     % get the packet header
            [msgHeader, byteVecIdx, frameNum] = getBufferHeader(dataArray, frameNum);
    
            if  msgHeader.totalLength == 0
                continue;
            end
            Params.gui.cloudPointsPresent = 0;
            Params.gui.rangeProfilePresent = 0;
            Params.gui.azimHeatMapPresent = 0;
            Params.gui.rangeDopplerHeatMapPresent = 0;
            pointCloud.numObj = 0;
    
            for tlvIdx = 1: msgHeader.numTLVs
                [tlv, byteVecIdx] = getNextTLV(dataArray, byteVecIdx);
                 switch tlv.type
                    case OP_SECTION_DATATYPE_SYSTEM_INFO
                        [systemInfo, byteVecIdx] = getSystemInfo(dataArray,...
                                                   byteVecIdx);
                        if systemInfo.numDopplerBins ~= Params.numDopplerBins
                            fprintf('ERROR: Unexpected Doppler FFT size!\n');
                            return;
                            EXIT_KEY_PRESSED = 1;