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.
Typically someone would have integrated Calibre with Virtuoso so that in Virtuoso you'd use a menu, probably Calibre > Run nmDRC or Run nmLVS. These bring up the Calibre Interactive GUI so that you can specify the rule file, layout, the checks to run, and so on.
You can also run Calibre...
You will need access to the documentation, unfortunately, as that is what the "Try It" kits are classed as. Here is the link, in case you do get access (or if anyone else would like to try it):
https://docs.sw.siemens.com/en-US/product/852852053/doc/202308034.calbr_quickstart_ekit
Hi Fayiz-
This might be too late, but you can register for a free account at Siemens Support Center (https://support.sw.siemens.com/en-US/ ) and access it there. It is copyrighted material, and at least under Mentor Graphics the company would send stern letters to those who posted it on the...
You'll need a Support Center account. If you don't have one, a link won't do you any good, and if you do have one, you'll know where the downloads tab is. Support Center is https://support.sw.siemens.com/
Best-
Sam.
Yeah, older releases are tricky to get to. In Support Center from the Calibre Downloads tab, set version to "Older Versions". (It is to the left of the Filter field, above the list of current versions.)
There are four 2017.4 versions in the extensive list -- they correspond to the first...
It could also be a couple of other things -- I dug up the reference (svrf_ur.pdf) for the DECRYPT4 error. This error can also be caused by "duplicate layer names, duplicate rule names, incorrectly set environment variables, incorrect Calibre version, or mismatches in the number of arguments...
Hi Leo-
The message says that the rule file was written for a different version of Calibre than you are using. Foundries can choose to make this an error or a warning; looks like they went with error. The only way to get past this is to use the same version of Calibre that the rule file was...
For LVS to figure out a netlist, it needs to know how devices are connected. As Dick mentioned, that's normally in the rules that the runset runs.
Two key statements are "Device" and "Connect". The first one tells Calibre how to tell what combination of layers with interacting shapes is a...
At a guess, check the rule file for "PEX NETLIST SPEF PRIMETIME." The information in the SVRF manual says that the PRIMETIME keyword (among other things) outputs keywords and element names in all uppercase. You might try adding "PEX NETLIST UPPERCASE KEYWORDS NO" to your file if you are using a...
That can happen if the background and layer use the same value -- they should be opposites. (In the simplest case, a dark/clear pair.) What are the lines for the "background" keyword and the "layer" keyword in the setup file? (Not the SVRF part, but the ones with the setlayer commands...
If you can describe geometrically where you want the SRAFs, you could try OPCSBAR, which doesn't use models. The instructions for it are in the Calibre OPCsbar User's and Reference Manual. (calbr_sbar_useref.pdf in your Calibre installation)
Alternatively, it isn't that hard to turn models...
The SVDB directory is created by Calibre -- because you are running QRC rather than xRC or xACT, it won't have the parasitic files (.pex.netlist, .pxi).
It probably is not a good idea to have multiple people running from the same directory -- there will be filename collisions unless you are careful, and quite possibly issues with space, depending on the size of the input.
That said, if you really want to do it, create a runset with the settings...
Sounds like the rule file has a DRC rule, OD.DN.3, that is turning up some violations of a PDK rule. From the rest of the headline, it has something to do with density on "All_OD" (is that a layer?) in a 20 micron by 20 micron region. The rule has the regions being stepped a half-region each...
Hi Pujan-
Assuming this doesn't happen in a clean directory, the workaround is to delete the query_results file.
(Notice the banner says "This software is in pre-production form and is considered to be beta"? If you can update to a release that isn't pre-production, you'll want 2019.2 or...
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.
