I2C Slave Device Identification Coding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing I2C bus systems lack an efficient method for identifying inter-integrated circuit slave devices, which can lead to difficulties in managing and communicating with diverse slave devices from different manufacturers, especially in systems requiring specific device parameters like manufacturer, type, and revision information.
Innovation Solution
Implementing device identification coding on the I2C serial data transfer bus, where a slave device transmits a unique device identification code in response to a device identification address, allowing a master device to identify parameters such as manufacturer, part identification, and revision number, using a three-byte read-only word.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional I2C addressing is used without device identification coding, then the communication protocol remains simple, but the ability to identify and manage diverse slave devices from different manufacturers is insufficient
Solution Approach 1:
The patent applies preliminary action by implementing device identification coding during the manufacturing process, where each slave device is pre-configured with a unique identification code. This allows the master device to identify and manage diverse slave devices without adding complex communication protocols, as the identification capability is already embedded in the hardware.
Solution Approach 2:
The patent implements universality by designing a communication protocol that can handle both traditional addressing and device identification functions using the same I2C bus infrastructure. The three-byte read-only word structure allows the slave device to respond with comprehensive identification information (manufacturer, part identification, revision number) while maintaining compatibility with existing I2C communication mechanisms.
2Measurement precision
If device identification coding is implemented to identify diverse slave devices, then device identification accuracy improves, but the communication overhead and data transfer requirements increase
Solution Approach 1:
The patent applies partial action by implementing a three-byte identification code that provides sufficient identification accuracy for most applications. The identification structure includes manufacturer code (1 byte), part identification (1 byte), and revision number (1 byte), which offers comprehensive device identification without excessive data transfer requirements. This partial implementation balances identification precision with communication efficiency.
3Ease of operation
If a uniform device identification method is implemented across all slave devices, then ease of operation and device management improve, but the ability to accommodate manufacturer-specific variations may be reduced
Solution Approach 1:
The patent applies segmentation by dividing the device identification into distinct segments: manufacturer code, part identification, and revision number. This segmented structure allows for a uniform identification method that simplifies device management while simultaneously accommodating manufacturer-specific variations. Each segment can be independently configured to meet both standardized management requirements and manufacturer-specific needs.
Data Source
AI summary
Consistent with one example embodiment, communications systems, using a serial data transfer bus having a serial data line and a clock line used to implement a communications protocol, incorporate identification of inter-integrated circuit slave devices using device identification coding. The communications system includes a slave device having a device identification code identifying one or more parameters. Communications circuitry in the slave device is configured to communicate with a master device on the I2C serial data transfer bus using the communications protocol. In response to a transmission of a device identification address from the master device, the slave device is configured to transmit an ACKNOWLEDGE, and in response to a transmission of a slave device address and the device identification address from the master device, the slave device is configured to transmit the device identification code from the slave device to the master.


