Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report Timing summary showing -ve slacks for tcp toe. #9

Closed
IshtiyaqueShaikh opened this issue Apr 23, 2019 · 4 comments
Closed

Report Timing summary showing -ve slacks for tcp toe. #9

IshtiyaqueShaikh opened this issue Apr 23, 2019 · 4 comments

Comments

@IshtiyaqueShaikh
Copy link

I have added timing constraint as following:
dclock=8ns
refclock=6.4ns.

Then i run synthesis and Report Timing Summary. I have observed following :
Setup:

Worst Negative Slack: -5.6ns

Hold:

Worst Hold Slack=-0.349ns

Pulse Width:

Worst Pulse Width Slack= -0.02ns

My understanding is that all above values should be positive for meeting timing constraint before running on hardware.
I do not have hardware VCU118 now but i will get in future. I want to make sure that design work on real hardware without any surprises.

Please comments/suggest.

Thanks and regards,
Ishtiyaque
ishaikh101274@gmail.com

@dsidler
Copy link
Collaborator

dsidler commented Apr 24, 2019

Are you looking at the report after synthesis or implementation?

@IshtiyaqueShaikh
Copy link
Author

I have generated timing report after synthesis.

@dsidler
Copy link
Collaborator

dsidler commented Apr 24, 2019

This is just an estimation and not accurate. Only the timing report after place and route should be considered.

@dsidler dsidler closed this as completed Apr 25, 2019
@IshtiyaqueShaikh
Copy link
Author

So we need to run timing analysis after running implementation ? Do you remember if the timing report has any slack after synthesis/implementation ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants