
ADRV9029
Recommended for New Designs
The ADRV9029 is a highly integrated, radio frequency (RF) agile transceiver offering four independently controlled transmitters, dedicated observation...
Datasheet
ADRV9029 on Analog.com

Ramarao do you have any ideas on a resolution for this? Thanks
Sorry to have missed this. What is the reference clock that you are using? What is your test setup? Which profile are you using- Default or custom one?
We are using dev clock of 122.88 MHz and sysref of 60 kHz and a custom profile which I have attached. Thanks
{
"radioCtrlInit": {
"radioCtrlModeCfg": {
"txRadioCtrlModeCfg": {
"txEnableMode": 0,
"txChannelMask": 15
},
"rxRadioCtrlModeCfg": {
"rxEnableMode": 0,
"rxChannelMask": 255
},
"orxRadioCtrlModeCfg": {
"orxEnableMode": 0,
"orxPinSelectSettlingDelay_armClkCycles": 0,
"singleChannel1PinModeOrxSel": 0,
"singleChannel2PinModeLowOrxSel": 0,
"singleChannel2PinModeHighOrxSel": 0,
"dualChannel2PinModeOrxSel": 0
}
},
"txToOrxMapping": {
"orx1Map": 2,
"orx2Map": 3,
"orx3Map": 2,
"orx4Map": 3
},
"streamGpioCfg": {
"streamGpInput0": 19,
"streamGpInput1": 19,
"streamGpInput2": 19,
"streamGpInput3": 19,
"streamGpInput4": 19,
"streamGpInput5": 19,
"streamGpInput6": 19,
"streamGpInput7": 19,
"streamGpInput8": 19,
"streamGpInput9": 19,
"streamGpInput10": 19,
"streamGpInput11": 19,
"streamGpInput12": 19,
"streamGpInput13": 19,
"streamGpInput14": 19,
"streamGpInput15": 19
},
"lo1PllFreq_Hz": 3500000000,
"lo2PllFreq_Hz": 3550000000,
"auxPllFreq_Hz": 0
},
"initCals": {
"calMask": 862207,
"channelMask": 15,
"warmBoot": 0
},
"calRsltsFile": null,
"checkFwVer": 0
}
Are you seeing this issue if you use a default profile such as 50NLS?
I have just tried 90NLS as this is the closest match to our profile, however the TX bandwidth on all of the default profiles (in the gui) are too high for an LO frequency of 80 MHz, so it is not possible to recreate the issue using a default profile
I have modified 90NLS to set the Tx synth bw to 100 MHz to match our profile and can confirm the issue still exists. It may affect different frequencies with this profile as I got the error at 79 MHz in one run
Ramarao do you have any other suggestions on things we can try?