Stats

  • Locked Locked
  • Replies 2
  • Subscribers 90
  • Views 3248
  • 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

Insertion of I/O ports location in First Encounter

archive

Hi all.
I know there is an option to specify using the GUI the location of the design's input and output ports in First Encounter.
However, this can be a very tedious job to do each time I want to P&R the design after minor changes in the RTL.
Is there a way to import some kind of file with those definitions ? I didn't find such option.
I thought of writing a script that will do the location specifying automatically using First Encounter's command for this option but for some reason, the command doesn't appear in the command log - can you direct me to the proper command for specifying the location of ports?

Help would be very much appreciated,
Adi.


Originally posted in cdnusers.org by adi_j

  • if you check out the doc soceUG.pdf under Data Preparation, it talked about how to create the I/O spec file (using Design-> Save->IO) after you edited it the first time in Encounter. You can hand edit it later and re-load it back using "loadIoFile".

    li siang


    Originally posted in cdnusers.org by lisiang

  • Hi Adj,

    I use the file "pad.io" to specify my pads or pins. Please see the user guide for the format of this file.

    Sometime, I have to use DEF format (I write a simple awk script to generate the DEF file). I have to use DEF if I have two pins connect to the same net (e.g. a feed-through or to ease top-level routing). It seem that pad.io does not support this. Anyone know how to do this with pad.io? I will reduce some pain for me to craft the DEF. Thanks.

    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan

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.