• 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. encounter streamout by preserving the partition

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 126
  • Views 12912
  • 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

encounter streamout by preserving the partition

Shiny
Shiny over 12 years ago

Hello All,

I started with a vhdl behavioral filter design, did structural synthesis using Cadence BuildGates, place and route with soc encounter, imported output of encounter to virtuoso and extracted spice netlist using divaEXT.rul. My experimentation is supposed to be on the spice netlist.

The problem is I need to insert sensors in the filter design and connect them to certain modules. I have a transistor level implementation of filter (it cannot be represented as a gate level design). I was confused where to insert it in the flow so I specified those certain modules as partitions in soc encounter expecting a final structural netlist where I thought I could insert the sensors. But it is not working.

Can you suggest me another way to insert my filters in the flow?

Thanks a lot,

Shiny

  • Cancel
  • Quek
    Quek over 12 years ago

    Hi Shiny

    It sounds like you are exploring a mixed-signal design flow. How about this?

    a. Create abstract views for the sensors using abstract generator
    b. Export LEF files from the abstract views
    c. Use the LEF files in your Encounter flow together with the other LEF files

    Best regards
    Quek

    • 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