Dynamic Port Handling for Isolated Modules in Reconfigurable Circuits

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The integration of partial reconfiguration and isolated module design in programmable integrated circuits faces conflicts when RM instances have different numbers of isolated modules, leading to interface mismatches and errors in conventional Electronic Design Automation tools, preventing the realization of circuit designs that rely on both technologies.

Innovation Solution

The implementation of a port clean-up technique during the development process allows for matching interfaces between RM instances with different numbers of isolated modules by removing punched ports before swapping in new RM instances, ensuring consistent interfaces and avoiding interface mismatch errors, thereby enabling the use of both partial reconfiguration and isolated module design.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If RM instances with different numbers of isolated modules are integrated into the circuit design, then adaptability and versatility are improved, but interface mismatches and errors occur leading to design failure

Engineering Contradiction:

Improveability to handle RM instances with different numbers of isolated modulesVSAvoidinterface matching between RM instances and static isolated module

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary actions by inserting static drivers and additional ports before RM instances are fully integrated. This preparatory configuration ensures that the interface structure is ready to accommodate varying numbers of isolated modules, preventing interface mismatches before they occur during dynamic reconfiguration

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Static drivers are introduced as intermediary elements between the static isolated module and RM instances. These drivers act as mediators that buffer and manage the interface connections, allowing RM instances with different numbers of isolated modules to connect reliably to the static isolated module without direct interface conflicts

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If static drivers and additional ports are inserted for each RM instance, then interface consistency is improved, but device complexity and processing time increase

Engineering Contradiction:

Improveinterface consistency across RM instancesVSAvoidnumber of static drivers and ports to be managed

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Static drivers are designed with universal functionality to handle multiple RM instances with different configurations. Rather than creating dedicated drivers for each specific RM instance configuration, the same static driver structure can serve multiple instances, reducing overall device complexity while maintaining interface consistency

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system dynamically removes static drivers and additional ports that are no longer needed when RM instances are removed or reconfigured. This recovery process eliminates unnecessary interface elements, reducing device complexity and processing overhead while maintaining interface consistency for active RM instances

Inventive Principle:

Principle #34Discarding and recovering

3Productivity

If RM instances are dynamically swapped in the PR region, then productivity and reconfigurability are improved, but interface mismatch errors prevent successful reconfiguration

Engineering Contradiction:

Improvespeed of dynamic function exchangeVSAvoidease of implementing dynamic reconfiguration with isolated modules

Core Design Contradiction:

ProductivityVSEase of manufacture

Solution Approach 1:

The system performs preliminary configuration setup by inserting static drivers and defining additional ports before RM instances are dynamically swapped. This preliminary structuring of the interface ensures that reconfiguration can proceed smoothly without interface mismatch errors, making dynamic reconfiguration easier to implement

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Static drivers serve as intermediary elements that facilitate smooth transitions during RM instance swapping. By managing the interface connections through these mediators, the system enables rapid reconfiguration while preventing interface mismatch errors that would otherwise block successful dynamic reconfiguration

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12026444B2Dynamic port handling for isolated modules and dynamic function exchange

Publication Date: 2024.07.02 XILINX INC

AI summary

Dynamic port handling for circuit designs can include inserting, within a static isolated module of a circuit design, static drivers configured to drive isolated modules of reconfigurable module (RM) instances for inclusion in an RM of the circuit design. For each RM instance of a plurality of RM instances to be inserted into the RM, one or more additional ports can be inserted in the RM based on a number of isolated modules included in a current RM instance. Further, net(s) corresponding to the additional port(s) can be created. The circuit design, including the current RM instance, the additional port(s), and the net(s), can be placed and routed. Prior to the inserting and the performing place and route for a next RM instance to be inserted into the RM, the current RM instance can be removed from the RM along with the additional port(s) and the net(s).