Re: [casper] ZCU 208 PPS Input

2024-03-14 Thread Mitch Burnett
Thanks, John. I am certainly not advocating using -es1. You have production silicon and the only way for the tools to accurately target the device in all aspects is to setup the tool with the correct information. We need that note and ability to support the correct device, thank you for that. I

Re: [casper] ZCU 208 PPS Input

2024-03-14 Thread John Swoboda
Hi Mitch, The -es1 removal in the yaml file was something that was brought up by colleagues of mine who have used zcu216s recently. When I did have issues with the 100 Gbe I looked into the Vivado project and found that the part number did have the -es1 tag so that's why I was suspecting that

Re: [casper] ZCU 208 PPS Input

2024-03-12 Thread Mitch Burnett
Hi John, On Mar 12, 2024, at 10:00 AM, John Swoboda wrote: Hi Mitch, Thanks for the reply. The 100 Gbe is working fine on my end. I also was able to get the into my design. Great to hear! In terms of using the -es1 in the design files, I would suggest that this be noted in the tutorials th

Re: [casper] ZCU 208 PPS Input

2024-03-12 Thread John Swoboda
Hi Mitch, Thanks for the reply. The 100 Gbe is working fine on my end. I also was able to get the into my design. In terms of using the -es1 in the design files, I would suggest that this be noted in the tutorials that this could be an issue for people if they do not have a -es1 board and the

Re: [casper] ZCU 208 PPS Input

2024-03-10 Thread Mitch Burnett
Hi John, Now I think the trick is you have to change the block parameters for the yellow block supplying the PPS to be single ended because I ran that and it got rid of my error since in the zcu208/216 use single LVCMOS18 instead of LVDS_25. Am I on the right track here? Yes, this is correct.