The browser version you are using is not recommended for this site.Please consider upgrading to the latest version of your browser by clicking one of the following links.
We are sorry, This PDF is available in download format only
Interfacing I²C* Devices to SMBus ControllerExecutive SummaryIntel includes one or more SMBus controllers as part of their chipset devices. Its primary purpose is to permit the chipset to communicate with SMBus devices such as the SPD EEPROMs* on the DIMMs, the clock driver, and various temperature sensors. Some designs incorporate I2C* slave devices on the SMBus. Being "similar" to the I2C bus, it is often difficult to program the Intel® I/O Controller Hub (ICH) SMBus controller to reliably communicate with these I2C slave devices.The purpose of this paper is to provide details on the various SMBus cycles that the Intel ICH SMBus controller can create, and then to provide guidelines on how to "analyze" the cycles supported by I2C devices to see if they can be successfully accessed by the Intel ICH SMBus controller.It is important to realize that sometimes it is not possible to program the SMBus controller's basic cycles to communicate with a given I2C device. The judicious use of the various blocks modes when combined with the setting of an "I2C Enable" bit (I2C_EN) (which changes the format of the some of the cycles slightly) often permits the Intel ICH SMBus controller to communicate successfully with I2C devices.Read the full Interfacing I²C* Devices to SMBus Controller White Paper.
Discusses virtualization advances in hardware, technology, and platform consolidation.
Explains virtualization fundamentals, business impact, industry factors, model comparisons, and more.
Explores Intel® Virtualization Technology, how it works, and common virtualization techniques.
Demonstrates attachment of strain gauges to measure manufacturing board flexure. (v.1, Jan. 2011)
Demonstrates how to use a USB drive to boot a customer reference board to DOS. (v.1, June 2010)
Demos setup, software, oscilloscope settings, and power delivery assessments. (v.001, Mar. 2010)