dbCreateExtParamInst

dbCreateExtParamInst(
d_cellView
d_master
t_name
l_point
t_orient
[ x_numInst
[ l_params
[ g_physOnly ] ] ]
)
=> d_inst / nil

Description

Creates a parameterized cell instance (of cellview d_master) in the cellview d_cellView with an origin and orientation specified by l_point and t_orient. The parameters in the l_params list may be CDF parameters whose values match the CDF parameter defaults.

Arguments

d_cellView	Cellview in which the instance is placed.
d_master	Parameterized cell master cellview of the instance that is to be created. This parameter must be a super master; use of a submaster can cause unexpected behavior.
t_name	The parametrized cell instance is named by t_name; if nil the program assigns a unique name to the instance. t_name must obey the syntax of instance names as defined at the beginning of this chapter.
l_origin	Origin of the new instance.
t_orient	Orientation of the new instance.
x_numinst	(Optional) Number of instances; if t_name is given, it overrides any value specified by x_numInst (that is, the number of instances is derived from the name instead of taken from the x_numInst argument). If not specified, the default is one.
l_params	(Optional) Specifies a list of l_param, where l_param is list(t_propName t_propType g_value). If l_params is not specified the default is nil.
g_physonly	(Optional) Specifies whether cellview data is physical or both physical and logical. A cellview may contain both physical and logical data when it contains EMH type data. When t, the cellview is physical only. Default is nil.

Value Returned

d_inst	Returns dbObject of the instance.
nil	Returns nil if the instance is not created.

Examples

i3 = dbCreateExtParamInst(cell master "I3" 0:0 "R0" 1 list(list("aInt" "int" 11)) t)

Additional Information

The following example explains the difference between dbCreateParamInst and dbCreateExtParamInst:

Suppose a super master has parameters A=1 and B= 2. You create a parameter instance with A=2 in a top design and do not specify B, it is inherited.

The effective parameters on the instance will be A=2, B=2.

This top design is saved and purged.

Suppose the super master is modified out of context, and now A=2 and B=1.

You open the top design again and check the parameter instance.

If the parameter instance was first created with dbCreateParamInst, the effective parameters will now be A=2, B=1.

If the parameter instance was first created with dbCreateExtParamInst, the effective parameters will now be A=2, B=2.

This means that, dbCreateExtParamInst fixes the parameter values of unspecified parameters (here, B) so they do not change in the future if the super master is redefined.

Related Topics

rodGetObj

dbCreateParamInst

Return to top