AWR2944: Zero detections in advanced subframe profile with fast rangeproc options

Hi Dmitry,

I have tested the same at my end but I do not observe such behaviour. You can refer to the profile configuration that I have used and test the SDK demo without any changes.

sensorStop
flushCfg
dfeDataOutputMode 3
channelCfg 15 15 0
adcCfg 2 0
adcbufCfg -1 1 0 0 1
lowPower 0 0
%
profileCfg 0 77 267 7 57.14 0 0 70 1 384 13349 0 0 158
profileCfg 1 77 250 7 57.14 0 0 60 1 192 10000 0 0 158
%
chirpCfg 0 5 0 0 0 0 0 15
chirpCfg 6 11 1 0 0 0 0 15
%
advFrameCfg 2 0 0 1 0 2
subFrameCfg 0 0 0 6 16 200 0 1 1 200
subFrameCfg 1 0 6 6 64 200 0 1 1 200
%
guiMonitor -1 2 1 0 0 0 1
%
cfarCfg 0 1 3 16 0 0 1 24.0 0 7 0 1
cfarCfg 0 0 3 16 0 0 1 15.0 0 7 0 1
cfarCfg 1 1 3 16 0 0 1 24.0 0 7 0 1
cfarCfg 1 0 3 16 0 0 1 15.0 0 7 0 1
%
compressionCfg 0 1 0 0.5 8
compressionCfg 1 1 0 0.5 8
%
intfMitigCfg 0 15 18
intfMitigCfg 1 15 18
%
localMaxCfg 0 6 40
localMaxCfg 1 6 40
%
ddmPhaseShiftAntOrder 0 2 3 1
rangeProcCfg 2 0 300 300
antGeometryCfg 1 0 1 1 1 2 1 3 0 2 0 3 0 4 0 5 1 4 1 5 1 6 1 7 1 8 1 9 1 10 1 11 0.5 0.8
antennaCalibParams 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1
measureRangeBiasAndRxChanPhase 0 1.5 0.2
analogMonitor 0 0
calibData 0 0 0x1f0000
%
aoaFovCfg -1 -90 90 -90 90
%
sensorStart

Attaching the output log for your reference - teraterm_oob_2944.log

Regards,

Samhitha

Hi Dmitry,

HWA FFT engine has a pre-processing block which performs interference localization to identify samples corrupted by interference followed by interference mitigation to repair those samples. Any sample whose magnitude and/or magnitude of backward difference exceeds thresholds THRESH_MAG<n>
and THRESH_MAGDIFF<n> is considered as affected by interference. In case of fast range processing option, Interference mitigation and interference estimation is performed in the same HWA paramset. In pre-processing stage of FFT engine, Interference Mitigation block comes first followed by Interference Statistics.

Since we perform both Interference estimation and mitigation in the same paramset, so it might happen that thresholds get decrease below a certain level. In such a case, HWA may mark non-corrupted ADC data as interference affected and mitigate it as well. To avoid this, before loading into the HWA registers, processor ensures that magThreshold and magDiffThreshold are above intfMitigMagThresMinLim and intfMitigMagDiffThresMinLim respectively. Note: intfMitigMagThresMinLim is not used in the Range processing DPU currently.

For better understanding of HWA and processing chain, refer to

• AWR294x Technical Reference Manual (Rev. D)
• C:/ti/mmwave_mcuplus_sdk_04_07_01_03/mmwave_mcuplus_sdk_04_07_01_03/docs/mmwave_sdk_module_documentation.html

These minimum threshold limits can be defined based on your experiments.

Regards,

Samhitha