--connectivity Options - --connectivity Options - 2026.1 English - UG1702

--connectivity.region

--connectivity.region <arg>

Use this option to specify an affinity for a PL kernel to a PFM.REGION declared in the extensible .xsa hardware platform. The typical use of a PFM.REGION declaration is to match a Pblock defined in the hardware platform. An example is to demarcate a Super Logic Region (SLR) within a Stacked Silicon Interconnect (SSI) device such as an xcvp2802 SoC.

You must use a separate --connectivity.region option to map each compute unit to a particular region. The build process automatically places any compute unit that you do not explicitly map to a region through the --connectivity.region option in an available region.

Valid values include:

<region_label>:<cu_name>

Where:

• <region_label> is the string identifier that you specify in the platform's PFM.REGION attribute for the target SLR or logical region.
• <cu_name> is the name of the compute unit that you specify in the --connectivity.nk option. This defaults to <kernel_name>_1 unless you specify a different name.

In the linker configuration file, you specify the region assignment as follows:

[connectivity]
region=<region_label>:<cu_name_1>,<cu_name_2>

--connectivity.nk

--connectivity.nk <arg>

Where you specify <arg> as <kernel_name>:#:<cu_name1>,<cu_name2>,...<cu_name#>.

This instantiates the specified number of instances ('compute units') of the specified kernel (kernel_name) in the generated FPGA binary (.xclbin) file during the linking process. The cu_name is optional. If you do not specify cu_name, the instances of the kernel are numbered kernel_name_1, kernel_name_2, and so forth. By default, the Vitis compiler instantiates one compute unit for each kernel.

For example:

v++ --link --connectivity.nk vadd:3:vadd_A,vadd_B,vadd_C

[connectivity]
nk=vadd:3:vadd_A,vadd_B,vadd_C

--connectivity.stream_connect

--connectivity.sc <arg>

Create a streaming connection between two compute units through their AXI4-Stream interfaces. Use a separate --connectivity.sc option for each streaming interface connection. The order of connection must be from a streaming output port of the first kernel to a streaming input port of the second kernel. Valid values include:

<cu_name>.<streaming_output_port>:<cu_name>.<streaming_input_port>[:<fifo_depth>]

Where:

• <cu_name> is the compute unit name specified in the --connectivity.nk option. Generally, this is <kernel_name>_1 unless you specify a different name.
• <streaming_output_port>/<streaming_input_port> is the function argument for the compute unit port you declare as AXI4-Stream.
• [:<fifo_depth>] inserts a FIFO of the specified depth between the two streaming ports to prevent stalls. Specify this value as an integer.

For example, connect the AXI4‑Stream port s_out of compute unit mem_read_1 to s_in of increment_1 as follows.

--connectivity.sc mem_read_1.s_out:increment_1.s_in

[connectivity]
sc=mem_read_1.s_out:increment_1.s_in

The inclusion of the optional <fifo_depth> value lets the v++ linker add a FIFO between the two kernels to help prevent stalls. This uses BRAM resources from the device when specified, but eliminates the need to update the HLS kernel to contain FIFOs. The tool also instantiates a Clock Converter (CDC) or Datawidth Converter (DWC) IP if the connections have different clocks, or different bus widths.

--connectivity.system_port

--connectivity.sp <arg>

Use this option to specify the assignment of kernel arguments to system ports within the platform. A primary use case for this option is to connect kernel arguments to specific memory resources. Vitis requires a separate --connectivity.sp option to map each argument of a kernel to a memory resource. Any argument not mapped to a memory resource through --connectivity.sp automatically connects to available memory resource during the build process.

Valid values include:

<cu_name>.<kernel_argument_name>:<sptag[min:max]>

Where:

• <cu_name> is the name of the compute unit as specified in the --connectivity.nk option. Generally this is <kernel_name>_1 unless a different name was specified.
• <kernel_argument_name> is the name of the function argument for the kernel, or the compute unit interface port.
• <sptag> represents a system port tag, such as for memory controller interface names from the target platform. Valid <sptag> names include DDR, PLRAM, and HBM.
• [min:max] enables the use of a range of memory, such as DDR[0:2]. You can also use a single index such as DDR[2].

The following example maps the input argument of an AI Engine GMIO to interleaved LPDDR C2_C3 on the vek385_base platform:

v++ --link -f vek385_base --connectivity.sp ai_engine_0:out_gmio:LPDDR23

[connectivity]
sp=vadd_1.A:DDR[0:3]
sp=vadd_1.B:HBM[0:31]
sp=vadd_1.C:PLRAM[2]

--connectivity.noc.connect

  --connectivity.noc.connect <arg> 

Where <arg> is in the form of <compute_unit_name>.<kernel_interface_name>:<noc interface>, and specifies a connection between the PL kernel interface and the Versal NoC. Valid values are internal memory controllers, or master interfaces on the Versal NoC cell.

The Vitis compiler estimates kernel bandwidth requirements based on NoC connectivity and M_AXI properties (datawidth * clock freq) across the dynamic region. The compiler automatically sets NoC configuration settings for read and write bandwidth. The compiler scales as needed to avoid exceeding the available bandwidth.

[connectivity]
noc.read_bw=mm2s.M_AXI:2000.16
noc.write_bw=mm2s.M_AXI:2010.16
noc.connect=mm2s.M_AXI:M00_INI

--connectivity.noc.read_bw

--connectivity.noc.read_bw <arg>

Specify <arg> in the form <compute_unit_name>.<kernel_interface_name>:<Bandwidth>.<Avg_burst_length> to set both the bandwidth and burst length of the connection. The bandwidth value is in MB/s.

Use this option to specify expected read traffic characteristics on M_AXI interfaces and to override the automatic Versal NoC configuration.

--connectivity.noc.write_bw

--connectivity.noc.write_bw <arg>

Specify <arg> in the form <compute_unit_name>.<kernel_interface_name>:<Bandwidth>.<Avg_burst_length> to set both the bandwidth and burst length of the connection. The bandwidth value is in MB/s.

Use this option to specify expected write traffic characteristics on M_AXI interfaces and to override the automatic Versal NoC configuration.

--connectivity.connect

--connectivity.connect <X:Y>

You can use this option to make connections through the Vivado IP integrator. However, v++ does not perform any error checking on the specified connections. Use this to specify general connections between kernels and non-AXI elements of the target platform, such as connections to GT ports.

src/hierarchy_name/cell_name/pin_name:dst/hierarchy_name/cell_name/pin_name

The X and Y connections cannot include connections between AXI4-Stream interfaces that require --conectivity.sc. The connections also cannot include M_AXI interfaces that require --connectivity.sp (see above).

[connectivity]
connect=<X:Y>