1 of 1 people found this helpful
is the question about a symbol and a cell in the Central Library?
About what Mentor tools - schematic, layout, simulation - refer the question ?
Best regards, Liviu Craciun
Good questions, sorry I was down in the details and forgot to include the basics.
We are using DxDesigner for schematic entry with Xpedition for layout. We use hyperlynx drc and hyperlynx for Signal integrity and DC drop analysis.
Hi Jeff - thanks for your post. I am going to move it to the product-specific community where it will receive greater visibility by subject matter experts. The Mentor Ideas communities are where customers can submit enhancement requests to be voted on by others and are reviewed by the product teams for possible inclusion in future releases.
I am not an expert on library work, and I am new to expedition, but since no one else has replied...
I believe Mentor uses this capability to assign power nets to components when the symbols don't provide PWR/GND pins.
If your symbols have the PWR/GND pins, the nets you assign to them will drive the connectivity.
(All of our symbols show PWR/GND pins, so I have never tried any other way)
Mentor use that property for verification as well.. all depend on how much you rely on that verification. There's some rule regarding power/ground net
recently, we try to define power / ground pin as POWER/GROUND pin type for fractured part (multi symbols)...it appears to be bad idea because the tool move all power/ground pin type to a common gate, which will be common to every other symbol ...and choke at packaging!!! so we have to change pins back to somtthing else (we chose bidir)
This is exactly the type of thing I am trying to avoid, although we have symbols with power/ground pin types and we could package it OK.
This is a known issue with the PDB import. You can change the pins back to power and ground in the Part Editor after importing the gates successfully as layout does not use them.
is there any plan to fix those known issue one day ? are those known issue highlited anywhere in documentation ? up to now,it's sad that it's up to each user to discover those issue pretty much by themselve in their learning curve ..