Stats

  • Locked Locked
  • Replies 3
  • Subscribers 92
  • Views 13849
  • 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 as a LEF viewer ?

Anjana

I am working on a design for which we use a memory from a customer. We would like to see the pin locations / assignments in the memory lef that they dropped . But  I have not yet received a pre -synthesised netlist from the front end yet ,otherwise i could load it up and check. Is there any option in encounter wherein I could load the lef and see how the pin assignments are ?.

 

  • One solution is create a simple Verilog netlist that instantiates the memory such as:

        module top ();

        memoryName inst0();

        endmodule

    Then import that into Encounter in place of the synthesize netlist. You can then view the memory in the floorplan.

    Regards,

    Brian

  • I do this all the time.  There is no specific LEF viewer that I know of (perhaps somebody else does?).  However, it is relatively easy to create a wrapper Verilog around this cell, you don't even need to specify any ports or connectivity, just instantiate the cell.  Then load it up like any other design.  You'll need to open the color menu and expose pins and route blockages in the wires tab.  There are no actual wires when you view the LEF this way.  

     Hope that helps,

    Jason 

  • Thank you very much , Brian & Jason. I shall try that out.

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.