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.

TIDEP-01012: Difference between developing using the DFP and RADAR SDK ? which one is suitable on a non-TDA2x (custom board) with different CPUs?

Part Number: TIDEP-01012
Other Parts Discussed in Thread: AWR2243, AWR1243

I would like to know what is the main difference between developing using the DFP and RADAR SDK ? It seems like RADAR interface control API are only valid in DFP package? Could you please elaborate more. For us, we have a custom board (instead of a TDA2x), and we would like to be able to run our apps.out (or custom application) on linux (hlos)


  • Hi,

    The RADAR SDK is a TDA based framework. This framework is mainly used to implement the signal processing on the TDA.

    The communication with the sensor is done through the mmWave link API provided in the DFP.

    So, if you are not using TDA you would not need to consider the RADAR SDK.

    You would only need to use the mmWave Link API provided in the DFP.

    There are many example threads on e2e.

    I encourage you to use the google site search:

    site e2e.ti.com mmwave link

    thank you

    Cesar

  • Hi Cesar,

    Thanks for your clarifications. I understand that DFP package provided only support Windows.Would you be able to point/guide us on how we could compile DFP package in linux? 

    Also, please correct me if I'm wrong, in DFP package example given, AWR sensors are communicating via PC through ethernet. Can we modify the same example to run on linux? There aren't any documentation on running the DFP on link or custom board. It would be a huge help if you could guide us with this.

    Also, would the linux based DFP (once it's compiled) also work on TDA2x board? (i.e instead of running RTOS or apps.out(on hlos)?

    Regards,

    Shayan

  • Hi Cesar, 

    Sorry to spamming with multiple question.

    I also noticed in a post from 2018, (linke below), you've mentioned that "we don't have plans to support capture without mmwave studio", I was wondering whether this decision still witholds, or it has changed ever since. 

    Thanks,

    Shayan

  • Hello Shayan,

    Here are few e2e thread which may help you with Linux development for AWR device.

    https://e2e.ti.com/support/sensors/f/1023/t/627397?Linux-AWR1243BOOST-Porting-the-MMWAVELINK-Control-to-Linux

    https://e2e.ti.com/support/sensors/f/1023/t/797855

    https://e2e.ti.com/support/sensors/f/1023/t/801123?Linux-AWR1243BOOST-AWR1243-Async-Event-Handling

    https://e2e.ti.com/support/sensors/f/1023/t/963280?AWR2243-looking-for-the-DFP-library-source-code

    DFP package mainly provides the device firmware/patch and mmWaveLink library. Even TDA2x Radar SDK uses these two items within it to communicate with AWR device over SPI.

    AWR1243/AWR2243 requires firmware or patch to be loaded at the bootup time and later all the device configuration. Host application TDA2x (RADAR SDK application) or PC (DFP: mmwavelink example) or any other Host (connected with AWR device over SPI+CSI-2), communicate to AWR device over SPI. mmWaveLink provides all the callbacks and APIs which can be used to make this communication easier for Host Application. It just need to provide all the interface hooks to mmWaveLink in terms of callbacks (refer mmwavelink example and user guide from DFP).

    SO in your case as well, (non-TDA2x) embedded platform, you can either take reference from DFP mmwavelink example or port that to your Linux application. Above e2e threads and DFP user guide would help you in that task.

    BR,

    Jitendra