<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>I2c on Marcus Folkesson</title>
    <link>https://www.marcusfolkesson.se/tags/i2c/</link>
    <description>Recent content in I2c on Marcus Folkesson</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 04 Oct 2025 10:00:34 +0100</lastBuildDate>
    <atom:link href="https://www.marcusfolkesson.se/tags/i2c/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I2C Bus Recovery</title>
      <link>https://www.marcusfolkesson.se/blog/i2c-bus-recovery/</link>
      <pubDate>Sat, 04 Oct 2025 10:00:34 +0100</pubDate>
      <guid>https://www.marcusfolkesson.se/blog/i2c-bus-recovery/</guid>
      <description>I2C Bus Recovery Brief I was working on a project where we had a problem with an I2C bus that was sporadically hanging during communication with a certain device. I2C works with open-drain lines, which means that devices can only pull the lines low, and a pull-up resistor is used to pull the line high. If a device misbehaves and holds one of the lines low, the bus will be stuck, and no further communication can take place.</description>
    </item>
  </channel>
</rss>
