Hi,
in the past, we have been using several AWR1443BOOST EVMs with ES2.0 silicon successfully (with the 1.2 mmWave SDK).
Recently we bought some additional boards, but those have the ES3.0 radar chip.
However, our parameters settings that we used successfully on the ES2.0 boards no longer seem to work on the new boards and the 2.0 mmWave SDK.
After lots of trial and error, it seems to come down to the setting of 'digOutSampleRate' in the profile configuration. According to the mmwavelink API documentation, this parameter can be set between 2000 and 37500 ksps, but with the ES3.0 boards, the accepted range seems to be reduced significantly in practice.
I can reproduce the problem with the mmWave demo application: in the profile_2d.cfg example, the digOutSampleRate is set to 4500 ksps. If I increase it, the maximum accepted value seems to be 6250 ksps. If I go beyond that, the sensor fails to start. With the ES2.0 boards, we had no problem using 10000 ksps, for instance.
Is there some constraint for the ES3.0 silicon or 2.x SDK that I'm not aware of?
I've noticed that the lowPower setting is now mandatory for the new boards and SDK, but I cannot find any other changes that could explain this limitation.
Best regards,
Eddy
