• 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. layoutXL Gen from source doesn't give correct sizes.

Stats

  • Locked Locked
  • Replies 13
  • Subscribers 125
  • Views 5485
  • 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

layoutXL Gen from source doesn't give correct sizes.

MarkTown
MarkTown over 13 years ago

 If I place my Pcell by hand the cell works fine. Sizes are what I expect them to be.

Gen from source gives me small values that can't be laid out.

The symbol though has "90n M" which doesn't match other tech files I've worked with "90n"

 I've tried two different ways of doing the CDF:

    cdfCreateParam( cdfId
        ?name           "w"
        ?prompt         "width"
        ?defValue       "0.2n"
        ?parseAsNumber  "yes"
        ?type           "string"
        ?units          "lengthMetric"
    )
 

 

I've also tried the following default value:

minMosWidth = 0.2 * 1e-6

?defValue       sprintf(nil "%g" minMosWidth)
 

Neither gives me the desired result.  Any thoughts?

 

Mark

  • Cancel
Parents
  • MarkTown
    MarkTown over 13 years ago

     Yes, Andrew, I'm aware that its a units issue. I've tried quite a few different units trying to get them to match. I get the code working one way and then it breaks another way. 

     

    For something as easy to mess up as this, it would be nice if CD not only had an example like the 90nm sample code but also an explanation of why each cb, cdf, il and symbol has to be what it is and why. Where the conversion should be etc. I've thought I had ever line matched up with the CDS examples and yet it still didn't work. 

     

    So now its just going to ahve to be skill code that is placed. Its easy to make that work.  No gen from source in this version.

     

    thanks for you help

    Mark

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • MarkTown
    MarkTown over 13 years ago

     Yes, Andrew, I'm aware that its a units issue. I've tried quite a few different units trying to get them to match. I get the code working one way and then it breaks another way. 

     

    For something as easy to mess up as this, it would be nice if CD not only had an example like the 90nm sample code but also an explanation of why each cb, cdf, il and symbol has to be what it is and why. Where the conversion should be etc. I've thought I had ever line matched up with the CDS examples and yet it still didn't work. 

     

    So now its just going to ahve to be skill code that is placed. Its easy to make that work.  No gen from source in this version.

     

    thanks for you help

    Mark

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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