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.

AWR1443BOOST: rangeProfile data reading from L3 memory

Part Number: AWR1443BOOST

Hi,

I am reading rangeProfile data from L3 memory with the help of rangeDopplerLogMagMatrix pointer. But application is getting crashed after sometime.

I doubt if this is happening because of I am trying to read L3 memory which is not freshly populated. In my application, numRangeBins are 256. Is it possible that data for all these 256 bins is not present? But as I am trying to read data for all 256 bins, application is getting crashed.

Thanks & Regards,
Rajeshwari

  • Hi Rajeshwari,

    How do you capture the data rangeProfile data while device is running? To capture from CCS, halting the core and running again may cause the application to crash (ASSERT). As while pausing next frame/chirp data will be available at the memory and in the application it checks if last data is processed and sent out over the UART else ASSERT.

    If it is based on ASSERT then for this experiment you may need to disable the ASSERT to avoid application crash.

    Regards,

    Jitendra

  • Hi,

    I am reading rangeProfile data under function that is sending data over uart without pausing.

    I am using mmwave demo lab. Simply reading data, doing some operations and then sending result via CAN.

    Currently I have disabled uart sending vai CLI command. So no structure will be sent on uart.

    Everything works fine for sometime, but then all things are getting freezed. On pausing debug session, it gives message as 'no debug information available or out of program code'

    What can be the issue?

    Thanks & Regards,

    Rajeshwari

  • Hi Rajeshwari,

    As the application is much modified to fit in with your requirement, I can't predict here the cause of issue.

    L3 whole memory is available to read, even though 256 bin is not available, it won't harm reading this memory.

    You need to set some global tags at important points of application to narrow down your search of crashing point.

    Regards,

    Jitendra

  • Hi,

    Thank you very much for your help!

    I will definitely try out this.

    Regards,
    Rajeshwari