Stats

  • Locked Locked
  • Replies 6
  • Subscribers 130
  • Views 15539
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How forcing assura QRC to keep analogLib device from schematic to extracted view ?

ogiard

 Hello,

I try to build a simulation flow to improve top simulation of our design with assura QRC  extracted RC view.

Currently in schematic view we have some analogLib devices to help DC convergence, such as sp1tswitch, bsource or vdc for example.

Those devices have of course the property lvsIgnore=TRUE for LVS compatibility.

The problem is that such devices are not reported in assura QRC extracted view also.

Today we add manually convergence  devices in .scs netlist before simulation, but this is not really helpful with simulation flow using ADE, and we sometime forget to update convergence device when new extracted view is built.

 

I did try the solution to add such device in the extracted view by using some skill, but I did not succeed. This method need better skill knowledge and time that I do not have.

Is it possible to program assura QRC in order to report such analogLib device directly in the extracted view ? (and keep the property lvsIgnore=TRUE of course)

 

Thanks in advance

 

Olivier

 

Notes; my software version:

cadence_ic                      5.10.41.500.6.137

cadence_assura                  3.2_USR1_51    

cadence_ext                     9.1.4-p001_HF1 

Parents
  • Quek

    Hi Olivier

    It might be possible to do it using "callProc.il" file but actually it would be wrong to do so becaues those kind of instances are not meant to appear in an extracted view. : )  "callProc.il" is a skillscript which can be placed in the QRC tech directory so that QRC can read and execute it when generating the extracted view. This file can also be specified in "Setup" tab of the QRC form. Here is an example of a callProc.il file:

    procedure( avExtractedCellViewCallProc(cvLay)
       let( (cvSch x)
          cvSch=dbOpenCellViewByType(cvLay~>libName cvLay~>cellName "schematic")
          x=0
          foreach( schInst cvSch~>instances
             when( schInst~>cellName=="vsource"
                layInst=dbCreateInstByMasterName(cvLay "analogLib" "vsource" "symbol" schInst~>name x:0 "R0" 1)
                x=x+10
             ) ;when
          ) ;foreach
       ) ;let
    ) ;procedure


    The above procedure will search the schematic for "vsource" instances and add a corresponding vsource to the layout. It is still incomplete as the properties and net names of the instance need to be copied over too. The coordinates of the instance would also need to be modified for each instance. I think it would still take some effort to complete it.

    The correct approach to solving this problem is to replace all schematic connections to the vsource, switches with pins and remove those instances. Add the same pins in the layout. Create a symbol for the schematic, instantiate it in a test schematic and then connect vsource, etc to the original schematic through the pins. : )

    Best regards
    Quek

Reply
  • Quek

    Hi Olivier

    It might be possible to do it using "callProc.il" file but actually it would be wrong to do so becaues those kind of instances are not meant to appear in an extracted view. : )  "callProc.il" is a skillscript which can be placed in the QRC tech directory so that QRC can read and execute it when generating the extracted view. This file can also be specified in "Setup" tab of the QRC form. Here is an example of a callProc.il file:

    procedure( avExtractedCellViewCallProc(cvLay)
       let( (cvSch x)
          cvSch=dbOpenCellViewByType(cvLay~>libName cvLay~>cellName "schematic")
          x=0
          foreach( schInst cvSch~>instances
             when( schInst~>cellName=="vsource"
                layInst=dbCreateInstByMasterName(cvLay "analogLib" "vsource" "symbol" schInst~>name x:0 "R0" 1)
                x=x+10
             ) ;when
          ) ;foreach
       ) ;let
    ) ;procedure


    The above procedure will search the schematic for "vsource" instances and add a corresponding vsource to the layout. It is still incomplete as the properties and net names of the instance need to be copied over too. The coordinates of the instance would also need to be modified for each instance. I think it would still take some effort to complete it.

    The correct approach to solving this problem is to replace all schematic connections to the vsource, switches with pins and remove those instances. Add the same pins in the layout. Create a symbol for the schematic, instantiate it in a test schematic and then connect vsource, etc to the original schematic through the pins. : )

    Best regards
    Quek

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.