• 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 SKILL
  3. How do you get the prop.xx file when creating a techlib...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 15091
  • 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

How do you get the prop.xx file when creating a techlib in nograph mode?

jaleco
jaleco over 8 years ago

I am creating a new techlib and compiling an ascii techfile into it using the core code of ddCreateLib(), techOpenTechFile(), and tclLoadTechFile() from the attached solution.

However, I get very many warnings about the prop.xx file missing when opening the final layout in graphics mode.

The solution description says explicitly that it does not create the prop.xx file and to copy it from somewhere.

Where should the prop.xx file be copied from if it is not specific to a techlibrary? 

Since prop.xx binary, the contents are unknown, to confirm a random copy from another library is ok.

Alternatively, is there another way to create a new techlib and compile a techfile in nograph mode that would generate the prop.xx file?

support.cadence.com/.../ArticleAttachmentPortal;pageName=ArticleContent&sq=005d0000001T5b7AAC_2017111103018741

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    There is no need to have a prop.xx (or data.dm if OA) at the library level if you have a library with its own technology database (as is the case in this article). That article is a bit odd - I can't imagine why you'd ever copy it with a system() call. If you really wanted to copy it from another library, you really should use the ccp functions, but even then I don't see why you'd necessarily need to unless you need the specific properties.

    Without knowing what messages you're getting, I'm not sure I can advise you more...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jaleco
    jaleco over 8 years ago
    Hi Andrew,
    more specifically I am getting these warning messages when streaming out from a layout view, and they do not show up in my log file - just in the CIW.
    The message is:
    *WARNING* dbOpenBag: Failed to open prop. bag for 'mytechfile' in 'r' mode, file not found
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    I don't know which version you're using. I'm guessing it's an IC5141 version (since you're talking about prop.xx) - what does getVersion(t) return?

    I just tried reproducing this with the final hotfix of IC5141 (5.10.41.500.6.151 from November 2011). I don't get any such warnings, and I don't have any prop.xx files anywhere in the library, and I used the SKILL code in the solution to create the library.

    I did find CCR 228872 (filed in 2005) which talked about these warnings; it was never marked fixed, but I'm guessing it may have been resolved in a later hotfix. Anyway, those warnings are benign - it certainly is not required to have a property bag, and the CCR also reiterates that.

    If it really bothers you, you can do:

    bag=dbOpenBag(ddGetObj("mylib") "a")
    dbSaveBag(bag)
    dbCloseBag(bag)

    where "mylib" is whatever your library name is called.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jaleco
    jaleco over 8 years ago
    Thank you Andrew,
    Yes, this project is using version 5141. getVersion(t) returns "sub-version 5.10.41_USR5.90.69".
    dbOpenBag() did create the prop.xx for the techlib and eliminated the warnings on streamout.
    Thank you again for your information!
    • 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