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.

IWR1443: IWR1443

Part Number: IWR1443
Other Parts Discussed in Thread: AWR1843

I am developing a radar board using IWR1443 radar chip with the out-of-box demo code. Everything is working fine with the out-of-box demo code. I then add the group tracking algorithm in the main code. The final code size is around 160K and it cannot not be compiled. 

I then take out some of the unused modules in OOB and shrink the program code. I could incorporate the group tracking algorithm (~\mmwave_sdk_02_01_00_04\packages\ti\alg\gtrack) into the OOB within 128K. However, the code stop at the first line of code in the gtack as shown below. This statement eventually will call the Memory_alloc() function which will involve the heap memory. Just wonder if the heap used by the gtrack is the same as the heap assigned for the radar L3_ram. Do I have to assign a different heap for gtrack?

Also want to know if there is demo code other than the OOB which incorporates the gtrack algorithm already.

Thanks,

Henry

  • Henry:

    I am closing the original thread that you posted. I am providing some other labs that use gtrack. Although gtrack is only used on 68xx devices which have significantly less RAM. Also I would caution against removing parts of the OOB unless you know exactly the consequences of doing such. I would suggest getting a 68xx device, or incorporate more RAM into you system. The amount of RAM may very well be too little for your application.

    People Counting Demo for gtrack example.

    C:\ti\mmwave_industrial_toolbox_4_5_1\labs\people_counting\68xx_3D_people_counting\docs\3d_pplcount_user_guide.html

    Best,

    Connor Desmond

  • Hi Connor,

    I am switching to AWR1843 device. Do you know if it is easy to port gtrack into it?

    Thanks a lot,

    Henry

  • Henry:

    From my understanding there will be considerable amount of work involved. Fortunately, we have labs for the XWR18xx devices which have the gtrack algorithm implemented already. These labs are built from the code that makes the OOB, so you can use that as a baseline or reference for your application.

    Best regards,

    Connor Desmond