Browse Prior Art Database

IIC Multi-Master Identification Protocol On Redundant IIC Devices

IP.com Disclosure Number: IPCOM000020335D
Original Publication Date: 2003-Nov-13
Included in the Prior Art Database: 2003-Nov-13
Document File: 2 page(s) / 45K

Publishing Venue

IBM

Abstract

Technique for identifying and routing command/response type transactions in complex systems over an industry standard IIC (Inter-IC) I/O bus.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 78% of the total text.

Page 1 of 2

IIC Multi-Master Identification Protocol On Redundant IIC Devices

Disclosed is a technique for providing a master device identifier for command/response type transactions over an industry standard IIC (Inter-IC) I/O bus. Such a IIC master identifier is particularly advantageous in complex systems where multiple IIC agents communicate and act as both IIC masters and IIC slaves on the same IIC bus. Such a system is represented in Fig. 1.

In such a system, communications between IIC agents typically involves one agent mastering the IIC bus and sending a command (message) to another IIC agent acting as an IIC slave. Subsequently the targeted IIC slave agent would respond by mastering the IIC bus and sending a response (message) back to the original IIC agent which sent it the command. The problem is that the industry standard IIC protocol has no means of identifying the master agent on an IIC bus transaction so the responding agent does not know to which IIC agent it should address its response to.

The industry standard IIC protocol provides for transmission of a packet comprised of a start delimiter, a target address, a variable length message, and a stop delimiter (see Fig.2).

The solution to this problem is to provide as IIC master device identifier as part of the variable length message portion of an IIC transaction (see Fig. 3).

This IIC master device identifier could (but is not restricted to) include the master device type and the master's corresponding slave...