Stats

  • Locked Locked
  • Replies 10
  • Subscribers 127
  • Views 16829
  • 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

Need a quick explanation for back annotating parasitics in IC6.1.4

bnugent

Hi folks,

 

 

I am currently working on properly back annotating parasitics from the av_analog_extracted view onto the schematic for convenience. But does anyone have any quick tips on how to do this?
 
I am using IC6.1.4, Assura  4.12, and QRC 9.14.
 
Thanks

 

Parents

  • Hi bnugent

    You can refer to $CDSHOME/doc/parasim/parasim.pdf. The manual explains specifically about post layout simulation and backanotation.

    1. Create schematic
    2. Create test-bench using schematic
    3. Create config view for test-bench
    4. Create layout
    5. Run Assura LVS
    6. Run QRC parasitic extraction to generate extracted view
    7. Open up config view and switch to extracted view
    8. Open up test-bench from config view
    9. Run spectre simulation
    10. Descend into the subcell schematic from the test-bench schematic
    11. Display parasitics menu from "Launch" menu
    12. Set up parasitics info and do backannotation


    Best regards
    Quek

Reply

  • Hi bnugent

    You can refer to $CDSHOME/doc/parasim/parasim.pdf. The manual explains specifically about post layout simulation and backanotation.

    1. Create schematic
    2. Create test-bench using schematic
    3. Create config view for test-bench
    4. Create layout
    5. Run Assura LVS
    6. Run QRC parasitic extraction to generate extracted view
    7. Open up config view and switch to extracted view
    8. Open up test-bench from config view
    9. Run spectre simulation
    10. Descend into the subcell schematic from the test-bench schematic
    11. Display parasitics menu from "Launch" menu
    12. Set up parasitics info and do backannotation


    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.