I had done the timing analysis of a counter in both Synopsys DC and PrimeTime, but got the same output!! Any problem ??
Design file used is counter.v
The design compiler output is attached as DC.txt
The PrimeTime output is attached as PT.txt
Design compiler output is generated by giving input as counter.v , and clock period of 2.
PrimeTime output is generated by giving input as netlist file of counter , sdf file of counter (both generated from design compiler) and clock period of 2.
1. DC synthesizes the design into a netlist and runs timing analysis on that netlist.
2. Primetime loads the netlist produced by DC and runs timing analysis on that netlist.
You didn't change the netlist, SDF, or the default wireload models. If they didn't match then I'd be worried.
1. DC synthesizes the design into a netlist and runs timing analysis on that netlist.
2. Primetime loads the netlist produced by DC and runs timing analysis on that netlist.
You didn't change the netlist, SDF, or the default wireload models. If they didn't match then I'd be worried.
Hi gstekboy
As per my understanding both should match . As you are giving DC output netlist and sdf to PT and your constraints are also same . Since no routing or physical changes had not happened so it should not vary. Both will vary if there are any constraints mismatch or if any environment setting mismatch between them.
if you see between pnr tool and PT then PT will show you good results than pnr tool because pnr tool timing calculation is not as good as primetime. But in case of DC synthesis tool it should not vary much as it is using wireload models.
Hi gstekboy
As per my understanding both should match . As you are giving DC output netlist and sdf to PT and your constraints are also same . Since no routing or physical changes had not happened so it should not vary. Both will vary if there are any constraints mismatch or if any environment setting mismatch between them.
if you see between pnr tool and PT then PT will show you good results than pnr tool because pnr tool timing calculation is not as good as primetime. But in case of DC synthesis tool it should not vary much as it is using wireload models.
Actually in my experience the timing results for PT and DC will vary. This statement is made assuming that PT is not using SDF and uses the same wireload models as DC. I suppose they use different compute algorithms..
Actually in my experience the timing results for PT and DC will vary. This statement is made assuming that PT is not using SDF and uses the same wireload models as DC. I suppose they use different compute algorithms..
I suspect the reason should be that the module you are testing is pretty simple( a counter as I understand from your first post). Try it for a bigger and more complex block(e.g. an IP).
Hi gstekboy,
In this case then i would say as design is very small so you are not able to see the difference . try it for some bigger logic. As suggested by sarath
1. DC synthesizes the design into a netlist and runs timing analysis on that netlist.
2. Primetime loads the netlist produced by DC and runs timing analysis on that netlist.
You didn't change the netlist, SDF, or the default wireload models. If they didn't match then I'd be worried.
hi gstekboy,
I need to be cleared about your input database to PT: your netlist and SDF are exported from DC, aren't it ?
if yes, when you read them into PT, it just annotate SDF to netlist (what is DC already calculated) --> should be the same - I think.
to see difference, I think you should load netlist and SDC (which is exported from DC) into PT. then the tool will do compute, and may be bring different result.
P/S: in PT.txt , you can see character "*" --> that tell us that the value is annotated from SDF
hi gstekboy,
- I think.
to see difference, I think you should load netlist and SDC (which is exported from DC) into PT. then the tool will do compute, and may be bring different result.
P/S: in PT.txt , you can see character "*" --> that tell us that the value is annotated from SDF