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.

CCS/AWR1642: Memory allocation of SRR mode and USRR mode

Part Number: AWR1642

Tool/software: Code Composer Studio

Hi Sir,

I have a question about memory allocation.

Why do the variable "trackerState" in SRR mode and "dbScanState" in USRR mode use the same memory location ?

I think that the variable "trackerState" should not be cleared.

But the memory allocation as below, the variable "trackerState" in SRR mode will be replaced by "dbScanState" in USRR mode.

Please help us to solve this problem.

Than you.

Jacki

  • Hello Jacki ,

    Have you turned ON both the "MAX_VEL_ENH_PROCESSING" and "POINT_CLOUD_PROCESSING" ? Meaning , have you set "POINT_CLOUD_PROCESSING" and "MAX_VEL_ENH_PROCESSING" to 1 ?

    -Raghu
  • Hi Raghu,
    This is the source code of the lab002 ''Short range detection" which you provided.
    "MAX_VEL_ENH_PROCESSING" is subframe 0 and "POINT_CLOUD_PROCESSING" is subframe 1 of single frame.
    From the source code, these two different mode shared the same address.
    It's meaning that the data of subframe 0 will be replaced by the data of subframe 1.
    If my aspect isn't wrong, how do the radar track the target ?
    Because the variable "trackerState" of subframe 0 will be replaced by "dbScanState" of subframe 1.

    Best regards,
    Jacki
  • Hello Jacki,

    We do not think there is any issue as the subframe processing happens in a sequence ie subframe 0 and then subframe1. There is no memory leak or memory overwriting in this case.

    The "tracekerState" is applicable to subframe 0 and then the "dbscanState" is for subframe1 as they are processed 1 after the other in a sequence , this is not an issue.

    -Raghu