New Contributor
New ContributorHi Adzim,
I know that I use wildcard character, but what about the value of 10% more than the data delay of path, that means I need to use a specified value for every path, and thus, I can't use the wildcard isn't it?
I did not apply any constraint in my SDC, and I did not make any change to this part. I might have just cleaned timing on unrelated parts of the design and just relaunched the build.
So the only thing you are telling me to do at the end of the day is :
You can try to set min delay like below:
if { ! [is_post_route]} {
set_min_delay -from [get_keepers {path}] -to [path] value
}
value is 10% more than the data delay of the path.
Please see the } [IN RED] that I added to your code and tell me if I am right?
Also, am I right saying that I can't use the wildcard character because every path will need a different value value ?
Thanks
Super ContributorHi Renardo,
1. Please see the } [IN RED] that I added to your code and tell me if I am right?
- Yes you are right, and if you are unsure about the syntax, you can always use constraint menu in TA, just select any constraint and locate the node in the node finder to make sure right collection is specified, then change to your desired constraint type, e.g set_max_skew or set_min_delay for your case. This is just for the sake of verification of the nodes and tcl syntax. Let me know if you are not understand.
2. Also, am I right saying that I can't use the wildcard character because every path will need a different value value ?
- You can still use wildcards for that, in this case wildcard, the value specified will be normally used referred to the data delay of the worst negative slack path (usually the first path in column when report timing). Thus you no need to specified every path a value.
Cheers
New ContributorHi SyafieqS,
I am sorry I didn't have time to test it this week, please let me test this now and I'll tell you if anything changes
Thank you
