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.
Hi all,
Can any one tell me which constraints written out by DC, like set_clock_latency/ set_clock_transition/ set_clock_uncertainty, will affect the clock spec generation in CTS stage?
The generated Clock.ctstch looks like below:
AutoCTSRootPin clkgen_m/u6/Z
Period 40ns...
Hi friends,
This is confusing to me. The definition of self-clocking means the clock infomation is embedded in the data transmission.
From this view I2C is not self-clocked as there's a clock SCL running alongside the data.
But recently I've read "self-clocked I2C" in the functional block in a...
Hi friends!
In the timingReports directory there's **_postRoute.slk, and in this slk file it looks like below:
# Format: clock timeReq slackR/slackF setupR/setupF instName/pinName # cycle(s)
exck_i(R)->exck_i(R) 15.000 8.153/* 5.000/* ex_rd_o 1...
Dear all,
Is it possible to synthesize & verify a RTL latch-based design using DC? Or for latch-based designs, there're methodologies rather than DC?
I know there's a way to create two non-overlapping clocks using create_clock, but not sure if DC/PT can verify the timing after PR, that the...
Hi matter,
But I think DC has got the wrong hold relationship, It should not check the hold on 0ns of the launch edge, it should have been check the next rising edge, that is 20ns.
20+0.108-10=10.108.
The question is how can I put constaints to let DC check the correct hold relationship?
I have a design that has to used both rising and falling edges of a clock, to improve the holdtime margin. But I found DC has problem when doing timing analyze.
The hold time report looks like below. The clock period is 20ns, and I think the correct hold time slack should be 10ns+0.108=...
I've checked the .synopsys_dc.setup file, even the variable view_command_log_file is set, DC does not create the file name specified.
Is that bacause "view_command_log_file" is only in effect in Design Analyzer, and not avaiable to dc_shell-t or Design Vision?
I'm working with DC2007.03, today I've found that the eco_align_design is a "unknown command". But I still could set the variables eco_instance_name_prefix, compile_instance_name_prefix.
Does anyone knows from what version on, Synopsys begins not to support ECO compiler? And why?
Thanks in advance!
As this is for test purpose only, I haven't put any constraint on it.
read_verilog mul16x16.v
current_design mul16x16
compile
pipeline_design -stages 3 -clock clk -asyn rst
write_file -f verilog -h -o mul16x16.vg
Oops...The code was in my home computer...I will attach them tomorrow.
To answer your questions, the RTL is purely combinational, but as it's retimed by pipeline_design, the gate netlist has comb+ seq. Design Compiler was used for logic synthess.
Hi all,
It's a simple 16x16 multiplier and it's used for test only. After first compile I used the command pipeline_design to retime that mul.
And a default.svf was created. In formality environment, I imported the svf file and rtl, db library, and gate netlist, and set top module...
Hi everyone,
I am fresh to SOC ECO and need help on it. Thanks!
The chip has been taped-out and after some tests bugs are found. I’ve modified the verilog netlist using several spare cells. The changes are like below:
TOP module originally has instance of module A and module B, now signals...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.