Stats

  • Locked Locked
  • Replies 4
  • Subscribers 142
  • Views 2522
  • 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

Ultra pcell - pcell with variable of pcell in it.

kb how

Hi All,

Is there possible for us to create a ultra pcell where the pcell within the pcell is a variable, not fixed.

Example: I have a dummy pcell which is ultra pcell, and i want to make it flexible enough to have n number of dummy1 pcell in it, with different CDF param value. If it is possible, it will be great if you could share some example,

Thanks.

 

Parents

  • Hi How,

    Inside the pcDefinePCell, you'd have something like:

          inst=dbCreateParamInstByMasterName(
                pcCellView
                srcLib
                srcCell
                "layout"
                ""
                0.0:0.0
                "R0"
                1
                list(
                    list("l" "string" sprintf(nil "%g" lMic*1e-6))
                    list("w" "string" sprintf(nil "%g" wMic*1e-6))
                    list("cCols" "string" cCols)
                    list("segments" "string" segments)
                    list("segSp" "string" segSp)
                    list("connection" "string" connection)
                )
              )

    In this particular case, cCols, segments segSp and connection were parameters for the pcell and were all string types. The lMic and wMic were computed within the pcell code, and were originally derived from other parameters passed in.

    That's the idea - it's not very complicated. Not a complete example, but hopefully sufficient to get you moving?

    Regards,

    Andrew.

Reply

  • Hi How,

    Inside the pcDefinePCell, you'd have something like:

          inst=dbCreateParamInstByMasterName(
                pcCellView
                srcLib
                srcCell
                "layout"
                ""
                0.0:0.0
                "R0"
                1
                list(
                    list("l" "string" sprintf(nil "%g" lMic*1e-6))
                    list("w" "string" sprintf(nil "%g" wMic*1e-6))
                    list("cCols" "string" cCols)
                    list("segments" "string" segments)
                    list("segSp" "string" segSp)
                    list("connection" "string" connection)
                )
              )

    In this particular case, cCols, segments segSp and connection were parameters for the pcell and were all string types. The lMic and wMic were computed within the pcell code, and were originally derived from other parameters passed in.

    That's the idea - it's not very complicated. Not a complete example, but hopefully sufficient to get you moving?

    Regards,

    Andrew.

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.