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.
Hi Nathan,
I open this thread as continued of the question1, which is the URL below.
e2e.ti.com/.../iwr6843aopevm-cfar-ca-or-cfar-caso
My question is below.
When I used the configuration1.cfg (range CFAR is CFAR-CASO), AOP EVM works well. But incase the configuration2.cfg (range CFAR is CFAR-CA, parameters are same as doppler direction),
the detection result is strange. Not peak range bin is detected but "valley range bins". Is configuration2.cfg not correct? (the picture below is example.)
IWR6843AOPEVM
SDK3.5 pre-build binary xwr64xxAOP_mmw_demo.bin
demoVisualizer3.6
Regards,
Kei
Hi Kei,
When I run this locally, I get the following error message:
I'm running the visualizer locally with the instructions listed here.
When I run the default cfg, the objects and peaks seem to look right
Can you try it locally? We've seen some problems with the visualizer in the last few weeks that we're resolving concurrently.
Best,
Nate
Hi Nathan,
Thank you for your cooperation.
I used demo Visualizer locally, but the issue was not solved.
Regarding the error message you encountered, which pre-build binary did you use xwr68xx_mmw_demo.bin or xwr64xxAOP_mmw_demo.bin?
I guess if xwr68xx_mmw_demo.bin used, missing bpmCfg message is shown.
I am using xwr64xxAOP_mmw_demo.bin and IWR6843AOPEVM.
Regards,
Kei
Hi Kei,
I can confirm the behavior you're reporting. Please disable cyclic mode with the following change to the faulty configuration:
cfarCfg -1 0 0 4 2 3 0 15 0
Best,
Nate
Hi Nathan,
I tried disabling cyclic mode, then the fault was solved. Could you let me know why the fault was solved? Does range CFAR of xwr64xxAOP_mmw_demo.bin not support cyclic mode?
Regards,
Kei
Hi Kei,
I have confirmed with our HWA team that cyclic mode is not supported for range CFAR, only velocity. Thank you for your patience.
Best,
Nate