(1) In the version AWRL1432_ADAS_BSD_DEMO v4.1 code, I noticed that the calculation of gMmwMssMCB.numRangeBins as the following line:
This multiplication by 0.90f was not present in version 3.2. It seems to be an intentional change by TI, but it results in a 1.1 times increase in the subsequent calculation of rangeStep, which in turn causes the reported target distance to be 1.1x larger. Could you please explain the purpose of this 0.90f? Is it for the purpose of decreasing memory usage? BTW, the tlv type = 302 for rangeProfile output data also has a mismatch like length = 116 (128 points * 0.90 = 116 points) and still output data value = 128*4bytes.
(2) During practical testing with version 4.1, I observed that at very close range, one or two persistent target points consistently appear. These seem to originate from DC leakage in the rangeProfile. When configuring rangeSelCfg via CLI, setting argument 1 (minMeters) too large causes the CFAR DPU to fail, while setting it too small does not remove the persistent close-range points. Could you clarify if there are any limitations or recommended guidelines for tackling these persistent targets?
