Multichip Timing Synchronization via Hardware Software Counter Alignment

Solution Overview

Problem

In electronic systems, multichip synchronization is challenging due to clock cycle drift, leading to loss of common time base and potential system failures, especially when latency and jitter impact data communications across high-speed interfaces.

Innovation Solution

The implementation of synchronized hardware and software counters across multiple systems, where hardware counters are periodically synchronized and software counters are adjusted based on timing markers to maintain alignment, ensuring stable interactions and data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If hardware counters are periodically synchronized across multiple systems, then synchronization reliability is improved, but communication latency and jitter increase

Engineering Contradiction:
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary synchronization actions by having each system count and record timing markers locally before actual data exchange occurs. This pre-counting of timing markers allows the systems to establish synchronized timing bases in advance, reducing the impact of subsequent communication latency and jitter on synchronization reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where timing markers are exchanged between systems and processed to generate adjustment signals. These feedback signals allow the systems to continuously adjust their counters to maintain synchronization despite varying communication conditions, thereby improving reliability while managing latency effects.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If software counters are adjusted based on timing markers to maintain alignment, then synchronization precision is improved, but system complexity increases

Engineering Contradiction:
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The synchronization system is segmented into distinct functional components: hardware counters for coarse timing, software counters for fine timing adjustment, and timing marker processing units. This segmentation allows each component to perform its specific function with optimized complexity, achieving high timing precision while keeping individual module complexity manageable through clear functional separation.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If multiple systems operate with independent clock cycles, then system independence is improved, but time base alignment deteriorates

Engineering Contradiction:
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The system employs dynamic adjustment mechanisms where software counters continuously adapt to timing variations between independent clock cycles. By dynamically adjusting counter values based on recorded timing markers and received feedback signals, the system maintains time base alignment while preserving the independence of each system's clock operation, thus resolving the contradiction between system independence and time base stability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11474557B2Multichip timing synchronization circuits and methods
Publication Date: 2022.10.18
  • US11474557B2 patent drawing
  • US11474557B2 patent drawing
  • US11474557B2 patent drawing

AI summary

In one embodiment, the present disclosure includes multichip timing synchronization circuits and methods. In one embodiment, hardware counters in different systems are synchronized. Programs on the systems may include synchronization instructions. A second system executes synchronization instruction, and in response thereto, synchronizes a local software counter to a local hardware counter. The software counter on the second system may be delayed a fixed period of time corresponding to a program delay on the first system. The software counter on the second system may further be delayed by an offset to bring software counters on the two systems into sync.