-
Notifications
You must be signed in to change notification settings - Fork 778
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
[syn] Async FIFO gray pointer timing constraints #13011
Comments
How about we add something like this? # make sure this is strict, ideally < TCK/2 where TCK is the fastest clock in the system
set MAX_DELAY 5
set SYNC_PATH u_sync_1/gen_*u_impl*/gen_flops[0]*.u_size_only_reg/Q
# for prim_fifo_async.sv
set_max_delay $MAX_DELAY -from [get_pins *] -to [get_pins sync_wptr/$SYNC_PATH]
set_max_delay $MAX_DELAY -from [get_pins *] -to [get_pins sync_rptr/$SYNC_PATH]
# for prim_fifo_async_sram_adapter.sv
set_max_delay $MAX_DELAY -from [get_pins *] -to [get_pins u_sync_wptr_gray/$SYNC_PATH]
set_max_delay $MAX_DELAY -from [get_pins *] -to [get_pins u_sync_rptr_gray/$SYNC_PATH]
|
I'd be happy to try, but in order not to miss anything, could you please write these constraints in full chip level hierarchy ? thanks |
There are many asynchronous FIFO instances in the design (especially in the crossbar). given that the registers have unique names, it would be more economical to try a wildcard for this. maybe we can dump out the list of matches so that we can review them? |
wildcards is OK, but what I'm trying to say is that the above constraints won't find any cells. For example, I found u_sync_wptr_gray in the following path |
See lowRISC#13011 for context. Signed-off-by: Michael Schaffner <[email protected]>
Oh I see. I think we need to use |
See lowRISC#13011 for context. Signed-off-by: Michael Schaffner <[email protected]>
See lowRISC#13011 for context. Signed-off-by: Michael Schaffner <[email protected]>
See lowRISC#13011 for context. Signed-off-by: Michael Schaffner <[email protected]>
Targeting for M2.5.1-RC1. This is trending 2023-05-18. |
@moidx / @msfschaffner for updates |
Currently, OpenTitan SDC does not include the Async FIFO timing constraints:
The text was updated successfully, but these errors were encountered: