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: Sensors forum

Part Number: MMWCAS-DSP-EVM


Hi

I would like to have a better understanding of the build config in "vision_sdk_apps\configs\tda2xx_cascade_linux_radar"

From what I can read in the cfg.mk, it seems to be compiling at least 3 of the usecases in this directory: vision_sdk\apps\src\hlos\adas\src\usecases

UC_cascade_radar_capture_linux_only=yes
UC_cascade_radar_datacollect=yes
UC_cascade_radar_multi_datacollect=yes
ifeq ($(RADAR_STUDIO), yes)
UC_cascade_radar_datacollect_radar_studio=yes
endif

As far as my understanding goes, each use case is separate? How can it be compiling all three into one binary?

Please help me clear up my misunderstanding :)

Kind regards

Daniel

  • Hi Daniel,

    There are 3 separate usecases as you mentioned with each having its own links and chain in SW. Based on the build time options, each of these usecases can be compiled into a single binary (or a single top-level application whose binary you are referring to) and can be switched between one another based on the user's input choice over UART in the run time menu after the boot. The UC macros for different chains will be generated by the configuration in the makefiles and made available to the source code below which chooses which source code to include at build time.

    PROCESSOR_SDK_RADAR_03_08_00_00\vision_sdk\apps\src\rtos\radar\src\common\chains_radar_main.c

    Hope this resolved your question, if not let me know if further support is required.

    Regards,

    Kaushik

  • Thank you for the explanation :)