If you look at the ADRV9025 Manual, DPD Mode has API and Pin Mode.
TDD requires the use of pin mode.
I wonder why I should use Pin Mode instead of API Mode in TDD.
Please give a detailed explanation as to why.
thank you
If you look at the ADRV9025 Manual, DPD Mode has API and Pin Mode.
TDD requires the use of pin mode.
I wonder why I should use Pin Mode instead of API Mode in TDD.
Please give a detailed explanation as to why.
thank you
In SPI mode, signal path control relies on register access and its inherent unpredictable timings. For critical timing alignments when powering ON and OFF signal chains incase of TDD mode pin control mode is recommended.
See below snippet from UG. In case of API mode, we would have predictable timing issues due to SPI register access. In case of PIN mode, we use TX/ RX/ ORX Stream processors directly controlled to enable/ disable the channels where there wont be any delay. If you use API mode in case of TDD mode, you might miss the data due to incorrect timing.
By any chance, if you use APi mode in a TDD system using DPD 4-ORX, can DPD not work?
DPD can be enabled in API mode as well, you have to enable and disable Tx/Rx/Orx using adi_adrv9025_RxTxEnableSet() API according to your TDD timings.
Currently, DPD is operating in APi Mode, but sometimes (or often) DPD does not operate.
Can you provide more details of the issue?.As replied earlier it is recommended to use pin mode in TDD mode. what is your requirement to use API mode?