Stats

  • Locked Locked
  • Replies 3
  • Subscribers 63
  • Views 15299
  • 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

SOC Encounter

Oysters

 how to write .io assignment file in SOC encounter.

c an anyone tell me or can give me any documents regarding , How to write .io file for the SOC Encounter

Parents
  • gops
    Hi Oysters;
     
    I don't have a doc. regarding the same.
     
    According to my knowledge  .io file is not used to add an IO instance, instead it's just used to arrange it around the core.
     
    You can add IO cells in your design  in two ways.  you add it in synthesized nelist or you can use virtuoso schematic editor for the purpose. For the second option you need to load your netlist to virtouso and generate  a schematic.then add io cells and regenerate netlist.
     
    for the first option you need to modify your netlist.
     
    You create a new top module and add IO cells ,corner cells  under the new one.
     
    Then import this to encounter. Just save the IO file and edit it to re arrange the IOs.
     
    Hope this helps.
Reply
  • gops
    Hi Oysters;
     
    I don't have a doc. regarding the same.
     
    According to my knowledge  .io file is not used to add an IO instance, instead it's just used to arrange it around the core.
     
    You can add IO cells in your design  in two ways.  you add it in synthesized nelist or you can use virtuoso schematic editor for the purpose. For the second option you need to load your netlist to virtouso and generate  a schematic.then add io cells and regenerate netlist.
     
    for the first option you need to modify your netlist.
     
    You create a new top module and add IO cells ,corner cells  under the new one.
     
    Then import this to encounter. Just save the IO file and edit it to re arrange the IOs.
     
    Hope this helps.
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.