use_global

Specifies a single spine (LocalClock) or a rectangular spine region which may encompass more than one spine.

use_global spine <net_name>;

Arguments

spine

Specifies one of the spines: T1 to T<n> or B1 to B<n>.

net_name

Specifies the name of a net.

Supported Families

 ProASIC PLUS and ProASIC

Exceptions

• None

Example

If you specify the spine rectangle as B1, T3, the driven instances of the given net get a region constraint which encloses the rectangle, including the spine rectangle B1, T1, B2, T2, B2, T3.

use_global B1, T3 <net_name>;

The constraint tries to place the driver as close to the center of the rectangle as possible.

The RAMs and I/Os are assigned to the LocalClock region unless the Compile option  “Include RAM and I/O in Spine and Net Regions” is cleared.  For designs created with v5.1 or earlier, this option is cleared by default.

You can specify the following type of rectangles:

• Bn, Bm : n<=m will mean Bn, Bn+1, ... Bm

• Tn, Tm : n<=m will mean Tn, Tn+1, ... Tm

• Bn, Tm : n<=m will mean Bn, Tn, Bn+1,Tn+1 ... Bm, Tm

• Tn, Bm : n<=m will mean Bn, Tn, Bn+1,Tn+1 ... Bm, Tm

The following table summarizes the available spines.

Note: T1 and B1 are the leftmost top and bottom global spines, respectively.

See Also

Constraint support by family

Constraint entry table

GCF syntax conventions