• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 317 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.

IWR6843ISK-ODS: What happens if I turn off tracking engine by using trackingCfg?

Victoria Rudakova
Intellectual 770 points
Part Number: IWR6843ISK-ODS

Hello TI team,

I am looking at the overhead people counting lab of the latest version 4.4.1. I was curious if I could turn off the tracking engine completely (let's say the tracking and classification is done externally). 

1. How do I do it correctly? I tried to use "trackingCfg 0 2 800 20 37 33 120" - in this case it seems like something goes wrong and no data is coming, but maybe I am doing something wrong? I also tried to use "trackingCfg 1 2 1 20 37 33 120" - simply to restrict the number of acceptable points, it all works and no tracking is being performed, but I wonder if the tracking engine is still being allocated?

2. Assuming the tracking engine is not running through the Firmware, does it mean certain resources are now free (e.g., memory and processing power) and I could maybe tune the chirp config in a way so that it requires more memory/processing time; or perform some other functions? Is there any way to calculate how much of the resources is freed if the tracking engine is not used?

Best regards,

Victoria

  • 0
    TI__Mastermind 30405 points

    Hi Victoria,

    1. We have not tested disabling the trackingEnabled flag so it's possible it might have some issues as you discovered. Now, you changed the total number of points which seems to be a working alternative and I would suggest you to also reduce the max number of tracks argument (which is the next one) from 20 to 1 or even 0 so that the tracker will not allocate memory for any tracks. The tracker allocates memory based on the total number of points and tracks so changing these values will certainly reduce the memory and MIPS requirement on the MSS.

    2. However, as noted above, the tracker is running on the MSS (cortex R4F) which is not the limiting factor for the chirp configuration. The limiting factor for the chirp configuration (e.g. the number of frames per second) is the physical detection i.e. the 3D capon beamforming chain which runs on the DSP core. Due to the very high resolution capon beamfoming processing in 3D, the MIPS and memory are maxed out on the DSP core and disabling the tracker will not help with that.

    Hope it helps answer your questions.

    Regards

    -Nitin

  • 0 in reply to Nitin Sakhuja
    Intellectual 770 points

    Hello Nitin,

    Thanks for the clarifications, it makes sense.

    Regards,

    Victoria