Background:
Custom board
My baremetal code resets the adrv9002 when the user wants to enable/disable dpd.
To enable dpd, a dpd-enabled profile is loaded after hardware reset (c99 files are unchanged).
To disable dpd , a dpd-disabled profile is loaded after hardware reset (c99 files are unchanged).
Both sets of c99 files were created in TES. No manual editing.
Problem description:
Before the adrv9002 hw reset, carrier frequency error is within expected tolerances. After the adrv9002 hw reset (dpd-enabled or dpd-disabled), the carrier frequency offset error is approximately 10x - 50x larger.
I have already tried putting more time in between asserting and de-asserting the adrvf9002 reset pin. That did not work.
Also, during testing, I have a uart terminal printing messages from the adrv9002. No calibration error messages are printed after the hw reset.
Request:
Could you provide any of the followng?:
- A way to enable/disable dpd using baremetal code without resetting the adrv9002 hardware
- I know the dpd tracking cal can be turned off, but I'm not referring to that.
- A way to reset the adrv9002 without suffering additional carrier frequency error
- A tested method for pushing the dpd engine to re-tune if I load a dpd-enabled profile and the resulting waveform looks bad.
