• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 30 subscribers
  • Views 1399 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR1642: Weird behavior when loading configuration multiple times

Xinsi lin
Intellectual 530 points
Part Number: AWR1642

Hi,

Download  TI’s mmw_sdk_01_00_00_05 default mmw_demo binary into EVK,  starting  TI's visualizer app,  then go to the plot tab, use "Load Config From PC and Send" to load configuration file.

Test 1  send the "profile_2d.cfg" coming with the sdk  multiple times, you will notice that every other times there is a spike at the end of range profile in the first picture.

Test 2 : First send the "profile_2d.cfg", then send a slightly modified version of "profile_2d.cfg" which removes the line of "calibDcRangeSig 0 -5 8 256" multiple times,  Here I want to explain why remove"calibDcRangeSig 0 -5 8 256"  because we don’t reset the target so that the calibration data from the first time running "profile_2d.cfg" is still in memory and effective!  You will notice that ONLY every other times DCRangeCalib makes effect in the 2nd picture.


The question is why with the same parameters, the radar chip behave differently every other time.

Thanks,

Xinsi Lin