You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
To satisfy the growing demands in corner case evaluation during sign-off, various FPGA bitstreams are required, each of which represents an unique configuration. Note that these configurations cannot be merged, as the same paths in an FPGA are required to be enabled or disabled, representing two operating modes.
Also, these configurations are not synthesizable or consume a lot of effort to develop HDL designs that can result in the desired bitstream.
Clock network is such a case which requires very intensive efforts during sign-off. Engineers may wish to turn on all or part of the clock paths, to check setup/hold time. When there are multiple clocks, engineers have to check the performance of each clock.
Even though the existing command route_clock_rr_graph by default route all the clocks in the global network. It does not enable the clock tap multiplexer (See the green line in the figure below) unless it is mapped. Therefore, we need a dedicated feature to force enabling the clock tap multiplexer.
Describe the solution you'd like
Add a new syntax clock_routing to the bitstream setting file, which allows user to select which clock is selected to propagate at the tap point. Note that
Is your feature request related to a problem? Please describe.
To satisfy the growing demands in corner case evaluation during sign-off, various FPGA bitstreams are required, each of which represents an unique configuration. Note that these configurations cannot be merged, as the same paths in an FPGA are required to be enabled or disabled, representing two operating modes.
Also, these configurations are not synthesizable or consume a lot of effort to develop HDL designs that can result in the desired bitstream.
Clock network is such a case which requires very intensive efforts during sign-off. Engineers may wish to turn on all or part of the clock paths, to check setup/hold time. When there are multiple clocks, engineers have to check the performance of each clock.
Even though the existing command
route_clock_rr_graph
by default route all the clocks in the global network. It does not enable the clock tap multiplexer (See the green line in the figure below) unless it is mapped. Therefore, we need a dedicated feature to force enabling the clock tap multiplexer.Describe the solution you'd like
Add a new syntax
clock_routing
to the bitstream setting file, which allows user to select which clock is selected to propagate at the tap point. Note thatFor example,
The
network
andpin
correspond to the clock networkname
and a valid pin ofglobal_port
in the clock network description.The text was updated successfully, but these errors were encountered: