• 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. Digital Implementation
  3. tech file complain when adding IO lef file

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 90
  • Views 13777
  • 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

tech file complain when adding IO lef file

archive
archive over 17 years ago

Please help! I would like to use Encounter to configure the IO pad, so I include the IO .lef and .lib file into the .conf file as usual with the command:

set rda_input(ui_iolib) "io.lib"
set rda_input(ui_leffile) "io.lef"

but then, I got this error >> lef file can not work with cdump files without a tech file.

anyone seen this kind of error before? thanks!
sincerely,
chhay


Originally posted in cdnusers.org by kongtep2
  • Cancel
  • archive
    archive over 17 years ago

    Hi Chay ,

    I think you might not have given technology lef file before io.lef .
    So, load the technology lef file first and then io.lef.

    regards,
    KVB


    Originally posted in cdnusers.org by viswanadhbabu
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Thanks KVB. I did include the "tech.lef" before the "io.lef". but the error is still there. It is weird. that it complains about: >> lef file can not work with cdump files without a tech file. only when i have the command: set rda_input(ui_iolib) "io.lib" in the .conf file. so i think there's nothing wrong with the lef file but the io.lib. I look into the "io.lib" file, everything seems normal and similar to the regular std_cell.lib. please help. thank you very much.
    chhay


    Originally posted in cdnusers.org by kongtep2
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    FYI: For lef file, I usually put them into one line in my conf file like: set rda_Input(ui_leffile) "tech.lef stdcell.lef macroList.lef". It works fine. The tech.lef should have layers, vias, via gen rules, site/core defined inside it. Sometimes, if the header of macro/stdcell lef file conflict with the corresponding information in tech.lef, it may fail, then, I usualy remove all the header portion of it. Also, check the consistance between your tech lef and your io.lef file, such as if the layer names used are same. For .lib files, I also integrate them into "set rda_Input(ui_timelib,min/max)...".
    Tongju


    Originally posted in cdnusers.org by Tongju
    • 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