Stats

  • Locked Locked
  • Replies 1
  • Subscribers 165
  • Views 12428
  • Members are here 0
More Content
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

Module with homogeneous part does not optimize package

PaoloUoB

I have created a module that includes a single opamp which comes in a quad package (i.e. there are 4 identical opamps in one IC, specified as different sections in part developer).

Now I need to place 4 of such modules in my design.

In my past experience, once placing several modules, the packager would recognize that the opamps can be optimized and use a single IC every four modules. However in the current design this is not happening: each module is assigned a unique IC (so IC1, IC2, IC3, IC4) and then only one of the opamps in the IC is used in every module. This is clearly not ideal as it means using 4 times the number of required ICs.
I have tried to descend into a module and specify the section to use, but the change propagates to all of the other modules: if I descend in module 2 and specify to use section 2, then all other modules use section 2 and I am back to the starting point.

I have read various documentation about modules and packagin but I still can not locate why this is happening.

Is there a trick/setting to tell the packager to optimize the ICs to use the minimum amount of components?

  • Answering my own question.

    After a bit of trial and error, I found the source of the issue: I had assigned the ROOM property to each module. The property is obviously inherited by the components inside the module. It turns out that if two opamp have different ROOM values, the packager treats them as separated and refuses to put them in the same IC.

Cadence Guidelines

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.