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.

IWR1642BOOST: Request help understanding how to customize DSP chain

Part Number: IWR1642BOOST

Hello.

I have read through the mmWave SDK documentation and watched several of the training videos explaining the SDK.  I have also successfully built the out-of-box demo from source and got it running properly through the web-based visualization tool.

I am now at the point where I would like to modify the signal processing chain (e.g. add in additional filters or other custom blocks).  It is not immediately clear to me where I can do that type of development and/or how much I am able to customize without sending the raw data out to an external FPGA.  Is there some sort of step-by-step guide that would walk me through this process?  If not, any insight or pointers would be greatly appreciated.

Eric

  • Hi Eric,

    Have you had a chance to look at the following video?

    https://training.ti.com/easy-evaluation-and-development-mmwave-systems-software-development-kit

    1. Please make sure to understand the creation, initialization and runtime view of the DPU and DPC in the OOB demo especially what data structures are used for initialization of the DPC and DPUs through the DPM.

    2. Also take the time to refer back to the highlighted source code constructs to develop a deep understanding on what functions encapsulate the core runtime processing for the corresponding DPUs (e.g. DPU_AoAProcHWA_process which performs the AOA processing every frame). The simplest way would be to add your additional processing in one of the existing DPUs depending upon where in the signal chain it falls.

    3. Look at the section "Extending the SDK architecture for advanced applications" in the above training and refer to the demos we developed on top of the out of box demo to add tracking functionality and the custom DPUs (and DPCs) developed for this purpose outside the ones provided in the SDK. Again, please make sure to invest time to study the code for these additional components (e.g. trackerProc DPU) to understand what all goes into creating a DPU and integrating it with the SDK chain.

    The above should provide you good understanding on adding your custom processing or filters to the demo chain.

    Regards

    -Nitin