> lef fi">
     
Thursday, January 08, 2009     Register | Login | Search | Contact Us
     
   
     
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Forums > Digital IC > Floorplanning, Place and route

Subject: tech file complain when adding IO lef file
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
kongtep2
Posts: 6
Online: User is Offline
3/12/2008 4:44 PM  
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
viswanadhbabu
Posts: 16
Online: User is Offline
3/12/2008 8:40 PM  
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
kongtep2
Posts: 6
Online: User is Offline
3/13/2008 3:33 PM  
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
Tongju
Posts: 13
Online: User is Offline
3/14/2008 9:21 AM  
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
Posting to forums is available to community members only.
Login or Register
Forums > Digital IC > Floorplanning, Place and route > tech file complain when adding IO lef file


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.