Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: update LowskewManagement removing BD local_lowskew + replace BD by GCK for NG-ULTRA

...

  • Using a low-skew dedicated complex pad (highly recommended)

  • Using a simple/complex pad and buffer in global_lowskew modeUsing a simple/complex pad and buffer in local_lowskew modeCommon to System Converter (CSC)

  • Using a simple/complex pad connected to a WFG (not recommended)

Using low-skew dedicated pads reduces clock skew delays in order to reach best performances during Static Timing Analysis.

Global_lowskew mode has to be used in case of registers from different tiles are on low-skew signal destination. Otherwise, if registers are in the same tile, it is enough to use local_lowskew For NG-MEDIUM/NG-LARGE, CSC is instantiated thanks to NX_BD in global_lowskew mode.

For NG-ULTRA, CSC is instantiated thanks to NX_GCK in CSC mode.

Environment:

Here after the table of compliances for this testcase.

Variant

NG-MEDIUM NG-LARGE NG-ULTRA

Embedded

No

Simulation

No

Attributes

 

IP

NX_BD NX_GCK NX_WFG

Methods

addModule createRegion confineModule

Table: Design LowskewManagement environment

...

NanoXmap check: After project launching, the user can check in progresslowskew.rpt that 2 clock buffers and 2 WFG are counted. Routing ways are observable in the GUI.

...

 

Simulation check: No simulation environment is available for this testcaseand in the GUI that clocks are inserted in the lowskew through multiple ways.

 

...

Simulation check: Clocks go through different ways without impact.

 

Board check: No board purpose for this testcase.

...