• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 910 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: RangeDoppler and Azimuth HeatMaps

Claudio ANUCHNIK
Expert 1100 points
Part Number: AWR1843

Hi,

I am developing an application based on the "mrr_18xx_(dss/mss)" demo projects.

I want to know that, even not used in this application; if the DSS software places RangeDoppler and Azimuth HeatMaps after interFrame calculations in the radar cube memory in the L3 shared memory.

I've seen it in the "mmwave_sdk_18xx_(dss/mss)" projects.

If it does it: what are the addresses for those HeatMaps in the DSS and in the MSS? I know how to see L3 in both processors.

For debugging purposes I need to send those HeapMaps over UART or CAN with the MSS software.

I know, I have to lower the frame rate to make room for such a big bunch of data to be sent in inter frame time.

Thanks,

Claudio

  • 0
    TI__Guru 69960 points

    Helo Claudio,

    You can store your intermediate results in L3 memory and same can be accessed via MSS or DSS.

    Address scheme is different for MSS and DSS. Linker*.cmd files specifies this L3 address for MSS and DSS

    For MSS:  L3_RAM (RW)   : origin=0x51000000 

    For DSS: L3SRAM:         o = 0x20000000,

    So based on this address you can add the offset for that specific result data and on MSS end, same can be transferred over UART/CAN interface.

    But make sure that you have sufficient inter frame time, so while you are transferring over UART/CAN, same memory region is not updated by DSP processing chain-result flow.

    Regards,

    Jitendra

  • 0
    TI__Genius 15046 points

    Hi Claudio,

    The demo allows for both of these to be exported. If you enable these under the plot selection setting in demo visualizer, the MmwDemo_transmitProcessedOutput function in mss_main.c will export the azimuth heatmap (search for result->azimuthStaticHeatMap in the function) and the range doppler heatmap (search for detmatrix or result->detMatrix.data in the function)

    If you want to find the addresses of these, simply put a breakpoint in the function and read the values of the pointers I mentioned. These pointers are used in UART_writePolling to export the data in the same funciton. Do note that the address for the same structure would be different depending on whether it is accessed from MSS or DSS. The address in the result structure is DSS based since the DSS produces this structure. MmwDemo_transmitProcessedOutput uses SOC_translateAddress to translate this to an address usable by the MSS.

    I am wondering if that answers your question. Since the demo has built-in support to export heatmaps, couldn't you just use that? It is doing what you intend to do, just that it exports the data in TLV format.

    Regards,

    Aayush

  • 0 in reply to Aniket Mahajan
    Expert 1100 points

    Hi Jitendra and Aayush:

    It helps me a lot.

    Thank you,

    Claudio