- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
could you please tell me as to what it means and how to get rid of it?
I have a grey code counter connected to D flip flops through some combinational logic in the path. in the report it says: -2.000 ns MKE_StMach:inst7|D1 keyStoreMem:inst2|FF1 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns MKE_StMach:inst7|D0 keyStoreMem:inst2|FF1 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns RowScanner:inst|rScan_GrCounter:inst|D0 keyStoreMem:inst2|FF1 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns RowScanner:inst|rScan_GrCounter:inst|D1 keyStoreMem:inst2|FF1 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns MKE_StMach:inst7|D1 keyStoreMem:inst2|FF2 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns MKE_StMach:inst7|D0 keyStoreMem:inst2|FF2 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns RowScanner:inst|rScan_GrCounter:inst|D0 keyStoreMem:inst2|FF2 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns RowScanner:inst|rScan_GrCounter:inst|D1 keyStoreMem:inst2|FF2 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns RowScanner:inst|rScan_GrCounter:inst|D0 keyStoreMem:inst2|FF3 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns RowScanner:inst|rScan_GrCounter:inst|D1 keyStoreMem:inst2|FF3 Clk Clk 0.000 ns 6.000 ns 4.000 ns -2.000 ns RowScanner:inst|rScan_GrCounter:inst|D0 keyStoreMem:inst2|FF4 Clk Clk 0.000 ns 6.000 ns 4.000 ns링크가 복사됨
2 응답
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Not enough info. Are you using Classic Timing Analyzer? Right-click on one of these and do a Locate Path. It will give details below. You need to figure out if:
a) The requirement is correct. (For example, a transfer within a 10ns clock domain usually has a 10ns setup requirement and a 0ns hold requirement) b) Is there significant clock skew causing it to fail timing. This is usually a result of gated clocks, and if bad enough, creates requirements that can't meet timing regardless of the datapath. c) If this is all correct, then it's something in your datapath. Is it too many levels of logic? Is it placed badly? Etc. (Those apply more to setup violations, which are the more common one.)