You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using an externally generated serial clock the -source constraint added by the core seems to assume that serial clock is directly generated by the pixel clock, which doesn't make much sense (if anything it would be vice versa via a BUFR, but that is not always the case either). This causes several critical warnings and seems to confuse the clocking analysis.
Unless this constraint is serving some purpose, I think it should be removed. The clock generation should be handled by the upstream core that actually generates the clocks.
The text was updated successfully, but these errors were encountered:
When using an externally generated serial clock the -source constraint added by the core seems to assume that serial clock is directly generated by the pixel clock, which doesn't make much sense (if anything it would be vice versa via a BUFR, but that is not always the case either). This causes several critical warnings and seems to confuse the clocking analysis.
Unless this constraint is serving some purpose, I think it should be removed. The clock generation should be handled by the upstream core that actually generates the clocks.
The text was updated successfully, but these errors were encountered: