Bus Protocol Switching for Legacy Device Coexistence
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Legacy devices on shared I2C buses hinder the achievement of higher bandwidths due to their operational limitations, necessitating a method to selectively disable them without power cycling or bus reset to enable next-generation devices to operate at enhanced performance levels.
Innovation Solution
A system where next-generation devices can send a disable command to legacy devices on a shared bus, allowing them to enter a dormant state, and subsequently send an enable command via a secondary bus to re-enable them without power cycling, enabling higher bandwidth operations by switching between communication protocols on the same bus.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If legacy devices operate on the shared I2C bus, then backward compatibility is maintained, but bandwidth is limited
Solution Approach 1:
The bus dynamically switches between I2C mode (for legacy device compatibility) and a higher-speed mode (for increased bandwidth). The system can adapt its operating mode based on the presence and requirements of devices on the bus, allowing transition between compatibility mode and performance mode without physical reconfiguration
Solution Approach 2:
The communication protocol parameters are changed to enable higher bandwidth operation. By modifying the bus operating parameters (such as clock speed, data encoding) when in high-speed mode, the system achieves increased throughput while maintaining the ability to revert to standard I2C parameters when legacy devices are present
2Productivity
If next-generation devices use higher bandwidth protocols, then data throughput increases, but legacy devices cannot operate concurrently
Solution Approach 1:
The system introduces a temporal dimension to device coexistence by using sequential operation modes. Legacy devices and next-generation devices operate at different times on the same bus - legacy devices during I2C mode, and high-speed devices during the higher bandwidth mode. This time-based separation allows both device types to share the bus without interference
Solution Approach 2:
The bus operates dynamically in different modes depending on which devices need communication. The system can switch between I2C-compatible operation (when legacy devices are active) and high-speed operation (when only next-generation devices are present), allowing flexible adaptation to the current device composition on the bus
3Productivity
If legacy devices are power cycled to enable higher bandwidth, then bandwidth increases, but system complexity and energy consumption increase
Solution Approach 1:
Instead of power cycling legacy devices to clear the bus for high-speed operation, the system performs a preliminary disable action through software control. The legacy devices are placed in a low-power or disabled state before switching to high-speed mode, and can be re-enabled afterward without requiring full power cycles. This preliminary software-based preparation simplifies the transition process
Data Source
AI summary
A first set of devices is coupled to a first bus, a second bus, and configured to communicate over the first bus according to a first communication protocol. A second set of devices is also coupled to the first bus and configured to communicate over the first bus according to both the first communication protocol and a second communication protocol. In a first mode, the first set of devices and second set of devices may concurrently communicate over the first bus using the first communication protocol. In a second mode, the second set of devices communicate using the second communication protocol over the bus, and the first set of devices to stop operating on the first bus. An enable command is sent by at least one of the second set of devices over a second bus to cause the first set of devices to resume activity over the first bus.