Other Parts Discussed in Thread: AWR2944
Tool/software:
Hi,
can I run a tracker for 2944 based on this configuration example: Tracker Tuning Guide
If not, how to do that?
Arie
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.
Tool/software:
Hi,
can I run a tracker for 2944 based on this configuration example: Tracker Tuning Guide
If not, how to do that?
Arie
For some reason the link doesn't open, resending it: Tracker Tuning Guide
Hello Arie,
For the the 2944 I would reference this document in the SDK
"C:\ti\mmwave_mcuplus_sdk_04_07_01_03\mmwave_mcuplus_sdk_04_07_01_03\ti\alg\gtrack\docs\Tracking radar targets with multiple reflection points.pdf"
It specifies the steps needed to utilize the tracker.
Best,
Gabriel
Thank you for the document. I will learn it.
Meanwhile, generally speaking, is the control over tracker performed via .cfg file? If yes, where can I see an example of configuration, suitable for 2944?
Hello,
Yes the .cfg is what controls the tracker, but currently there is not a typical .cfg tracker example. Tracker is utilized in the High End Corner Radar demo in the radar toolbox. You can then get some example parameter by observing the code. There is MmwDemo_loadGtrackCfg() in mmw_load_params.c that shows what is used for the tracker parameters. You can then just observe these define values and use them in your own configuration.
You might have to play around with some parameters for your use case but this should be a good starting example.
Best,
Gabriel
Do I understand correctly that in order to utilize the tracker with my configuration, I actually need to compile the HECR code into executable FW with my parameters, load it into EVM using a FW loader and only then will be able to observe the tracker in the visualizer?
No, you dont have to build anything with the HECR demo. This just has an example configuration. The PDF I shared specifies all the steps you need to do. To use the tracker you first need to include the library in your custom build. Then you can add parameters in your .cfg as specified in the pdf shared. Here is the example
Recommended values for Traffic monitoring (TM) and People counting (PC) use cases are given as an example.
Or yes you can just use the HECR as your application and tweak the parameters as needed. Then you can visualize with the automotive visualizer present in the radar toolbox
C:\ti\radar_toolbox_3_10_00_05\tools\visualizers\Automotive_Visualiser
Best,
Gabriel
I don't have currently a custom build. I used precompiled OOB project, which as I understand doesn't include a tracker in it. I took binaries from:
C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\ti\demo\awr294x\mmw\awr2944_mmw_demoTDM.appimage
and
C:\ti\mmwave_mcuplus_sdk_04_07_00_01\mmwave_mcuplus_sdk_04_07_00_01\tools\awr294x\sbl_qspi.release.tiimage
I see, in that case I recommend just using the HECR for the 2944. It utilizes tracking.
Then you can visualize with the automotive visualizer present in the radar toolbox
C:\ti\radar_toolbox_3_10_00_05\tools\visualizers\Automotive_Visualiser
Best,
Gabriel
The problem with that is that I don't understand how I open the project in CCS. I accessed C:\ti\radar_toolbox_3_10_00_05\source\ti\examples\Automotive_ADAS_and_Parking\high_end_corner_radar\src\demo\awr2944\ but there is only .project file which could not be opened in CCS and no .projectspec files as I would expect. What should I do please?
Ok so there are two options here.
- There is not a working projectspec for the HECR in the current RTB. But there is a working projectspec that is to be released in the next RTB release (RTB 3.20). You can wait for this release which is planned for next week.
- Or you can build the demo from makefile (all present in the HECR demo) and then use the core images or app images for testing.
Best,
Gabriel