• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. How forcing assura QRC to keep analogLib device from schematic...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 14693
  • 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
ogiard over 14 years ago

 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 

  • Cancel
  • Quek
    Quek over 14 years ago

    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

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 14 years ago

    Hi Olivier

    That was a really good description of the problem. Thank you. : )  Providing the tool versions definitely helps a lot in understanding and solving the problem.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ogiard
    ogiard over 14 years ago

    Hi Quek,
     
    The last solution you propose with adding pin on layout/schematic  is the idea I have in mind at the beginning and certainly the more simple to implement. I keep it if I don’t find anything more simple for common users.

    The solution you propose with the callProc.il procedure is something I prefer because it is more “transparent” for user and I can manage it with the global project control skill codes for any type of extracted. In that way, I did experiment at the beginning of my investigations  to add manually wanted device in the extracted view  with a copy/paste from schematic to extracted view (including wire connections). This is what your code does nicely (thanks for this). Devices are present in the .scs netlist (great!) but without any connection (Bad!) because connectivity properties of devices have value=nil.

    I never used skill for connecting device pin to  net. I will try to find some example on source link or other cadence helps.

    Maybe I can copy/past property cons & instTerms from schematic to extracted ?
     
    Best regards.
     
    Olivier

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ogiard
    ogiard over 14 years ago

     Hi Quek,

     

    Now I can copy my devices in the layout extracted view correctly.

    But I can't connect correctly the terminals of the device to wanted net. I found a function named dbCreateConn in the skill doc, but I did not found enough documentation on it. I did try to copy the ~>conns section of the schematic into the device of the extracted, but it does not work.

    Do you have an idea on how I can put the connectivity properties of my extracted view devices?

     

    Thanks

     

    Best regards

    Olivier


    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 13 years ago

    Hi Olivier

    Sorry for the late reply. I have been busy. : )

    You can use dbMakeNet and dbCreateConnByName to create connectivity. The following script will add all schematic vsource instances to the extracted view and copy the properties and connectivities.

    Best regards
    Quek


    procedure( avExtractedCellViewCallProc(cv)
       let( (cvSch myNet x vInst)
          cvSch=dbOpenCellViewByType(cv~>libName cv~>cellName "schematic")
          x=0
          foreach(inst cvSch~>instances
             case(inst~>cellName
                ("vsource"
                   vInst=dbCreateInst(cv inst~>master inst~>name x:0 "R0")
               vInst~>srcType=inst~>srcType
               vInst~>vdc=inst~>vdc
                   foreach( term inst~>instTerms
                      myNet=dbMakeNet(cv term~>net~>name)
                      dbCreateConnByName(myNet vInst term~>name)
                   ) ;foreach
               x++
                   printf("Created 1 vsource in extracted view\n")
                ) ;vsource
                ("Others" printf("Do something\n"))
             ) ;cond
          ) ;foreach
       ) ;let
    ) ;procedure

    createinst.il
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ogiard
    ogiard over 13 years ago

    Hi Quek,

    Thanks

    This command looks great for my skill.

    I‘ll try to update my skill soon. I’m also quite busy with other design issues.

    I’ll keep you informed

    Best regards / Cordialement

    Olivier GIARD

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information