<html><head></head><body>What's the problem with reading? Is this a MAX, or a Turbot? I2C on the MAX has a known issue with the level shifter on those pins not always working with some devices (I2C needs slightly different shifters), that's fixed on the Turbot right now.<br>
<br>
- John<br><br><div class="gmail_quote">On March 4, 2016 10:46:20 AM PST, Tony <tony.makkiel@daqri.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi John 'Warthog9' Hawley,<br /> Thank you very much. It is bus 7. I can see the clock when I run i2cget.<br /><br />I guess something might be wrong with my led controller, which cause the <br />read to fail. But thanks to you I know Minnowboard is working :)<br /><br />Many Thanks,<br />Tony<br /><br />On 04/03/16 16:38, John 'Warthog9' Hawley wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> The LSE and HSE's I2C is on physical interface #5 (which is the<br /> DesignWare IP), but that doesn't mean it enumerates in the OS to #5. In<br /> your i2cdetect you'll note that the first DesignWare adapter is on bus<br /> #7. Re-running your tests on that bus should get you what you are<br /> expecting. I *HAVE* seen in a couple of cases where i2cdetect on the<br /> bus won't report some devices, but if you attempt to read/write directly<br /> to the address (I.E. just assume it's
there)
things work. The issue<br /> there is that some devices don't quite implement smbus / i2c quite right<br /> and get confused on how to respond to the detection.<br /><br /> Let me know if that works, and if it doesn't we'll try some additional<br /> things.<br /><br /> - John 'Warthog9' Hawley<br /><br /> On 03/04/2016 07:58 AM, Tony wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> Hi,<br /> I am trying to talk to TI led controller using i2c#5, pin 13 and 15.<br /> But for some reason I cant get the i2c pins working. I tried connecting<br /> i2c probe on the pins. But don't see any clock when I do i2cdetect.<br /><br /> sudo i2cdetect -y 5<br /><br /> I am using xubuntu kernel 4.4. The related kernel modules I could find are<br /><br /> i2c_designware_platform and i2c_designware_core<br /><br /> For some reason i2c-5 is getting used by display driver.<br /><br /> i2cdetect -l<br /> i2c-0
unknown i915 gmbus ssc N/A<br /> i2c-1 unknown i915 gmbus vga N/A<br /> i2c-2 unknown i915 gmbus panel N/A<br /> i2c-3 unknown i915 gmbus dpc N/A<br /> i2c-4 unknown i915 gmbus dpb N/A<br /> i2c-5 unknown i915 gmbus dpd N/A<br /> i2c-6 unknown DPDDC-B N/A<br /> i2c-7 unknown Synopsys DesignWare I2C adapter N/A<br /> i2c-8 unknown Synopsys DesignWare I2C adapter N/A<br /><br /><br /> Any suggestions on what I might be doing wrong?<br /><br /> Many Thanks,<br /> Tony<br /><hr /><br /> elinux-MinnowBoard mailing list<br /> elinux-MinnowBoard@lists.elinux.org<br /> <a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a></blockquote><br /><br /><hr /><br /> elinux-Minnow
Board
mailing list<br /> elinux-MinnowBoard@lists.elinux.org<br /> <a href="http://lists.elinux.org/mailman/listinfo/elinux-minnowboard">http://lists.elinux.org/mailman/listinfo/elinux-minnowboard</a></blockquote><br /><br /></pre></blockquote></div></body></html>