Hot I2C–I3C Protocol Transition by Slave-Address Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies lack efficient methods for transitioning between I2C and I3C communication protocols without requiring reset protocols, handshake protocols, or waiting periods, which is necessary for hybrid implementations supporting both I2C and I3C devices on the same communication bus.
Innovation Solution
A system and method that allows controller devices and target devices to transition seamlessly between I2C and I3C communication protocols by determining the appropriate protocol based on a slave address, using an address table to identify the communication protocol, and enabling direct hardware reading and firmware communication without additional interrupts or resets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If reset protocols, handshake protocols, or waiting periods are implemented for transitioning between I2C and I3C protocols, then communication reliability is improved, but communication speed and system responsiveness deteriorate
Solution Approach 1:
The system performs preliminary protocol identification by examining the slave address before actual data transfer begins. The controller device determines whether I2C or I3C protocol should be used based on the slave address matching against stored addresses, allowing the system to prepare the appropriate protocol configuration in advance without requiring reset or handshake procedures during the transition.
2Stability of the object's composition
If protocol transition procedures (reset, handshake, waiting periods) are implemented, then communication stability is improved, but system complexity and operation time increase
Solution Approach 1:
The controller device maintains a stored set of slave addresses associated with specific protocols, allowing it to determine the appropriate protocol before communication begins. This preliminary configuration eliminates the need for complex runtime protocol transition procedures, reducing both operational complexity and time requirements while maintaining stable communication.
3Reliability
If protocol transition procedures are implemented, then communication reliability is improved, but productivity and time efficiency deteriorate
Solution Approach 1:
The system pre-configures protocol information based on slave addresses stored in the controller device. When a communication request is initiated, the controller quickly determines the appropriate protocol by comparing the target slave address against stored addresses, enabling immediate protocol selection without time-consuming transition procedures, thereby maintaining high productivity while ensuring reliable communication.
4Speed
If I3C protocol is used for higher speed communication, then communication speed is improved, but compatibility with legacy I2C devices deteriorates
Solution Approach 1:
The system dynamically selects between I2C and I3C protocols based on the specific slave address being accessed. The controller device examines the slave address in real-time and determines whether to use I2C or I3C protocol accordingly, allowing the system to achieve high-speed I3C communication with compatible devices while maintaining backward compatibility with legacy I2C devices through protocol adaptation.
Solution Approach 2:
The system changes the communication protocol parameter based on the slave address. By storing specific slave addresses associated with I3C capability and comparing incoming addresses against this stored set, the system dynamically adjusts the protocol parameter to optimize communication speed for I3C devices while maintaining compatibility with I2C devices.
Data Source
AI summary
A system includes a communication bus, a controller device, and a target device. The controller device and the target device may transition between different communication protocols in association with transferring data over the communication bus. The target device may receive a transaction command including a slave address. Based on the slave address, the target device may determine a communication protocol associated with transferring data in association with the transaction command. A first communication protocol may include a message protocol, and the message protocol may be associated with an I2C communication protocol or an I3C communication protocol. The second communication protocol may include a bus protocol, and the bus protocol may be associated with the I2C communication protocol.