<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>I2c on Christian Gmeiner</title>
    <link>https://playground.christian-gmeiner.info/tags/i2c/</link>
    <description>Recent content in I2c on Christian Gmeiner</description>
    <image>
      <title>Christian Gmeiner</title>
      <url>https://playground.christian-gmeiner.info/papermod-cover.png</url>
      <link>https://playground.christian-gmeiner.info/papermod-cover.png</link>
    </image>
    <generator>Hugo -- 0.152.2</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 Feb 2013 10:54:30 +0000</lastBuildDate>
    <atom:link href="https://playground.christian-gmeiner.info/tags/i2c/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SMBus Compatibility With an I²C Device</title>
      <link>https://playground.christian-gmeiner.info/2013-02-23-smbus-compatibility-with-an-i-c2-b2c-device/</link>
      <pubDate>Sat, 23 Feb 2013 10:54:30 +0000</pubDate>
      <guid>https://playground.christian-gmeiner.info/2013-02-23-smbus-compatibility-with-an-i-c2-b2c-device/</guid>
      <description>&lt;p&gt;Some naive guys – like me – think that SMBus and I²C are equal expect the bus level. But in the last days I run into a problem where an at24 based EEPROM connected via SMBus triggers a bus collision after a warm reboot. After some hours of debugging – even staring minutes at a oscilloscope showing SDD and SDC lines – I started to add some dump_stack() calls into i2c_core.c file form a recent linux kernel. And I found the bad bus transaction – i2c_probe_func_quick_read(..).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
