Port connection by name vs by position in Verilog - Visual Side-by-Side Comparison

Concept Flow - Port connection by name vs by position

Module Instantiation

↓

Connect Ports by Position

↓

Match ports in order

↓

Signals connected by order

↓

Connect Ports by Name

↓

Match ports by explicit names

↓

Signals connected by name

When instantiating a module, you can connect its ports either by listing signals in the exact order (by position) or by explicitly naming each port (by name).

Execution Sample

Verilog

module mymod(input a, input b, output c);
  assign c = a & b;
endmodule

mymod inst1(x, y, z); // by position
mymod inst2(.a(x), .b(y), .c(z)); // by name

This code shows a module with three ports and two ways to connect signals: by position and by name.

Execution Table

Step	Connection Type	Port Order	Signal Connected	Resulting Connection
1	By Position	a	x	Port 'a' connected to signal 'x'
2	By Position	b	y	Port 'b' connected to signal 'y'
3	By Position	c	z	Port 'c' connected to signal 'z'
4	By Name	a	x	Port 'a' connected to signal 'x'
5	By Name	b	y	Port 'b' connected to signal 'y'
6	By Name	c	z	Port 'c' connected to signal 'z'
7	Exit	-	-	All ports connected correctly

💡 All ports connected; instantiation complete

Variable Tracker

Port	Initial	After Inst1 (by position)	After Inst2 (by name)
a	unconnected	x	x
b	unconnected	y	y
c	unconnected	z	z

Key Moments - 3 Insights

Why is the order of signals important when connecting ports by position?

Because ports are connected in the order they are declared in the module, if the order of signals does not match, wrong signals connect to wrong ports (see execution_table rows 1-3).

Can you skip ports when connecting by position?

No, you must provide signals for all ports in order, or use default values inside the module. Named connections allow skipping ports (see execution_table rows 4-6).

Why might connecting ports by name be safer for large modules?

Because you explicitly specify which signal connects to which port, avoiding mistakes from wrong order (see variable_tracker showing consistent connections).

Visual Quiz - 3 Questions

Look at the execution_table, what signal is connected to port 'b' in instantiation by position at step 2?

A x

B z

C y

D unconnected

💡 Hint

Check execution_table row 2 under 'Signal Connected'

At which step does the connection by name assign signal 'z' to port 'c'?

A Step 6

B Step 3

C Step 5

D Step 4

💡 Hint

Look at execution_table rows 4-6 for by name connections

If you swapped signals 'x' and 'y' in the by position connection, what would happen?

A Port 'a' connects to 'x' and port 'b' connects to 'y'

B Port 'a' connects to 'y' and port 'b' connects to 'x'

C Port 'c' would be unconnected

D No change in connections

💡 Hint

Refer to execution_table rows 1-3 and how order affects connections

Concept Snapshot

Port connection in Verilog:
- By position: connect signals in the order ports are declared
- By name: connect signals explicitly using .port(signal)
- By name is safer for large modules or when skipping ports
- By position requires exact order, else wrong connections
- Both methods connect signals to module ports for instantiation

Full Transcript

This visual execution shows how Verilog module ports connect to signals either by position or by name. When connecting by position, signals must be listed in the exact order of the module's port declaration. The execution table traces each port connection step by step, showing which signal connects to which port. By name connections explicitly specify the port name with the signal, making it safer and clearer, especially for modules with many ports. The variable tracker confirms the final connections for both methods. Key moments clarify common confusions about order importance and skipping ports. The quiz tests understanding of signal-port mapping and effects of swapping signals in position-based connections.

Practice

1. What is the main difference between port connection by name and port connection by position in Verilog?

easy

A. By position allows skipping ports; by name does not allow skipping ports.

B. By position connects ports explicitly by their names; by name connects ports in the order declared.

C. By name requires fewer ports; by position requires all ports to be connected.

D. By name connects ports explicitly by their names; by position connects ports in the order declared.

Solution

1. Step 1: Understand port connection by position

   Port connection by position links signals to ports based on the order the ports are declared in the module.

2. Step 2: Understand port connection by name

   Port connection by name links signals explicitly by specifying the port names, so order does not matter.

3. Final Answer:

   By name connects ports explicitly by their names; by position connects ports in the order declared. -> Option D

4. Quick Check:

   Port connection by name = explicit naming [OK]

Hint: Remember: name = explicit, position = order [OK]

Common Mistakes:

• Confusing order with explicit naming
• Thinking by position allows skipping ports
• Assuming by name requires fewer ports

2. Which of the following is the correct syntax for connecting ports by name in Verilog?

easy

A. module_name (input_signal, output_signal);

B. module_name (.port1(input_signal), .port2(output_signal));

C. module_name {port1: input_signal, port2: output_signal};

D. module_name -> (port1=input_signal, port2=output_signal);

Solution

1. Step 1: Recall named port connection syntax

   Named connections use dot notation: .port_name(signal_name).

2. Step 2: Match syntax options

   module_name (.port1(input_signal), .port2(output_signal)); matches the correct syntax: module_name (.port1(input_signal), .port2(output_signal));

3. Final Answer:

   module_name (.port1(input_signal), .port2(output_signal)); -> Option B

4. Quick Check:

   Named ports use dot and parentheses [OK]

Hint: Named ports use dot before port name [OK]

Common Mistakes:

• Using commas without dots for named ports
• Using braces or arrows which are invalid
• Confusing named and positional syntax

3. Given the module declaration:

module my_module(input a, input b, output c);

Which instantiation will correctly connect signals x, y, and z by position?

medium

A. my_module instance1 (.a(x), .b(y), .c(z));

B. my_module instance1 (z, y, x);

C. my_module instance1 (x, y, z);

D. my_module instance1 (.c(z), .b(y), .a(x));

Solution

1. Step 1: Understand port order in module

   The ports are declared in order: a, b, c.

2. Step 2: Match signals by position

   By position, the first signal connects to 'a', second to 'b', third to 'c'. So (x, y, z) matches correctly.

3. Final Answer:

   my_module instance1 (x, y, z); -> Option C

4. Quick Check:

   Position order = a=x, b=y, c=z [OK]

Hint: Position order matches port declaration order [OK]

Common Mistakes:

• Swapping signal order in positional connection
• Using named syntax but calling it positional
• Connecting signals in wrong order

4. Identify the error in this module instantiation:

my_module instance1 (x, .b(y), z);

Assuming my_module ports are a, b, c in order.

medium

A. Mixing positional and named connections is not allowed.

B. The named connection .b(y) is correct here.

C. The order of signals is correct for positional connection.

D. No error; this is valid syntax.

Solution

1. Step 1: Check connection styles used

   The instantiation mixes positional (x, z) and named (.b(y)) connections.

2. Step 2: Recall Verilog rules on mixing connections

   Verilog does not allow mixing positional and named port connections in the same instantiation.

3. Final Answer:

   Mixing positional and named connections is not allowed. -> Option A

4. Quick Check:

   Mixing connection styles = error [OK]

Hint: Do not mix named and positional in one instantiation [OK]

Common Mistakes:

• Thinking mixed connections are allowed
• Ignoring order importance in positional connections
• Assuming named connections can appear anywhere

5. You have a module with ports declared as (input clk, input reset, output reg done). You want to instantiate it with signals clk_sig, rst_sig, and done_sig. Which instantiation style is safer and why?

hard

A. By name, because it explicitly connects signals to ports regardless of order.

B. By position, because it is shorter and easier to write.

C. By position, because it allows skipping some ports.

D. By name, because it automatically matches signals by data type.

Solution

1. Step 1: Consider risks of positional connection

   Positional connection depends on port order; if order changes, connections break.

2. Step 2: Consider benefits of named connection

   Named connection explicitly links signals to port names, so order changes do not cause errors.

3. Final Answer:

   By name, because it explicitly connects signals to ports regardless of order. -> Option A

4. Quick Check:

   Named connection = safer for clarity [OK]

Hint: Use named ports to avoid order mistakes [OK]

Common Mistakes:

• Assuming positional is always simpler and safer
• Thinking named connection matches by data type
• Believing positional allows skipping ports