<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Beaglebone Black I2C Tutorial	</title>
	<atom:link href="https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/</link>
	<description>Microcontroller Tutorials and Resources</description>
	<lastBuildDate>Sun, 15 Oct 2023 20:47:15 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>
		By: Mike		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-176520</link>

		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Wed, 28 Jul 2021 17:40:43 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-176520</guid>

					<description><![CDATA[Trying to work with i2c device and i2c-tools on beaglebone.
Need to issue general call reset according NXP&#039;s I2C documentation (UM10204) which I understand is at address 0x00 with value 0x06. 

Didn&#039;t work for me with i2cset -y -a 2  0x00 0x06

Is there a hint how to apply general reset with i2c-tools?

Thanks a lot]]></description>
			<content:encoded><![CDATA[<p>Trying to work with i2c device and i2c-tools on beaglebone.<br />
Need to issue general call reset according NXP's I2C documentation (UM10204) which I understand is at address 0x00 with value 0x06. </p>
<p>Didn't work for me with i2cset -y -a 2  0x00 0x06</p>
<p>Is there a hint how to apply general reset with i2c-tools?</p>
<p>Thanks a lot</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Raj Mehta		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-159943</link>

		<dc:creator><![CDATA[Raj Mehta]]></dc:creator>
		<pubDate>Tue, 22 Jun 2021 09:56:12 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-159943</guid>

					<description><![CDATA[Aim: Work with three I2C Slave devices.

All three devices have the same address 0x29. so differentiate slave device address need different i2c address. How to set Slave Device Address in BeagleBone Black.]]></description>
			<content:encoded><![CDATA[<p>Aim: Work with three I2C Slave devices.</p>
<p>All three devices have the same address 0x29. so differentiate slave device address need different i2c address. How to set Slave Device Address in BeagleBone Black.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: John		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-15923</link>

		<dc:creator><![CDATA[John]]></dc:creator>
		<pubDate>Sun, 04 Nov 2018 17:18:57 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-15923</guid>

					<description><![CDATA[I built a system around a BeagleBone Black Rev some time ago with the I2C bus connected to Pins P9-19 (SCL) and P9-20 (SDA). I have three or four prototypes configured that way, they all work fine and and I have not touched the I2C code for quite some time.

I recently bought another BeagleBone Black Rev C from Mouser and it was manufactured by GHI. I plugged it into an existing system and installed the SD memory from a functioning system into it and could not see any activity on the I2C bus, nothing. I Swapped it with the BBB originally in the system and that BBB worked fine. I swapped again and the new one still would not communicate over the I2C bus. I tried the new one on two other systems with the same results. I contacted GHI and the sent a replacement. It doesn&#039;t work either. Everything on these two new BBB Rev C works fine except this bus.

Since the memory os POP right on top the processor I can&#039;t tell it the processor is the same between the old BBB and the new BBB. I suspect that TI may have rev&#039;ed the silicon and this bus is no longer available on these pins.

Any one have any idea what is going on here.

thanks,
john]]></description>
			<content:encoded><![CDATA[<p>I built a system around a BeagleBone Black Rev some time ago with the I2C bus connected to Pins P9-19 (SCL) and P9-20 (SDA). I have three or four prototypes configured that way, they all work fine and and I have not touched the I2C code for quite some time.</p>
<p>I recently bought another BeagleBone Black Rev C from Mouser and it was manufactured by GHI. I plugged it into an existing system and installed the SD memory from a functioning system into it and could not see any activity on the I2C bus, nothing. I Swapped it with the BBB originally in the system and that BBB worked fine. I swapped again and the new one still would not communicate over the I2C bus. I tried the new one on two other systems with the same results. I contacted GHI and the sent a replacement. It doesn't work either. Everything on these two new BBB Rev C works fine except this bus.</p>
<p>Since the memory os POP right on top the processor I can't tell it the processor is the same between the old BBB and the new BBB. I suspect that TI may have rev'ed the silicon and this bus is no longer available on these pins.</p>
<p>Any one have any idea what is going on here.</p>
<p>thanks,<br />
john</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: navi golen		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-666</link>

		<dc:creator><![CDATA[navi golen]]></dc:creator>
		<pubDate>Fri, 13 Apr 2018 13:00:22 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-666</guid>

					<description><![CDATA[can anyone post c++ code for i2c. i am working with battery fuel gauge. my c++ does not work on it.]]></description>
			<content:encoded><![CDATA[<p>can anyone post c++ code for i2c. i am working with battery fuel gauge. my c++ does not work on it.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Yasir		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-629</link>

		<dc:creator><![CDATA[Yasir]]></dc:creator>
		<pubDate>Wed, 04 Apr 2018 03:51:27 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-629</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-628&quot;&gt;Roland Pelayo&lt;/a&gt;.

PRU&#039;s are definitly what caught my attention when selecting the beaglebone for their realtime capabilities and potential of using processor heavy tasks with linux to control the PRUSS is really promising. I hope it gets clearer as to how one could tap into the PRUSS as it does not seem to be similar to programming an AVR microcontroller at all.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-628">Roland Pelayo</a>.</p>
<p>PRU's are definitly what caught my attention when selecting the beaglebone for their realtime capabilities and potential of using processor heavy tasks with linux to control the PRUSS is really promising. I hope it gets clearer as to how one could tap into the PRUSS as it does not seem to be similar to programming an AVR microcontroller at all.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Roland Pelayo		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-628</link>

		<dc:creator><![CDATA[Roland Pelayo]]></dc:creator>
		<pubDate>Wed, 04 Apr 2018 03:31:21 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-628</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-627&quot;&gt;Yasir&lt;/a&gt;.

For changing speeds, you have to update the I2C device tree overlay of the BBB. I have written articles about device tree overlays &lt;a href=&quot;https://www.teachmemicro.com/beaglebone-black-pwm-ubuntu-device-tree/&quot;&gt;here&lt;/a&gt;. 

For real-time communication, you can use the BBB&#039;s PRU (programmable real-time unit) which is like a separate microcontroller. Using it isn&#039;t easy though and I haven&#039;t tried using it with I2C. Maybe I&#039;ll write about that in the future.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-627">Yasir</a>.</p>
<p>For changing speeds, you have to update the I2C device tree overlay of the BBB. I have written articles about device tree overlays <a href="https://www.teachmemicro.com/beaglebone-black-pwm-ubuntu-device-tree/">here</a>. </p>
<p>For real-time communication, you can use the BBB's PRU (programmable real-time unit) which is like a separate microcontroller. Using it isn't easy though and I haven't tried using it with I2C. Maybe I'll write about that in the future.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Yasir		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-627</link>

		<dc:creator><![CDATA[Yasir]]></dc:creator>
		<pubDate>Wed, 04 Apr 2018 02:04:59 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-627</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-435&quot;&gt;Roland Pelayo&lt;/a&gt;.

Thanks for that Roland, I was not aware of that possibility and will start experimenting with it immediately. 
How would you set the clock frequency with those commands? Since the slave would only operate at either 400kHz or 1Mhz. I assume real-time communication is not possible with this method on the BBB?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-435">Roland Pelayo</a>.</p>
<p>Thanks for that Roland, I was not aware of that possibility and will start experimenting with it immediately.<br />
How would you set the clock frequency with those commands? Since the slave would only operate at either 400kHz or 1Mhz. I assume real-time communication is not possible with this method on the BBB?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Roland Pelayo		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-626</link>

		<dc:creator><![CDATA[Roland Pelayo]]></dc:creator>
		<pubDate>Wed, 04 Apr 2018 01:38:15 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-626</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-625&quot;&gt;Yasir&lt;/a&gt;.

Hi Yasir,

You can always use shell scripts to run bash commands like i2cget, i2cset, etc. I assume you are not familiar with this so let me share a bit.

A typical script contains these:

  #!/bin/bash
  
  command1
  sudo command2
  command3
  sudo command4

this is normally a .sh file that you can make executable using

    chmod +x script.sh

to run it:

   ./script.sh

you can also use conditional statements, loops, etc in shell scripts. I would recommend this site: https://www.shellscript.sh/]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-625">Yasir</a>.</p>
<p>Hi Yasir,</p>
<p>You can always use shell scripts to run bash commands like i2cget, i2cset, etc. I assume you are not familiar with this so let me share a bit.</p>
<p>A typical script contains these:</p>
<p>  #!/bin/bash</p>
<p>  command1<br />
  sudo command2<br />
  command3<br />
  sudo command4</p>
<p>this is normally a .sh file that you can make executable using</p>
<p>    chmod +x script.sh</p>
<p>to run it:</p>
<p>   ./script.sh</p>
<p>you can also use conditional statements, loops, etc in shell scripts. I would recommend this site: <a href="https://www.shellscript.sh/" rel="nofollow ugc">https://www.shellscript.sh/</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Yasir		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-625</link>

		<dc:creator><![CDATA[Yasir]]></dc:creator>
		<pubDate>Wed, 04 Apr 2018 01:19:54 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-625</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-435&quot;&gt;Roland Pelayo&lt;/a&gt;.

Hi Roland,

It still seems confusing as to how one can write a program to write to an I2C slave device and control. Command line is great but writing a script that could be run and looped is something that I am still looking into. Any advice?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-435">Roland Pelayo</a>.</p>
<p>Hi Roland,</p>
<p>It still seems confusing as to how one can write a program to write to an I2C slave device and control. Command line is great but writing a script that could be run and looped is something that I am still looking into. Any advice?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Roland Pelayo		</title>
		<link>https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-459</link>

		<dc:creator><![CDATA[Roland Pelayo]]></dc:creator>
		<pubDate>Mon, 26 Feb 2018 14:56:38 +0000</pubDate>
		<guid isPermaLink="false">https://www.teachmemicro.com/?p=782#comment-459</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-458&quot;&gt;mahmoud saati&lt;/a&gt;.

Glad to hear you were able to solve it Mahmoud. I hope you solve the other problem as well.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.teachmemicro.com/beaglebone-black-i2c-tutorial/#comment-458">mahmoud saati</a>.</p>
<p>Glad to hear you were able to solve it Mahmoud. I hope you solve the other problem as well.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 

Served from: www.teachmemicro.com @ 2026-10-18 07:20:51 by W3 Total Cache
-->