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

 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

Parents

  •  Well, turns out there is still an issue with the size of the Pcell.

     

    If I places the nsoi Pcell thru layoutXL gen from source I get the correct size transitors.

    If I instanciate the pcell from my layout cell I get very large transistors. This makes sence in the way I've changed the Pcell code to get it to work with the gen from source.

       ;  Define formal parameter name-value pairs.
       (
          ( w     "0.2" )
          ( l     "0.09" )
    ....

    these lines work with gen from source.

           width  = cdfParseFloatString(w)* 1e6
           length = cdfParseFloatString(l)* 1e6

    These lines work when pcell is instanciated.

    ;       width  = cdfParseFloatString(w)
    ;       length = cdfParseFloatString(l)

    I currently don't have any call back called.

     There is the CDF code:

        ;;; Parameters
        cdfCreateParam( cdfId
            ?name           "w"
            ?prompt         "width"
            ?defValue       "0.2"
            ?parseAsNumber  "yes"
            ?type           "string"
          ?units          "lengthMetric"
    ;        ?callback    "nsoiCB('w)"
        )
        cdfCreateParam( cdfId
            ?name           "l"
            ?prompt         "length"
            ?defValue       "0.09"
            ?parseAsNumber  "yes"
            ?type           "string"
          ?units          "lengthMetric"
    ;        ?callback    "nsoiCB('l)"
        )

     

    Anyone got any thoughts about where the conversion should take place from schematic to layout?

     

Reply

  •  Well, turns out there is still an issue with the size of the Pcell.

     

    If I places the nsoi Pcell thru layoutXL gen from source I get the correct size transitors.

    If I instanciate the pcell from my layout cell I get very large transistors. This makes sence in the way I've changed the Pcell code to get it to work with the gen from source.

       ;  Define formal parameter name-value pairs.
       (
          ( w     "0.2" )
          ( l     "0.09" )
    ....

    these lines work with gen from source.

           width  = cdfParseFloatString(w)* 1e6
           length = cdfParseFloatString(l)* 1e6

    These lines work when pcell is instanciated.

    ;       width  = cdfParseFloatString(w)
    ;       length = cdfParseFloatString(l)

    I currently don't have any call back called.

     There is the CDF code:

        ;;; Parameters
        cdfCreateParam( cdfId
            ?name           "w"
            ?prompt         "width"
            ?defValue       "0.2"
            ?parseAsNumber  "yes"
            ?type           "string"
          ?units          "lengthMetric"
    ;        ?callback    "nsoiCB('w)"
        )
        cdfCreateParam( cdfId
            ?name           "l"
            ?prompt         "length"
            ?defValue       "0.09"
            ?parseAsNumber  "yes"
            ?type           "string"
          ?units          "lengthMetric"
    ;        ?callback    "nsoiCB('l)"
        )

     

    Anyone got any thoughts about where the conversion should take place from schematic to layout?

     

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.