Other Parts Discussed in Thread: AWR2944
Tool/software:
Hi,
Would you pls provide a demo or sample setting of Interference Mitigation block in HWA?
I can't find any example for Interference Mitigation block in HWA in SDK.
Thanks,
Chris
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.
Hey Chris,
Unfortunately, we don't have demo code for the interference mitigation block in the HWA. Instead, I would recommend looking over Sections 10.2.1.2 Interference Mitigation and 10.2.1.2.2 Interference Statistics from the xWRL432 TRM which does a good job outlining the main factors of the interference mitigation block. The INTF_THRESH_EN, THRESH_MAG/THRESH_MAGDIFF, and INTF_ZERO_MODE are mapped to the fields of the interfLocalize struct and INTF_STATS_RESET_MODE is mapped to interfStat struct - both under <MMWAVE_LSDK_INSTALL_DIR>/source/drivers/hwa/v0/hwa.h. These structs are accessible through the preProcCfg struct of the paramConfig passed using HWA_configParamSet.
Regards,
Kristien
Kristine,
Does TI has plan to make an demo to use HWA interference feature? If yes, when it will be ready?
Thanks,
Chris
Hey Chris,
There are currently no plans to make a demo that uses the HWA interference feature for low-power devices. The OOB demo for AWR2944 does use an HWA interference block, but its configuration differs compared to the HWA interference block used by low-power devices. As a reference, the following interference configuration is used in the OOB demo for AWR2944, but please note this may not work as intended on low-power devices.
preProcCfg.interfLocalize.thresholdEnable = HWA_INTERFERENCE_ENABLE
preProcCfg.interfLocalize.thresholdMode = HWA_INTERFERENCE_THRESH_MODE_MAGDIFF
preProcCfg.interfLocalize.thresholdSelect = HWA_INTERFERENCE_THRESH_SELECT_BUILTINpreProcCfg.interfStat.resetMode = HWA_INTERFERENCE_STATS_RESET_HOLD
Regards,
Kristien
Hi Kristien,
Regarding the register position of these values of 1432 anti-interference, can you give a similar reference to 2944, which can be easily modified at the bottom. At present, we see that the HWA document has a register description, but it cannot correspond to the code (or could you tell how to correspond to the code modification).
The relevant screen pictures are as follow:
Best,
Yitong.
Hey Jin,
The HWA_PreProcessing struct may need to be updated for xWRL1432. I need to confirm with the design team whether this block/driver should be the same between xWR2944 and xWRL1432.
Regards,
Kristien
Hi Kristien,
Thanks a lot. Could you please help ask when the design team can give us a reply? Will their SDK update this feature?
Best,
Yitong.
Hey Jin,
I've already reached out to the relevant design team members and SDK members. I will update you once I get a reply back from them.
Thank you for your patience,
Kristien
Hey Jin,
I'm still waiting on a response from the SDK team, but according to the design team, xWR2944 and xWRL1432 use two different HWA IP versions, HWA2.1 and HWA1.2 respectively, that support different mitigation methods. HWA1.2 only supports zero-out mitigation while HWA 2.1 supports additional methods such as window zero-out and linear interpolation.
Regards,
Kristien
Hi Kristien,
Yes, we have noticed this difference, and hope for the response from the SDK team.
Best,
Yitong.
Hi,
Just wanted to follow up to let you know we'll post when we have more feedback.
Thanks,
Clinton
Hey Jin,
I have confirmed with the SDK team that the interfMitigation struct in the MMWAVE L-SDK is not needed and should not be used for xWRL1432. This will be removed in a future version. Please test the parameters previously shared, and let us know if there are any issues.
Regards,
Kristien
Hi Kristien,
Excuse me, we would like to further confirm (1) the parameters previously shared you mentioned, are the items in the above reply (as shown in screenshot)? But we can’t find these structs in 1432.
(2) how to test the parameters previously shared.
Best,
Yitong.
Hey Jin,
If you are referring to the interfMitigation struct, then there should be no struct for 1432 needed. If you are referring to the interfLocalize and interfStat structs, then these are needed to utilize interference mitigation.
For testing the parameters previously shared, since there is no example code, this will be up to the end user to test and implement for the time being. However, one potential area to start would be to add interference mitigation into the FFT portion of the HWA range processing chain - i.e., adding interfLocalize and interfStat to the range FFT portion of rangeProcHWA_ConfigHWA under <MMWAVE_LSDK_INSTALL_DIR>/source/datapath/dpu/rangeproc/v0/rangeprochwa.c.
Finally, could you tell us what end application you intend to use interference mitigation in? Depending on your answer, I might be able to find someone who can comment more on this issue.
Regards,
Kristien
Hi Kristien,
We notice that HWA_configParamSet can only support configuration of these three variables as shown below, does it mean that the interference can only match these few, which cannot be configured as the documentation says.Or are there any new documents to update to us.
Best,
Yitong.
Hey Jin,
The interference mitigation parameter configuration only requires those three parameters for setup. As mentioned before, the values for these fields and what they do can be found under Sections 10.2.1.2 Interference Mitigation and 10.2.1.2.2 Interference Statistics from the xWRL432 TRM. You can also look at the typedef struct defined under <MMWAVE_LSDK_INSTALL_DIR>/source/drivers/hwa/v0/hwa.h and look for HWA_INTERFERENCE macros near the top of the same file.
Regards,
Kristien
Hi Kristien,
The above registers are also masked in MMWAVE_L_SDK_05_03_00_02. Does it indicate that this SDK does not support anti-jamming and needs to be upgraded to MMWAVE_L_SDK_05_05_00_02, as shown below:
Best,
Yitong.
Hey Jin,
I'm not sure what anti-jamming is in this context, but as stated before, the interfLocalize struct is used for interference mitigation. If possible, could you clarify what "anti-jamming" is?
Regards,
Kristien
Hi Kristien,
Sorry for the lack of clarity, "anti-jamming" is represented for interference mitigation.
The above registers are also masked in MMWAVE_L_SDK_05_03_00_02, which are commented out. Does it indicate that SDK 5.3 does not support interference mitigation and needs to be upgraded to MMWAVE_L_SDK_05_05_00_02, as shown below:
Could we use these interfLocalize structs used for interference mitigation in SDK 5.3 as well?
Best,
Yitong.
Hey Jin,
You should always use the latest software version when possible, so please update to 5.5.0.2 if you haven't already. Complete driver support of the interference mitigation block was finished in 5.4.0.1, hence why it is excluded from 5.3.0.2.
Regards,
Kristien