TIMING-54: Scoped False Path, Clock Group, or Max Delay Datapath Only Constraint between Clocks - 2022.2 English

TIMING-54: Scoped False Path, Clock Group, or Max Delay Datapath Only Constraint between Clocks - 2022.2 English - UG906

Vivado Design Suite User Guide: Design Analysis and Closure Techniques (UG906)

Document ID

UG906

Release Date

2022-10-19

Version

2022.2 English

A scoped <message_string> timing constraint is set between clocks <clock_group> and <clock_group> (see the constraint position <message_string> in the Timing Constraint window in the Vivado IDE). It is not recommended to define such scoped constraints between clocks because the constraint impacts timing paths outside of the scope.