• 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. issue in altering the 'numInst' value for a iterated in...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 144
  • Views 6050
  • 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

issue in altering the 'numInst' value for a iterated instance

Chikoo
Chikoo over 12 years ago

Hi,

I am trying to alter the parameter 'numInst' for an iterated instance.i.e.,I am trying re-assign the numInst paramter.But I can see that the value is not getting updated.

The assignment was working fine in 5.1 version but it is not working in OA version 6.1.5.

eg:

 

cv=geGetEditCellView()

instId=dbOpenCellViewByType(<libName> <cellName> "symbol" "" "r")

cellId = dbCreateInst(cv instId "test" <coord> "R0" 5)

 

The above will return me an iterated instance 'test<4:0>' at the location defined by <coord>.

Now if i have to alter the number of instances to 2 later in the code, in older version 5.1, I could do something like cellId~>numInst=2 which will return me an instance 'test<1:0>'.But the same is not working in 6.1.5.

After doing some research i found the command 'dbSetAnyInstNumInst' in 'Integrator’s Toolkit: Database Reference Manual,Product Version 5.0'.

Is there any equivalent command for 'dbSetAnyInstNumInst' in 6.1 or is there some other way in which we can change the numInst value.

Thanks in advance,

Chikva


  • Cancel
  • skillUser
    skillUser over 12 years ago

    Hi Chikva,

    I have never tried to set numInst directly, I always assumed that it would be derived from the instance name (e.g. I<4:0> would yield numInst of 5) - the IC61x dbCreateInst function still accepts the x_numInst argument, so what doesn't work, modifying it directly?  I could not find this documented anywhere.  It may be that you have encountered a feature which was undocumented which happened to change between releases - I don't know without investigating deeper.  By the way in your code example I think the names should be swapped for less confusion, i.e. cellId should be used for the return value of the dbOpenCellViewByType function, and instId should be used for the return value of dbCreateInst.

    Hope this helps,

    Lawrence.

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

     Hi Lawrence,

    I need to modify the numInst value based on certain conditions.i.e,I will be needing different bit instances to be used as I will be using a skill code to generate my toplevel block.

     Thanks,

    Chikva

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

     Use the dbCreateParamInst(celview master name x:y rotation numberOfInst parameters)

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

    Thanks Slayer.

    I can use the suggested command or even dbCreateInst ,but I will be losing the connectivity information,otherwise I need to do a Check and Save in between after instantiating the block.Again I need to retrieve the co-ordiante information before removing the old instance so that I can re-instantiate

    Thats why I was checking for a work around.:-)

    Thanks,

    Chikva

    • 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