ADRV9009 DAC (TX) output Issues

There seems to be an issue with the way the data is sent from the FPGA. Make sure that the data that you are sending has I and Q phase difference of 90 degree. With internal NCO, you will not see two tones at the output.

Refer to the below link for some example files, you can try loading  the same files :

https://wiki.analog.com/resources/eval/user-guides/ad-fmcomms2-ebz/software/basic_iq_datafiles 

Hi srimoyi ,

The issue looks to be coming from the DDS, and the way the tone is generated from the FPGA. If you dont involve our chip, and loopback TX to RX only in your FPGA, you will see similar results.

 Can you test with a modulated waveform? 

HI srimoyi ,

            Sorry for the delayed response. I plotted the DDS module output which is given to the DAC(TX) module. In the DDS output we observed only fm+LO frequency. The same DDS module when we use the ADRV9009 evaluation board then only fm+LO frequency was observed. But the same DDS module when we use custom ADRV9009 then we get fm+LO and fm-LO(image frequency) frequencies as observed in the TX output.  I also tested with modulated signal then also image frequency was observed.

Here I'm attaching the DDS module output FFT plot

Thanks and Regards

Goli Ganesh

This kind of two tone output at TX can occur if either the I or Q signal  gets dropped while the data is being sent to the chip. Check if both I and Q data is being sent from the DDS to the JESD. Make sure that the data packing is correct.

Can you try testing RX to TX loopback using the attached script? Send a tone from siggen to RX input and check if you are seeing the same tone at TX output. 

RX_TX_loopback.zip

Hi srimoyi ,

I think its clear that the issue is from the TX side . Can you please  share the TX QEC Tracking cal status using getTxQecStatus() API .

Hi vanitha ,

                    Here I'm attaching the TX QEC Tracking cal status:

Thanks and Regards

Goli Ganesh

It looks like TX QEC cal is not running , Please check if the QEC Cal is run properly .

The  iteration count and update count should be incremented as shown in the working case below .

Enable  the initial calibrations and tracking calibrations using the below API's

TALISE_runInitCals(taliseDevice_t *device, uint32_t calMask)

TALISE_enableTrackingCals(taliseDevice_t *device, uint32_t enableMask)

Please make sure that the QEC init cal and tracking cal are enabled.

Attached the script for the same .

########################
#ADI Demo Python Script
########################

#Import Reference to the DLL
import clr
import System
import time
clr.AddReferenceToFileAndPath("C:\\Program Files (x86)\\Analog Devices\\ADRV9009 Transceiver Evaluation Software_Latest17thOct2022Installed\\AdiCmdServerClient.dll")
from AdiCmdServerClient import AdiCommandServerClient
from AdiCmdServerClient import Talise
from AdiCmdServerClient import FpgaTalise
from System import Array

#Create an Instance of the Class
Link = AdiCommandServerClient.Instance

#Connect to the Zynq Platform
if(Link.hw.Connected == 1):
    Connect = 0
else:
    Connect = 1
    Link.hw.Connect("192.168.1.50", 55555)

print Link.Version()
##################################################
# Tracking Cals
##################################################
time.sleep(1)
#trackingCalMask = 0
#Link.Talise.EnableTrackingCals(0)
print "Enabled Tracking Cals After Init Cal", Link.Talise.GetEnabledTrackingCals(0)
txlol = Link.Talise.GetTxLolStatus(Link.Talise.TxChannel.Tx1)
print "Tx LOL Tracking Cals Status"
print "\tErrorCode", txlol.ErrorCode
print "\tPercentComplete", txlol.PercentComplete
print "\tVarianceMetric", txlol.VarianceMetric
print "\tIterCount", txlol.IterCount
print "\tUpdateCount", txlol.UpdateCount

#Link.Talise.EnableTrackingCals(0)
print "Enabled Tracking Cals After Init Cal", Link.Talise.GetEnabledTrackingCals(0)
#txlol = Link.Talise.GetTxQECStatus(Link.Talise.TxChannel.Tx1)
txQEC = Link.Talise.GetTxQecStatus(Link.Talise.TxChannel.Tx1)
print "Tx QEC Tracking Cals Status"
print "\tErrorCode", txQEC.ErrorCode
print "\tPercentComplete", txQEC.PercentComplete
print "\tCorrectionMetric", txQEC.CorrectionMetric
print "\tIterCount", txQEC.IterCount
print "\tUpdateCount", txQEC.UpdateCount


trackingCalMask=0
trackingCalMask |= int(Link.Talise.TrackingCalMask.Rx1Qec)
trackingCalMask |= int(Link.Talise.TrackingCalMask.Rx2Qec)
trackingCalMask |= int(Link.Talise.TrackingCalMask.ORx1Qec)
trackingCalMask |= int(Link.Talise.TrackingCalMask.Tx1Qec)
trackingCalMask |= int(Link.Talise.TrackingCalMask.Tx2Qec)
Link.Talise.GetEnabledTrackingCals(trackingCalMask)
print "Enabled Tracking Cals After Init Cal", Link.Talise.GetEnabledTrackingCals(0)
#LoopBW = Link.Talise.GetRfPllLoopFilter(0)
Z = 0
Y = 0
print "\nLoopbandwidth_KHz", Link.Talise.GetRfPllLoopFilter(Z,Y)



#Disconnect from the Zynq Platform

if(Connect == 1):
    Link.hw.Disconnect()

Hi vanitha ,

            We are using both TALISE_runInitCals(taliseDevice_t *device, uint32_t calMask) and TALISE_enableTrackingCals(taliseDevice_t *device, uint32_t enableMask) API's. The QEC init cal and tracking cal are also enabled. Still the update count and Iteration count are 0 for getTxQecStatus() in our case. What could be the reason for this ?

Thanks and Regards

Goli Ganesh

What is the initcal mask used ?

Can you please try reading back the init and tracking cals status using getInitCalStatus() and getEnabledTrackingCals() ?

What is the initcal mask used ?

Can you please try reading back the init and tracking cals status using getInitCalStatus() and getEnabledTrackingCals() ?

Hi vanitha ,

        The initCal Mask used is :

 The read back status of getEnabledTrackingCals() ,  getTxLolStatus() and getInitCalStatus()  are 

Can you please try reading back the getTxQecStatus() rather than the getTxLolStatus(). The image issue might be due to the QEC cals.

You need to get the QEC Tracking cal status as below without any error code and update count and Iteration count should be incrementing .