Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 15761
  • 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

Help me change master for schematic view

uvxyz

Hi All,

Nice to meet you in cadence community.

I'm a newbie.

I try to use function dbSetInstHeaderMasterName to change master cellname for schematic view,  but there is a warning message "can't set two instHeaders to the same master" because the master cellname I intend to change is being used by another instance. This can be illustrated by the following example:
    - There are 2 instances in cell A
    - Master cell of Inst1 is mas_a
    - Master cell of Inst2 is mas_b
    - I can't change master cell of Inst2 from mas_b to mas_a if using dbSetInstHeaderMasterName.

Is there any way to change master cell of Ins2? Please note that I perform this operation in SKILL source code, not for GUI.

I would lile to receive all help from you.

Thanks you very much,
--vu~

  • dbSetInstHeaderMasterName is used to change all instances of a particular master to another - but you're right, you cannot use it if that master is already used in the cellView.

    Instead, you need to set the ~>master attribute of each instance, one by one. This is set to the new master - and you'll see that instance then gets moved to the other instHeader.

    Regards,

    Andrew.

  •  Dear Andrew,

    Thanks for your comment.

    Due to setting master attribute for schematic view, the operation ~> will result in floating pin or some connection will be destroyed.

    How should I do ?

    Regards,

    --vu~.

  • vu,

    Are you saying that the replacement cell has different pins, or pins in different locations? If so, you'd have exactly the same problem if you changed the cell interactively in the schematic editor - how would you solve it then? You'd presumably need to wire up the extra pins? If so, you could automate this (maybe) with schCreateWire(). But since I don't know what your real problem is, or what the objective is for what you're doing, the best I can do is guess.

    Perhaps the problem is something else? If it is, you'll need to be clearer about what the problem actually is.

    Regards,

    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.