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.

IWR1642BOOST: About GtrackLib for traffic monitor

Part Number: IWR1642BOOST

Hello.

I'm looking at GtrackLib for traffic monitor, what is different from GtrackLib in SDK.
------------------------------------------------
1. GtrackLib for traffic monitor
C: \ ti \ mmwave_industrial_toolbox_2_4_0 \ labs \ lab0013_traffic_monitoring_16xx \ src \ mss \ gtrack
In case
2. GtrackLib in SDK
C: \ ti \ mmwave_sdk_ 02 _ 00 _ 00 _ 04 \ packages \ ti \ alg \ gtrack
------------------------------------------------

I do not understand the purpose of the following difference in gtrack_create.c.
I am wondering if that is a problem.

1. GtrackLib for traffic monitor

	/* allocation array holds the measurement indices of allocation set */
	inst->allocIndex = (uint16_t *) gtrack_alloc(inst->maxNumPoints, sizeof(uint16_t));
	if(inst->bestIndex == NULL) {
		*errCode = GTRACK_ENOMEM;
		goto exit;
	}

2. GtrackLib in SDK

	/* allocation array holds the measurement indices of allocation set */
	inst->allocIndex = (uint16_t *) gtrack_alloc(inst->maxNumPoints, sizeof(uint16_t));
	if(inst->allocIndex == NULL) {
		*errCode = GTRACK_ENOMEM;
		goto exit;
	}

(It differs depending on whether the target of NULL check is bestIndex or allocIndex)

Please tell me the purpose of the difference.

Thanks.

  • Former Member
    0 Former Member

    Hello Koji,

    This is a bug in the the code though functionally it should not have an affect. The correct code would be as appears in the 2. (SDK).

    Amanda