Hi everyone, When I validated my design on ROACH2, I found that there were some issues with the synchronization of the adc chip.
The environment I used was ubuntu14 ise14.7 matlab2013b mlib_devel-roach2. The parameter of my XSG_core_config module is set to ROACH2:sx475t adc0_clk 200MHz. I used david's adc16 script for initialization, and there were no errors. Use adc16_status.rb to view the adc channel and find that synchronization was not successful. adc16_init.rb: Connecting to roach7... Programming roach7 with adcsync.bof... Design built for ROACH2 rev2 with 8 ADCs (ZDOK rev2) Gateware supports demux modes (using demux by 1) Resetting ADC, power cycling ADC, and reprogramming FPGA... ZDOK0 clock OK, ZDOK1 clock OK Calibrating SERDES blocks...ABCDEFGH SERDES calibration successful. Selecting analog inputs... Using default digital gain of 1... Done! adc16_status.rb ： [observer@cylctrl bin]$ ruby adc16_status.rb roach7 roach7: Design built for ROACH2 rev2 with 8 ADCs (ZDOK rev2) roach7: Gateware supports demux modes (currently using demux by 1) roach7: ZDOK0 clock OK, ZDOK1 clock OK roach7: AAAABBBBCCCCDDDDEEEEFFFFGGGGHHHH roach7: 12341234123412341234123412341234 roach7: ................................ deskew roach7: ....XXXXXXXX........XXXX....XXXX sync May I ask which step do you think I did not set correctly, resulting in the failure of adc synchronization? Has anyone synced successfully on ROACH2 using the adc16x250-8 module? Could you please send me a copy of your mlib_devel? I suspect it is caused by the version of mlib_devel. BW！ Wang -- You received this message because you are subscribed to the Google Groups "casper@lists.berkeley.edu" group. To unsubscribe from this group and stop receiving emails from it, send an email to casper+unsubscr...@lists.berkeley.edu. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/a92b52b4-1f91-49ce-b0cf-c397332e535fn%40lists.berkeley.edu.
