Stats

  • Locked Locked
  • Replies 2
  • Subscribers 144
  • Views 1694
  • 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

Member object is 'nil' after using dbCreateInst in SKILL script, works fine in CIW

TrumanBurbank

Hi,

I am automating the creation of many buffers in my schematic, however, I encounter this error:

buf_cv = dbOpenCellViewByType("techlib" "buffer_name" "symbol")

buf = dbCreateInst(cv buf_cv "test_buffer" list(inx iny) "R0" 1)

println(buf~>instTerms)

Where inx and iny are coordinate values assigned earlier. "techlib" and "buffer_name" are stand-ins for a tsmc standard cell library and the buffer cell. I don't understand why the last line, buf~>instTerms returns nil. If I go to the CIW and select the buffer schematic, and run:

css()~>instTerms

It gives the list of terminal objects as expected. What is causing the discrepancy and what's the solution? Thanks

  • You need to explicitly Check and Save when running script ( schCheck + dbSave )

    Newest versions of Virtuoso are doing the C&S automatically when schematic changes, so this may explain the discrepancy

    Sebastien

  • in reply to sebcliq

    Just to clarify what Sebastien says, the database itself does not automatically create instTerms - you'd need to do that yourself with dbCreateInstTerm or dbCreateConn, or call schCheck() to call the schematic extractor/checker. In ICADVM20.1 there is automatic incremental connectivity extraction in the schematic editor (if the schematic is open in the schematic editor) - it's not quite doing an automatic "Check and Save" - it's only doing the connectivity extraction incrementally, and not (yet) the check part (this is on the future plan) and certainly not the save. Even in older releases, the schematic editor tended to auto-add instTerms, but Sebastien is right, you're almost certainly seeing the effects of the editor kicking in.

    Andrew

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.