Simulator Configuration Guide for Synopsys Models

Chapter 7: Using QuickSim II with Synopsys ModelsSimulator Configuration GuidePIN_NAME MappingThe two methods for creating custom symbols described in “Custom Symbols” on page144 cannot be used to map bus symbol pins to model pins. You must use a pin_map fileto accomplish this sort of custom symbol creation, as explained in the followingsections.PIN PropertyA PIN property can have two distinct values in Design Architect, as follows:●●Compiled pin valueUser pin valueThe compiled pin value must be the same value that is used in the model. When initiallyadding a pin to a symbol, both these values are set to the specified value. For example,naming a pin “A” causes both its user pin value and the compiled pin value to be “A”.Changing a PIN property value causes the compiled pin value to track the user pinvalue. Specifically changing the compiled PIN property value disables this trackingmechanism. To re-enable tracking, set the value of the compiled PIN property to null(“”).PIN_NAME PropertySmartModel Library symbols include a property called PIN_NAME that is used purelyfor graphical purposes. The PIN_NAME property is provided because SmartModelLibrary symbols do not completely match the Mentor Graphics requirements for pinnames. Deleting a PIN_NAME property does not affect model functionality in any way.AttentionDo not confuse the PIN property with the PIN_NAME property onSmartModel symbols.Purpose of the pin_map FileUse the pin_map file to map custom symbol pins to model pins. If your symbol does nothave buses, then you can use the “user pin value” and “compiled pin value”combinations previously described to do this mapping without using the pin_map file. Ifyou have bus pins on your symbol, then you need to use a pin_map file and ensure thatthe PKG symbol property is set to the value “BUS”. Following is a general descriptionof the pin_map file which describes both cases.NoteError messages cite the pin names used by the model, not those on thesymbol or in the pin_map file.146 Synopsys, Inc. October 6, 2003