• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 338 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.

IWR6843AOP: Area Scanner Static Map

Pat Sierra
Prodigy 60 points
Part Number: IWR6843AOP

I'm having some trouble configuring the area scanner demo (using the 3.6.0.0 SDK). Specifically the heatmapGenCfg field, the default low power config file works fine out to about 3m but if I try to expand the heatmap to detect static objects over a larger range the application crashes (no output on the data UART).

I'm assuming this is a memory problem but there's no explicit error that indicates this. It looks like the heatmap used to calculate a static "background" (azimuthRangeHeatmap_record) shares memory in the L3 range with the Radar Cube so the profile configuration clearly would impact this memory. The mmWaveSensingEstimator tool provides a calculation for the memory used by the radar cube but not by the heatmap, the heatmap however should be much smaller and even if I reduce the radar cube drastically I still can't seem to expand the static heatmap, is there some hardcoded limit on this that I'm missing?

  • 0
    TI__Mastermind 19520 points

    Hello.

    Can you provide your configuration that is causing the crash so that I can try and replicate the issue on my end?  Have you tried running the demo in CCS debug to see where it might be failing?

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 60 points

    I'm using one of the default config files for the area scanner from the Radar Toolbox area_scanner_68xx_AOP_low_power_full_bandwidth.cfg
    Making any changes to heatmapGenCfg in order to extend the heatmap to other bins causes it to crash. I've also played around with other profile settings to see if that changed how big I could make the heatmap but I haven't been able to pin down a consistent trend. My understanding is that the actual range distance is (range bin * range resolution) right? 

    I have tried to build the example in CCS but I'm running into some linker issues so I can't make it build, I suspect it's a project properties problem, can you point me at a guide for running the demo in CCS debug?


    area_scanner_68xx_AOP_low_power_full_bandwidth.cfg

  • 0 in reply to Pat Sierra
    TI__Mastermind 19520 points

    Hello.

    I have included a link to our CCS debug guide here.

    Thank you for your configuration.  I will try to replicate your issue and provide an update by the end of day tomorrow.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    TI__Mastermind 19520 points

    Hello.

    I ran into the same issue you are running into, it looks like it is not able to actually start the sensor due to the memory constraints as you identified.  I believe you may have to change the address of where the heatmap is stored, as there are set addresses for the radar cube and the heatmap, and so even if you reduce the size of the radar cube, if the heatmap exceeds it bounds, it will cause the sensor to crash.  In the objectdetection.c file in the DSS, on line 2042, there is a comment detailing how the L3 range for the heatmap is set.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Prodigy 60 points

    Thank you I will look into this, unfortunately I had some trouble building the actual demo in CCS so I wasn't able to quickly test this theory. I will not be back in the office to get to this until next week at the earliest but I will follow up with how it goes.

  • 0 in reply to Pat Sierra
    TI__Mastermind 19520 points

    No problem Pat.

    Feel free to ping this thread with your update once you are back.

    Sincerely,

    Santosh