Stats

  • Locked Locked
  • Replies 6
  • Subscribers 91
  • Views 14796
  • 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
After floorplanning my design in Encounter, I specified partition to few of my blocks in the design. I did gds streamout and imported the .gds file to virtuoso. The netlist extracted from virtuoso do not show the partitions. How should I preserve the partioning all the way until the netlist phase? Please help me out!
Parents
  • Hi Brian,

    I tried converting my transistor level hspice netlist of sensor into lef format, instantiated in verilog  and did place-and-route in encounter. But in place phase, the standard cells are populated in the entire circuit except  in the sensors since the are not described as netlist with standard cells to start with. In the final gds, the sensor location came out as empty. Please let me know if my flow has a problem.
    Also, I was not able to access the mixed signal interoperability guide that you suggested me to. If possible, could you send me the file to spendya2@mail.usf.edu so I will try to find solution to my problem from the interoperability guide?

    Thanks a lot,
    Shiny
Reply
  • Hi Brian,

    I tried converting my transistor level hspice netlist of sensor into lef format, instantiated in verilog  and did place-and-route in encounter. But in place phase, the standard cells are populated in the entire circuit except  in the sensors since the are not described as netlist with standard cells to start with. In the final gds, the sensor location came out as empty. Please let me know if my flow has a problem.
    Also, I was not able to access the mixed signal interoperability guide that you suggested me to. If possible, could you send me the file to spendya2@mail.usf.edu so I will try to find solution to my problem from the interoperability guide?

    Thanks a lot,
    Shiny
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.