• 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. Error marker when gen. PCell

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 14780
  • 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

Error marker when gen. PCell

RVERP
RVERP over 12 years ago

When I generate a pcell,  it includes a marker error.

If I look up the explanation, it says:

location: ("testLib" "pcTest" "layout")
reason:   Generating Pcell for 'pcTest layout'.

 Any idea what this means? If this is'nt enough, I can always post the PCell code.

 Thanks

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Do you by any chance have a printf() statement in your pcell code?

    If not, perhaps you can post the code?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RVERP
    RVERP over 12 years ago

     I have indeed a sprintf statement, what's wrong with that?

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

    Nothing wrong with an sprintf - it's printf that I was asking about. Within pcell evaluation, anything printed to standard output is converted to be a marker on the pcell - this is a convenience to allow markers to be generated.

    So an sprintf should not cause this problem...

    Maybe you should just post your code?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RVERP
    RVERP over 12 years ago

    procedure( icsMatchedCrossQuad(arrayLibName arrayCellName mosType l w labelList)

        eval(`pcDefinePCell(
            list(ddGetObj(,arrayLibName) ,arrayCellName "layout")

            ; PCell Parameters
            ; ----------------
            (
            (l float float(l))
            (w float float(w))
            (mosType string mosType)
            (labelList ILList labelList)
            )

            ; PCell skill code
            ; ----------------
            let((pathPitch unitName)
                pathWidth = 2*cadr(icsInit->metalConstraints->metalViaEnclosure) + cadr(icsInit->viaConstraints->viaWidth)
                pathPitch = pathWidth + cadr(icsInit->metalConstraints->metalSpace)

                ; Generate unit
                ; -------------
                unitName = sprintf(nil "%s_unit" ,arrayCellName)
                icsMatchedCrossQuadUnit(,arrayLibName unitName mosType float(l) float(w) labelList)

                ; Place in cross quad
                ; -------------------
                let((xPos yPos pcMaster)
                    yPos = icsInit->mosConstraints->mosGOffset + pathPitch*2
                    xPos = 4*l + 6*icsInit->mosConstraints->mosSDOffset

                    pcMaster = dbOpenCellViewByType(,arrayLibName unitName "layout" "maskLayout")

                    dbCreateParamInst(
                        pcCellView
                        pcMaster
                        nil
                        (0:yPos)
                        "R0"
                        1
                        list(    list("l" "float" l)
                            list("w" "float" w)
                            list("mosType" "string" mosType)
                            list("labelList" "ILList" labelList)
                            )
                        )

                    dbCreateParamInst(
                        pcCellView
                        pcMaster
                        nil
                        (xPos:-yPos)
                        "R180"
                        1
                        list(    list("l" "float" l)
                            list("w" "float" w)
                            list("mosType" "string" mosType)
                            list("labelList" "ILList" labelList)
                            )
                        )
                ) ;End of let
             ) ;End of let
        ) ;End of pcDefinePCell
        ) ;End of eval
    ) ;End of procedure

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

    My guess (I can't run your code because it is not complete) is that this is caused by the call to icsMatchedCrossQuadUnit() in your code. I'm guessing that this function also generates a pcell - and so it will output a message telling you that it is building a new pcell - and that output (because it's on stdout) will appear as a marker.

    In general I really would not create a new pcell within a pcell evaluation. Fine to instantiate another pcell, but building it doesn't make so much sense to me. It's not obvious why you would want to do that, rather than creating the pcell up front (outside of the pcDefinePCell).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RVERP
    RVERP over 12 years ago

    Ok, I moved the creation of the second Pcell out of the "Master" Pcell,and the marker is gone.

    Thanks

    • 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