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.

Recent content by npardeepsain

  1. N

    UNASSIGN definiation for cds.lib

    I am not sure if you are looking for solution now. ASSIGN is used to combine multiple libraries into one group and show in Library Manager as a single unit which can be expanded to drill down further. Once you use UNASSIGN, basically you are disabling the expanding option in library manager.
  2. N

    PDK development for GaN

    PDK is broad term. Are you talking about P-cell development?
  3. N

    Cadence: how to recover layout.oa file

    You can check with IT team if they are taking the backup.
  4. N

    Set Rule Deck Variables with Cadence PVS

    Did you check the foundry user manual? You can probably define the settings in header file including pointer to runset file. Then execute pvs deck.
  5. N

    LUP.2 DRC in TSMC 28nm Technology

    You can use some debugging setting from the foundry runset to identify the OD injector and then move those clamps cells away from the OD injectors. Please check the definition of I/O signal pad. Once you remove the Signals pad names from the design then tool will not find the OD injector and...
  6. N

    Mixed IC Design Flow Using: Synopsys DC-ICC & Cadence Virtuoso

    You have already done the stream out from Cadence as you are saying it is failing LVS when stream out from Cadence. What kind of LVS and DRC issues are you seeing?
  7. N

    How to measure Chip size using SVRF for calibre DRC

    If you are aware of SVRF (Calibre) code then you can use top level Boundary layer as input parameter, use ANGLE command to get the horizontal and vertical edges, report the length of horizontal and vertical edges either by using LENGTH > 0, this would report coordinates of failing edge and then...
  8. N

    Dummy Metal Fill Issues in MMWave IC Layout in Bi(CMOS)

    My thought: There may be impact on dummy fill on interconnect in spice extraction as it depends on which technology you are in. For older node technologies I do not think there would be any impact on having dummy metal fills in design or it can be minimal. However in case of latest technology...
  9. N

    Supply error detected when Run LVS

    Did you find solution to the problem?
  10. N

    Calibre PEX error: duplicate DMACRO definition name.

    I think there is some issue in extract.cal file that result in calling same macro two times when PEX setting is executed. Contact your foundry and report them.
  11. N

    How to turn off Calibre warnings?

    As far as I know, you can not suppress these warning message from externally. This warning message is reported because Calibre does not find the CELL NAME used in operation in your layout. If you have write access to Calibre runset, then you can add an exception in starting of Calibre. You can...
  12. N

    TLUplus files mapping, Synopsys

    Yes . these are valid. You should provide a mapping file that contains Metal name, via name .. like: conducting_layers metal1 <first metal name> metal 2 <2nd metal name> ..... <pull all the required metals under above section> via_layers via1 <first via name > via2 <2nd via name> ...
  13. N

    How to avoid latchup error?

    Refer to Technology manual for this. If you run DRC you should see fails related to latchup if your design does not meet the latch criteria. (or) read the tech manual before trying to design layout.
  14. N

    calibre drc text output

    Hello, This -hier is just to process the design hierarchy when running DRC. If you are getting text data with -hier then you can flatten the "out.gds" latter. like "FLATTEN CELL "*"" This would flatten the out.gds. Just give a try. PS.
  15. N

    Calibre drc error: failure to read input file stdin at record offset 0

    What is the error message you are getting ? Generally the error message mentioned above reports only when you have export wrong setting like in case of running rule file on gds data you have used LAYOU_SYSTEM = OASIS...

Part and Inventory Search

Back
Top