Quantcast
Channel: Altera Forums
Viewing all articles
Browse latest Browse all 19390

Recovery timing violation

$
0
0
Hi all,

I have a design with major recovery timing violation (among others).

The design wasn't written by me, I'm only editing it, so I'm not fully aware of everything inside it.

There's a photo in the attachment with screenshots from timequest with the worst failing recovery path.

I'm unable to grasp where is the ~7000 ns latch edge time in the data required path coming from???

Launch clock is 24 MHz, latch clock is 200 MHz.

I tried putting the reset signal to global resources, but quartus just ignores this assignment.
I'm working in quartus 17.1. I tried using the following assignment:
Code:

set_instance_assignment -name GLOBAL_SIGNAL ON -to "h158_core:u0|h158_core_mem_if_ddr3_emif_0:mem_if_ddr3_emif_0|h158_core_mem_if_ddr3_emif_0_p0:p0|h158_core_mem_if_ddr3_emif_0_p0_memphy:umemphy|h158_core_mem_if_ddr3_emif_0_p0_reset:ureset|h158_core_mem_if_ddr3_emif_0_p0_reset_sync:ureset_afi_clk|reset_reg[15]";
Any help would be appreciated as I'm stuck and have no idea what to do next.

Thanks for your help!
Attached Images

Viewing all articles
Browse latest Browse all 19390

Trending Articles