Scripts or commands to create the package stackup

you can always import and export the cross section technology file from the cross secton editor.

after adding the top 4 layers of the laminate 1 design on the cross section editor on the laminate 2 design, you can import laminate1 design into the laminate 2 design.

you are very lucky as you need to deal with only 12 layers.

i have to deal with 21 layers (5 layers on the interposer plus 16 layers on the bottom substrate)

thanks for the reply, actually this is the pre-design stage. There is no design. You can assume that there are 2 stack-ups available one with me and other with another end user. I will give the end user the laminate2 stack-up without any design.

The other user wants to instantiate this laminate2 stackup on his laminate1 stackup and then start the design. This will then become easy for them to repeat this for other database in future if they are able to instantiate my stackup over their laminate database which can change from time to time.

So keeping this in mind can you please suggest what should be done.

if there is not design yet, that would be much easier.

i would talk to your end user as to what layer names, what constraint name to be used on the design.

then you create one file which has all the layers including laminates 1 & 2 and all the constraints used on laminates 1 & 2.

you give your end user a copy of the file.

you work on the laminate 1 portion.

your end user works on the laminate 2 portion.

after you and your end user complete the work, then you can combine them into one design.

you are very lucky as you have another one to work with.

i have to work alone with designing both laminates 1 & 2.

thanks for the reply,

"you create one file which has all the layers including laminates 1 & 2 and all the constraints used on laminates 1 & 2." -

the above method is not scalable as tomorrow if their laminate1 changes then again a new file has to be created hence i am trying to seek a scalable solution where I just give the end user the database and they should be able to use it with whichever laminate stackup they have in future without requiring my intervention. This is the way the end user wishes. They don't wish to come back to me time and again if they laminate layers change.

By the way the 12 layers is just an example that I gave , actual scenario is having many more layers in laminate1 and 2.

thanks for the reply,

"you create one file which has all the layers including laminates 1 & 2 and all the constraints used on laminates 1 & 2." -

the above method is not scalable as tomorrow if their laminate1 changes then again a new file has to be created hence i am trying to seek a scalable solution where I just give the end user the database and they should be able to use it with whichever laminate stackup they have in future without requiring my intervention. This is the way the end user wishes. They don't wish to come back to me time and again if they laminate layers change.

By the way the 12 layers is just an example that I gave , actual scenario is having many more layers in laminate1 and 2.

you and your end user can work separately with different designs on different files.

if you later change the layer stackup, that would be fine.

if your end user later change the layer stackup, that would be fine also.

when you combine them into one file, you simply make sure that no layer names, no constraint names, no symbol names are identical.

Thanks for the reply, but I won’t be changing the design. It needs to be a plugin for the end user so that they can do trials with their different  stackups.

Hello , any suggestions on my last request ?

what is your request?

Hi all,

Can you please suggest a way to change the pin names and nets names of a .mcm file ? I have a completely routed design where I need to rename all the netnames and pin names one by one. (Pin names for the die as well as BGA).