• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 252 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR1843: Range/Doppler Heatmap availability in MRR project

Claudio ANUCHNIK
Expert 1100 points
Part Number: AWR1843

Hi all,

We are developing an application based on the "mrr_18xx" demo project.

I suppose the Range/Doppler Heatmap full information should be available somewhere in memory of the DSS (radarCube, detmatrix, other?) for CFAR and other calculations that need it before the same memory space is used for other things or cleared.

If this is the case, I want to keep and store this information in other L3 free space for future use in the MSS section before the above happens.

So, I want to identify where in the DSS code I can find this.

Maybe in "MmwDemo_interFrameProcessing(MmwDemo_DSS_DataPathObj *obj, uint8_t subframeIndx)" function in "dss_data_path.c" file?

Thanks,

Claudio 

 

  • 0
    TI__Genius 15046 points

    Hi Claudio,

    As this is not a documented use case, I can't pinpoint this information quickly. You can get an idea of all the buffers present and being used by reading the MmwDemo_interFrameProcessing function. My observation is that the buffer pointers used to store various intermediate output are all part of  MmwDemo_DSS_DataPathObj. You can also have a look at MMW_ALLOC_BUF calls to see what buffers are being allocated for. This happens in the MmwDemo_dataPathConfigBuffers function. The  MMW_ALLOC_BUF is a macro which is a little contrived, but seeing the definition should clear it up.

    Regards,

    Aayush

  • 0 in reply to Aniket Mahajan
    Expert 1100 points

    Hi Aayush

    I'll try all this

    Thank you

    Claudio