• 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. Custom IC Design
  3. Cannot load layers in layout

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 21560
  • 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

Cannot load layers in layout

Kabal
Kabal over 13 years ago

Out of nowhere I get this error in my status window when trying to open my layouts:

*WARNING* (GE-2125): Failed to get the manufacturing grid (mfgGridResolution) for the technology tech.db associated to the cellview test_lib/inv1/layout.

 

 I have no idea how come this appear? that tech.db file is in the design kit's folder of IBM kit, nothing was touched. I have tons of layouts which worked for me and I could open them and work on.

 

Any Idea what could get spoiled?

  • Cancel
  • Kabal
    Kabal over 13 years ago

     Ok i created another library based on my design kit lib, and then to there I copied some of the working cells from the library I had before, i tried to open it, and i could see layers, however I still cannot see them in original library.

     

    I noticed that on the LSW top left corner of the working library i see: cmrf7sf, which stands for my design kit tech name.

     

    But on the library whose layouts cant be seen i see cdsDefTechLib,  I guess somehow it got changed from cmrf7sf to  cdsDefTechLib,

     

    So how can I turn it back to cmrf7sf? 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kabal
    Kabal over 13 years ago

    I tried all kinds of stuff, for example from menu: IBM_PDK->Library->Add Ibm PDK Properties, and tefine tech file there. It did not help!

    And interesting thing is, every time when i create new library and put something there, after few restarts it turns again into cdsDefTechLib.. that doesnt make any sense!

     

    Is that setting stored in some textfile? I cannot find it.. How can i fix it?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    I don't know why it is getting lost, but you'd need to use the Attach button in the Tools->Technology File manager form to reattach to the technology library.

    This info is stored as a property in the library's data.dm (so the library properties) (techLibName is the property name). Is your library data.dm getting removed somehow?

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kabal
    Kabal over 13 years ago

    Ok, so:

    1) no data.dm is not there, However strange thing is when i create the library, and choose to "Reference to existing technology file", and then look into the folder of newly created library, data.dm is not there either, is it normal?

     

    2) your method of Attach button in Tools->Technology management for some reason only shows me esd7rf as a design library, and then shows all other libraries I have as a technology library, i.e. I dont know why I do not see another technology libraries in the design library dropdown?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

     Reference is different from Attach. If you reference a technology library you are using the incremental technology database approach - your library will then be a technology database itself, which will in turn reference another library - if  you dump the tech file for your library (which is stored in the tech.db file; attached libraries don't have these), you'll see it has any local overrides plus a reference link to the other technology library (or libraries).

    So that may be the reason why they all show up as technology libraries in the list?

    Hard to know without seeing - you may be best contacting customer support?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kabal
    Kabal over 13 years ago

    Im not sure how many days will the support take. I decided to create some library from scratch and see whats being created, here it is:

    1. when i create new library with "reference to technology" the following two files are created in library folder:

    cdsinfo.tag

    tech.db

     

    Now, when i did that i saw that the layout now is being shown correctly with all layers. (and by the way, when this method was used to create the library, then on top left corner of LSW i see my library name instead of the technology process name, but it works). However, I cannot run the preprocessor to process .netlist files for the LVS. (the tool couldnt find the preprocessor.pl file located within folders of a kit)

     

    2. after that I did this in CIW: IBM_PDK->Library->Add IBM PDK Lib Properties, and added properties of the cmrf7sf. After doing that I noticed the data.dm file appeared in my library folder (together now with cdsinfo.tag and tech.db). 

     

    So it looks to me that one has to do both #1 and #2 operations to get it all working. 

     

    My original library I created long time ago, and forgot how i got it working, the only thing i know is that i used "attach" method when creating it, not the "reference" method, and after things went bad I couldnt bring that library to life. 

    So i created it from beginning using methods above, and will transfer elements from old library. 

     

    And again, i want to stress on the fact that, when i now wanted before to create library using "attach" method, the LSW showed correct layers only at the time when i started creating cell, right after creation of library, but after reboot, all LSW again disappears! and on LSW i see "cdsDefTechLib" instead of technology name.

     

    But when i created it using "reference" method, and then did operation #2, then i see the correct LSW after reboots as well. 

    • 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