Configuration declaration in VHDL - Step-by-Step Execution

Concept Flow - Configuration declaration

Start Configuration Declaration

↓

Specify Entity and Architecture

↓

Map Components to Architectures

↓

Apply Configuration to Design

↓

End

The configuration declaration links an entity to a specific architecture and component implementations, defining how the design is built.

Execution Sample

VHDL

configuration cfg_example of my_entity is
  for arch_example
    for comp1: component1 use entity work.comp1(arch1);
    end for;
  end for;
end cfg_example;

This configuration binds 'my_entity' to 'arch_example' and maps 'comp1' to a specific component architecture.

Execution Table

Step	Action	Entity/Architecture	Component Mapping	Result
1	Start configuration declaration	my_entity	None	Configuration 'cfg_example' begins
2	Specify architecture for entity	my_entity / arch_example	None	Architecture 'arch_example' selected
3	Map component 'comp1'	my_entity / arch_example	comp1 -> work.comp1(arch1)	Component 'comp1' mapped to 'arch1'
4	End component mapping	my_entity / arch_example	comp1 -> work.comp1(arch1)	Component mapping complete
5	End configuration declaration	my_entity / arch_example	comp1 -> work.comp1(arch1)	Configuration 'cfg_example' completed

💡 Configuration declaration ends after all components are mapped and architecture specified

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
Entity	None	my_entity	my_entity	my_entity
Architecture	None	arch_example	arch_example	arch_example
Component Mapping	None	None	comp1 -> work.comp1(arch1)	comp1 -> work.comp1(arch1)

Key Moments - 2 Insights

Why do we specify an architecture inside the configuration?

Because the configuration links the entity to a specific architecture to define which implementation to use, as shown in step 2 of the execution table.

What does the component mapping inside the configuration do?

It tells the design which specific component architecture to use for each component instance, as shown in step 3 where 'comp1' is mapped to 'arch1'.

Visual Quiz - 3 Questions

Look at the execution table, what is the component mapping after step 3?

A comp1 -> work.comp1(arch_example)

B None

C comp1 -> work.comp1(arch1)

D comp1 -> work.comp2(arch1)

💡 Hint

Check the 'Component Mapping' column at step 3 in the execution table

At which step does the configuration declaration end?

A Step 4

B Step 5

C Step 3

D Step 2

💡 Hint

Look at the 'Step' and 'Result' columns to find when configuration completes

If we remove the component mapping, what would the 'Component Mapping' be after step 3?

A None

B comp1 -> work.comp1(arch1)

C comp1 -> work.comp1(arch_example)

D comp1 -> work.comp2(arch1)

💡 Hint

Refer to the variable_tracker for 'Component Mapping' when no mapping is done

Concept Snapshot

Configuration declaration syntax:
configuration <name> of <entity> is
  for <architecture>
    for <component_label>: <component_name> use entity <library>.<component_name>(<architecture>);
    end for;
  end for;
end <name>;

It binds an entity to an architecture and maps components to specific implementations.

Full Transcript

A configuration declaration in VHDL connects an entity to a chosen architecture and specifies which component implementations to use. The process starts by declaring the configuration name and the entity it applies to. Then, inside the configuration, you specify the architecture for the entity. Next, you map each component instance to a particular component architecture. Finally, the configuration declaration ends, completing the binding. This allows you to control which versions of components and architectures are used in your design without changing the entity or architecture code itself.

Practice

1. What is the main purpose of a configuration declaration in VHDL?

easy

A. To specify timing constraints for simulation

B. To declare signals inside an architecture

C. To define new data types

D. To select which architecture is used for a component instance

Solution

1. Step 1: Understand the role of configuration declarations

   Configuration declarations in VHDL are used to specify which architecture should be bound to a component instance.

2. Step 2: Compare with other options

   Declaring signals, defining data types, or specifying timing constraints are done elsewhere, not in configurations.

3. Final Answer:

   To select which architecture is used for a component instance -> Option D

4. Quick Check:

   Configuration = Architecture selection [OK]

Hint: Configurations pick architectures for components quickly [OK]

Common Mistakes:

• Confusing configuration with signal declaration
• Thinking configuration defines data types
• Assuming configuration sets timing constraints

2. Which of the following is the correct syntax to start a configuration declaration in VHDL?

easy

A. configuration ConfigName for EntityName is

B. config ConfigName for EntityName begin

C. config ConfigName of EntityName begin

D. configuration ConfigName of EntityName is

Solution

1. Step 1: Recall VHDL configuration syntax

   The correct syntax starts with the keyword configuration, followed by the configuration name, then for, then the entity name, and ends with is.

2. Step 2: Match options with correct syntax

   configuration ConfigName for EntityName is matches exactly: configuration ConfigName for EntityName is. Others use incorrect keywords or order.

3. Final Answer:

   configuration ConfigName for EntityName is -> Option A

4. Quick Check:

   Syntax = configuration ... for ... is [OK]

Hint: Use 'configuration Name for Entity is' to start [OK]

Common Mistakes:

• Using 'of' instead of 'for'
• Omitting 'is' keyword
• Using 'config' instead of 'configuration'

3. Given the following VHDL configuration snippet:

configuration CFG1 for MyEntity is
  for ARCH1
    for U1: MyComponent
      use entity work.MyComponent(ARCH2);
    end for;
  end for;
end CFG1;

What architecture is used for the component instance U1 inside MyEntity when CFG1 is applied?

medium

A. ARCH1

B. MyEntity

C. ARCH2

D. work.MyComponent

Solution

1. Step 1: Analyze the configuration binding

   The configuration CFG1 binds the architecture ARCH1 to MyEntity. Inside ARCH1, the component instance U1 is explicitly bound to the architecture ARCH2 of MyComponent.

2. Step 2: Identify the architecture used for U1

   Because of the line use entity work.MyComponent(ARCH2);, U1 uses ARCH2, not ARCH1 or the entity name.

3. Final Answer:

   ARCH2 -> Option C

4. Quick Check:

   Instance U1 uses ARCH2 architecture [OK]

Hint: Look for 'use entity ... (ARCH)' inside configuration [OK]

Common Mistakes:

• Assuming U1 uses ARCH1 because of outer for
• Confusing entity name with architecture
• Ignoring nested 'use entity' clause

4. Identify the error in this VHDL configuration declaration:

configuration CFG2 for MyEntity is
  for ARCH1
    for U1: MyComponent
      use entity work.MyComponent(ARCH2)
    end for;
  end for;
end CFG2;

medium

A. Wrong keyword 'for' instead of 'of' in configuration header

B. Missing semicolon after 'use entity' statement

C. Component instance name 'U1' is invalid

D. Entity name 'MyEntity' is missing

Solution

1. Step 1: Check syntax of 'use entity' statement

   In VHDL configurations, each statement must end with a semicolon. The line use entity work.MyComponent(ARCH2) is missing a semicolon.

2. Step 2: Verify other parts

   The configuration header uses correct keywords, the instance name U1 is valid, and the entity name MyEntity is present.

3. Final Answer:

   Missing semicolon after 'use entity' statement -> Option B

4. Quick Check:

   Statements end with semicolon [OK]

Hint: Check semicolons after each statement in configuration [OK]

Common Mistakes:

• Omitting semicolon after 'use entity' line
• Confusing 'for' and 'of' keywords
• Assuming instance names must be uppercase

5. You have two architectures for an entity Processor: FastArch and SafeArch. You want to create a configuration that uses FastArch by default but switches to SafeArch for the component instance ALU inside Processor. Which configuration declaration correctly implements this?

hard

A. configuration CFG for Processor is
for FastArch
for ALU: ALUComponent
use entity work.ALUComponent(SafeArch);
end for;
end for;
end CFG;

B. configuration CFG for Processor is
for FastArch
for ALU: ALUComponent
use entity work.Processor(SafeArch);
end for;
end for;
end CFG;

C. configuration CFG for Processor is
for SafeArch
for ALU: ALUComponent
use entity work.ALUComponent(FastArch);
end for;
end for;
end CFG;

D. configuration CFG for Processor is
for FastArch
for ALU: Processor
use entity work.ALUComponent(SafeArch);
end for;
end for;
end CFG;

Solution

1. Step 1: Understand the requirement

   The configuration should use FastArch for Processor by default, but for the component instance ALU of type ALUComponent, it should use SafeArch.

2. Step 2: Check each option

   configuration CFG for Processor is for FastArch for ALU: ALUComponent use entity work.ALUComponent(SafeArch); end for; end for; end CFG; correctly binds FastArch to Processor and overrides ALU instance to use SafeArch architecture of ALUComponent. configuration CFG for Processor is for FastArch for ALU: ALUComponent use entity work.Processor(SafeArch); end for; end for; end CFG; incorrectly tries to bind SafeArch to Processor entity instead of ALUComponent. configuration CFG for Processor is for SafeArch for ALU: ALUComponent use entity work.ALUComponent(FastArch); end for; end for; end CFG; reverses the default and override. configuration CFG for Processor is for FastArch for ALU: Processor use entity work.ALUComponent(SafeArch); end for; end for; end CFG; incorrectly uses ALU instance as Processor type.

3. Final Answer:

   configuration CFG for Processor is for FastArch for ALU: ALUComponent use entity work.ALUComponent(SafeArch); end for; end for; end CFG; -> Option A

4. Quick Check:

   Default architecture + instance override = configuration CFG for Processor is for FastArch for ALU: ALUComponent use entity work.ALUComponent(SafeArch); end for; end for; end CFG; [OK]

Hint: Override instance architecture with 'use entity work.Component(Arch)' [OK]

Common Mistakes:

• Binding wrong entity in 'use entity' clause
• Swapping default and override architectures
• Using instance name as entity type