AnsweredAssumed Answered

AD9371 No-OS deframer errors

Question asked by Newy on Feb 1, 2018
Latest reply on Feb 16, 2018 by Newy

We've been working with the AD9371 No-OS reference design and have been able to successfully take a signal on the
receive port, delay it, and send it out the transmitter port.  Through this development, I've been getting deframer errors.
Typically DeframerStatus=0x61 about 10% of the time, and DeframerStatus=0x60 about 70% of the time.  The 0x61s seem to be fatal, things seem to work normally even with the 0x60s.  I've been living with these and just rebooting from SDK until it works, but now I'm at the point that I need to get this resolved.

 

I've gone back to basics and get these errors even with unmodified reference design code.  There are a few related posts in EZ, but they had no resolution.

 

I have 2 Zynq boards and 3 AD9371 boards and all combinations seem to work the same. 

 

Clocks:

RX=TX=ORX=122.88 MSPS
SRX=30.72MSPS

TES JESD settings:

RxFramer:
LaneRate=4915.2
L=2
K=32
M=4
F=4

 

TXdeframer:
Lanerate=2457.6
L=4
K=32
M=4
F=2

 

ORXFramer:
LaneRate=2457.6
L=2
K=32
M=2
F=2

 

Scrambling Checked for all
Relink on Sysref checked for all
Use External sysref checked

 

typical output----


Please wait...
MCS successful
CLKPLL locked
AD9371 ARM version 5.1.1
PLLs locked
Calibrations completed successfully
RX_XCVR initialization OK
TX_XCVR initialization OK
RX_OS_XCVR initialization OK
DeframerStatus = 0x60
dac_setup dac core initialized (122 MHz).
adc_setup adc core initialized (123 MHz).
Done

Anything obvious I'm doing wrong?

Outcomes