Stats

  • Locked Locked
  • Replies 10
  • Subscribers 144
  • Views 4380
  • 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* dbTransformPoint: Invalid point - nil

Reinice

Hi All,

I want to get the points of a terminal(a "polygon" object type) pins(e.g. PLUS-MINUS, E-B-C) from a schematic symbol

Here is my script:

foreach( cell ddGetObj("QCBGB7_09T")~>cells

cvId=dbOpenCellViewByType("QCBGB7_09T" cell~>name "schematic" "schematic" "a")

foreach(inst cvId~>instances

if(inst~>cellName=="ndio" then

when(inst~>purpose == "cell"

foreach(insTerm inst~>insTerms

insTermPntsO=car(insTerm~>terms~>pins~>fig~>points)

ll=nth(0 insTermPntsO)

ur=nth(2 insTermPntsO)

tform=inst~>transform

;;transform ll=lower right and ur=upper right points of a symbol

insTermPntLL=dbTransformPoint(ll tform)

insTermPntUR=dbTransformPoint(ur tform)

);end of foreach

);end of when

);end of if

);end of foreach

);end of foreach

I' am having this error everytime I run this script for the "ndio" schematic symbol. By the way "ndio" is a symbol_xform(symbol pcell)

*Error* dbTransformPoint: Invalid point - nil

But if I use the script first time for other symbol such as pnp, for once I 'am not encountering this error. By the way "pnp" is also a symbol_xform(symbol pcell)

After I run the script again for pnp I' am encountering the same error.

Please correct the wrong part of my script.

Can anyone help me. It will be highly appreciated if anyone can help.

Thank You Very Much in advance.

Thanks and Regards,

Reinice

Parents

  • Reinice,

    That was an example of how to use it! Place it after the dbOpenCellViewByType() call. It's normally used to force all the sub-cells in a layout to load from disk too - although then you'd typically give a larger second number (the number of levels of hierarchy). Since schematics instantiate symbols, there's no point in specifying a large number for the hierarchy (although it won't do any harm) because symbols don't normally contain hierarchy. My idea was to see if the dbOpenHier() call causes it to force all the instantiated symbols to be loaded from disk, and if they are pcells (such as the symbol_xform views) to be evaluated - it needs to evaluate each variant to produce the subMaster - that's where the pin figures should be defined.

    I'm not sure this will fix your problem - mainly because I'm not really sure what your problem is (seeing the database and code would make it much easier to understand) - so this is a bit of guesswork.

    Regards,

    Andrew

Reply

  • Reinice,

    That was an example of how to use it! Place it after the dbOpenCellViewByType() call. It's normally used to force all the sub-cells in a layout to load from disk too - although then you'd typically give a larger second number (the number of levels of hierarchy). Since schematics instantiate symbols, there's no point in specifying a large number for the hierarchy (although it won't do any harm) because symbols don't normally contain hierarchy. My idea was to see if the dbOpenHier() call causes it to force all the instantiated symbols to be loaded from disk, and if they are pcells (such as the symbol_xform views) to be evaluated - it needs to evaluate each variant to produce the subMaster - that's where the pin figures should be defined.

    I'm not sure this will fix your problem - mainly because I'm not really sure what your problem is (seeing the database and code would make it much easier to understand) - so this is a bit of guesswork.

    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.