I2C Bus Failure Detection and Multi-Master Reconfiguration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

I2C bus failures in computer systems cause disruptions and require significant resource allocation, as existing methods lack effective detection, failover, and masking mechanisms, leading to non-recoverable errors and performance degradation.

Innovation Solution

A method for detecting I2C bus failures, reconfiguring a remaining bus as multi-mastered, and masking the failed bus to ensure continuous bi-directional communication, using data fields to indicate bus states and message counts, and implementing software to isolate and recover the failed bus without additional resource expenditure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If retry connection is used when master device does not receive response from slave device, then simple error handling is achieved, but system disruption increases and reliability decreases

Engineering Contradiction:
Improveerror handling simplicityVSAvoidsystem reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments error handling into distinct phases: detection phase (monitoring communication status), isolation phase (identifying failed bus), and recovery phase (switching to backup bus). This segmentation allows complex reliability measures to be implemented without increasing operational complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by pre-configuring backup communication paths and establishing failure detection mechanisms before failures occur. When a bus fails, the system can immediately switch to the pre-prepared backup bus, avoiding system disruption without requiring complex real-time decision-making.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If I2C failure detection and isolation mechanisms are implemented, then system reliability improves, but device complexity increases

Engineering Contradiction:
Improvecommunication reliabilityVSAvoidbus management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service through automatic failure detection and isolation mechanisms that operate without external intervention. The bus management software automatically monitors communication status, detects failures, isolates failed buses, and switches to backup buses, eliminating the need for manual intervention while maintaining simplicity.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The bus management software performs multiple functions: it manages normal I2C communication, detects failures, isolates failed buses, and controls backup bus switching. By consolidating these functions into a single universal software module, the system achieves high reliability without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If backup I2C bus switching is implemented upon failure detection, then system availability improves, but message transmission delays may occur

Engineering Contradiction:
Improvesystem availabilityVSAvoidmessage transmission delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-establishing backup communication paths and pre-configuring bus switching capabilities. When a failure is detected, the switch to the backup bus is immediate, minimizing transmission delays while ensuring continuous availability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system maintains continuity of useful action by ensuring that communication never stops during bus failures. The automatic switching mechanism ensures that message transmission continues uninterrupted on the backup bus, eliminating delays while maintaining high availability.

Inventive Principle:
Principle #20Continuity of useful action

4Productivity

If comprehensive failure detection and masking mechanisms are implemented, then productivity is maintained, but resource allocation increases

Engineering Contradiction:
Improvesystem productivityVSAvoidcomputing resources
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The bus management software operates autonomously, automatically detecting failures, isolating failed buses, and switching to backup buses without requiring additional computing resources for manual intervention. This self-service approach maintains productivity while minimizing resource consumption.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The bus management software consolidates multiple functions (detection, isolation, switching, and masking) into a single universal module, avoiding the need for separate resource-intensive mechanisms for each function. This maintains productivity while optimizing resource allocation.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7721155B2I2C failure detection, correction, and masking
Publication Date: 2010.05.18 X CORP
  • US7721155B2 patent drawing
  • US7721155B2 patent drawing
  • US7721155B2 patent drawing

AI summary

A method of operation of a computer system having a master and slave Inter-IC (I2C) bus network includes detecting and isolating an I2C bus failure, configuring a failed I2C bus as offline, reconfiguring a remaining I2C bus as a multi-mastered bus, and masking the failed I2C bus from operation until the failed I2C bus can be repaired. A first test request is sent to a remote device from a local device. If the remote device receives the first test request, a remote bus mode is switched to a failure position, a local bus mode is switched to a multi-master position, and a second request is sent to the remote device to indicate position changes.