Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

xilinx timing analysis report

Status
Not open for further replies.

arishsu

Member level 3
Member level 3
Joined
Sep 10, 2013
Messages
66
Helped
6
Reputation
12
Reaction score
6
Trophy points
8
Location
India
Visit site
Activity points
422
Hi
I have simulated a multiplier verilog code on xilinx ISE and I got the synthesis report and Post PAR static timing report as shown below. Untitled2.pngUntitled.png

What is actually these terms mean? How can I calculate the total delay of the circuit?
 

What exactly do you mean by "total delay"? the timing report indicates that if you provide a 200 MHz clock, it should all work without timing related problems.
 

A timing report will list out all the timing paths in your design. It will also show whether that path is satisfying the timing requirements or not. Your job is to go through these paths and look at how you can convert failing paths to passing ones. "Total delay" is ambiguous..
 

Given the results of the timing reports you didn't give the tools any constraints at all.

Because of this you have a design that has inputs and outputs with large delays (in excess of the default clock period). You should add a constraint file with target clock frequency and input/output timing constraints.
 

I need to calculate the time delay required to calculate the output after input is given. how can I calculate that?
And what is 'Maximum output required time after clock' mean?
 

What you need is nothing to do with the timing report. You need to calculate the latency, which is easily determined from the HDL - number of pipestages * clock period.
 

What you need is nothing to do with the timing report. You need to calculate the latency, which is easily determined from the HDL - number of pipestages * clock period.

That means number of clock cycles*clock period? But in the report, the input arrival time before input(or the setup time) is more than clock period. Then how will it work?
 

But given what ADS-ee said, you dont appear to have set any constraints, so the timing report is fairly meaningless.
 

The following should help.

Here is the clock constraint:


and the input output constraint:
**broken link removed**
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top