From 4c36b384d03dc4937b1c97074793dc5a34812c40 Mon Sep 17 00:00:00 2001 From: tangxifan Date: Tue, 26 Nov 2024 17:26:30 -0800 Subject: [PATCH] [doc] add new syntax --- .../manual/file_formats/bitstream_setting.rst | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/docs/source/manual/file_formats/bitstream_setting.rst b/docs/source/manual/file_formats/bitstream_setting.rst index 7cc340da0..12094fea0 100644 --- a/docs/source/manual/file_formats/bitstream_setting.rst +++ b/docs/source/manual/file_formats/bitstream_setting.rst @@ -14,6 +14,7 @@ This can define a hard-coded bitstream for a reconfigurable resource in FPGA fab + @@ -104,6 +105,33 @@ The following syntax are applicable to the XML definition tagged by ``interconne The default path can be either ``iopad.inpad`` or ``ff.Q`` which corresponds to the first input and the second input respectively. +Clock Routing-related Settings +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +The following syntax are applicable to the XML definition tagged by ``clock_routing`` in bitstream setting files. +This is to force the routing for clock tap multiplexers (green line in :numref:`fig_prog_clock_network_example_2x2`) even when they are not used/mapped. If no specified, only the used clock tap multiplexers will be configured to propagate clock signals. + +.. option:: network="" + + The ``network`` name to be constrained, which should be a valid name defined in the clock network file (See details in :ref:`file_formats_clock_network`). For example, + +.. code-block:: xml + + + + +The network and pin correspond to the clock network name and a valid pin of ``global_port`` in the clock network description. + +.. code-block:: xml + + + + +.. option:: pin="" + + The pin should be a valid pin of the ``global_port`` that is defined in the clock network description under the selected clock network. + + non_fabric-related Settings ^^^^^^^^^^^^^^^^^^^^^^^^^^^