04-10-2020 05:01 PM
From this post:
I understand that virtual clocks are used in order to correctly use exception when constraining Double Data rate interfaces - there're practically a must in that situation.
However I've also seen them used for constraining SDR interfaces where no such exceptions are required.
So why use them ?
What's the benefit of using virtual clocks when constraining SDR interfaces ?
04-12-2020 11:41 PM
I don't think virtual clock is a must when constrainting the SDR or DDR interface.
Using virtual clock is one of the methods of I/O constraints.
For me, I prefer the method given in Vivado language template.
It sorts the templates based on the types of the interfaces.
Once you match your design interface with one of the templates, you can use the constraint examples in the template directly.
04-13-2020 01:50 AM
Could be a relatively natrual thingking of adding constraints for the I/O interface, since the launching clock in input delay and capturing clock in output delay are clocks that do not exist in the current design.
Just my two cents.
04-13-2020 03:53 AM
Can someone please add more information on this ?
When dealing with SDR interfaces - What are the benefits of using a virtual clock as reference opposed to the real clock ?