Post Go back to editing

AD9162 JESD204B Bit Inversion Conflict

Category: Hardware
Product Number: AD9162

Hi,

 

I’m using AD9162 RF DAC with Xilinx Zynq Ultrascale+ and Kintex Ultrasace FPGAs and I have question about bit inversion of AD9162. I’m using AD9162-FMC-EBZ board and I also have a custom board for AD9162. I generated my FPGA project from AD HDL Reference Design “dac_fmc_ebz” which is configured for 8 JESD204B Lanes. Then, I run start up sequence as shown in datasheet Table 42-43-44. During start up sequence, I check JESD sync status from registers 0x470 to 0x473. When I’m using AD9162-FMC-EBZ with Zynq Ultrascale+ FPGA, I get 0xFF from all status registers and I don’t have any problem about JESD link. But when I change FPGA with Kintex Ultrascale, I get 0x00 from Checksum status (Register 0x472). After I apply bit inversion from register 0x334, it is solved and JESD link works fine. I know that P/N pairs are not switched on my Kintex Ultrascale hardware.

In addition to that test, I also run the same test with my custom AD9162 board by using the same Zynq Ultrascale+ hardware. There is also a conflict in that test. When I’m using my custom AD9162 board, only 3 of 8 lanes are passed from checksum and link is not working without bit inversion. But when I apply bit inversion for 5 lanes, I also get 0xFF from checksum and JESD link works fine. I’m sure that P/N pairs are connected right for all of the boards. What could be the reason for this problem? I can work properly when I apply correct bit inversion on these boards, but I couldn’t find the main reason of this problem. Is this any reason for that conflict?

 

Thanks,

  • Hi  ,

    Thank you for using AD9162.

    Can you share which specific device and package you are using for the Zynq UltraScale+ and Kintex UltraScale FPGAs? How are the SERDES lane input pins of the AD9162 connected to the FMC connector of your custom board? Kindly refer to the EVAL-AD916x schematic for how the AD916x SERDES lanes are mapped onto the FMC connector of the evaluation board.

    Note that in the eval board, AD916x lanes 4, 5, and 7 are not connected to the corresponding physical lanes of the FMC (i.e., AD916x lane 4 is connected to physical lane 7; AD916x lane 5 is connected to physical lane 4; AD916x lane 7 is connected to physical lane 5) and that P and N are swapped for physical lanes 4 to 7.

    Regards,
    Zaeefa

  • Hi,

    Thank you for your respond. We didn't realize P and N swap on FMC connector. For ZYNQ Ultrascale+ project, we used zcu102 from analog devices example project. In that project, P and N pairs are already swapped on constraints. But for our custom board, we didn't swap them on FMC connector. Therefore, we get an error. Now, we solved why there is a conflict like that. 

    Best Regards, 

    Serkan

  • Hi  ,

    Glad to know that your issue has been resolved. Feel free to post a new thread if additional questions come up.

    Regards,
    Zaeefa