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: Inquiry on Target Descriptor Buffering Mechanism (Ping/Pong) in trackerproc_3d.c (Radar Toolbox 3.10.00.05)

Part Number: IWR6843ISK


Hello TI Technical Support Team,

I am analyzing the Long Range People Detection project code, specifically within the GTRACK module of Radar Toolbox version 3.10.00.05.

1. Observation in trackerproc_3d.c: In the code, I found the following line which seems to statically initialize or reset the current target descriptor index:

trackerProcObj->targetDescrHandle->currentDescr = 0;  /*For now, use only the ping side */

2. Concern: The comment suggests that currently only the Ping side (index 0) is being used. After reviewing the related files, I could not find any subsequent code logic that modifies or toggles the trackerProcObj->targetDescrHandle->currentDescr variable (i.e., changing it from 0 to 1 or vice versa) in a typical Ping-Pong double-buffering fashion.

My Question:

  • Is the static initialization to 0 and the exclusive use of the Ping side (Descriptor 0) intentional in this specific project (LRPD 6843)?

  • If the value is updated elsewhere in the code, could you kindly point me to the relevant function or file where the currentDescr toggle occurs?

I look forward to your reply. Thank you.

Best regards, [JAEHOON KIM]