[MinnowBoard] i2c support
david.anders at intel.com
Mon Mar 7 21:36:05 UTC 2016
And scan the entire bus... you never know if it might be misconfigured for a different address:
#sudo i2cget -r -y 7
Depending on how the bios is configured you could potentially have the bus numbers swapped, so you might want to double check bus 8 as well:
#sudo i2cget -r -y 8
From: elinux-MinnowBoard [mailto:elinux-minnowboard-bounces at lists.elinux.org] On Behalf Of John Hawley
Sent: Monday, March 7, 2016 3:33 PM
To: elinux-minnowboard at lists.elinux.org
Subject: Re: [MinnowBoard] i2c support
Inline & cutting down as this is getting a little long -JH
On 03/07/2016 02:27 AM, Tony wrote:
> I am not sure, why read fails. It is Minnowboard MAX.
Since it's the MAX you are *LIKELY* running into a level shifter issue, which is obnoxious. What device is this? I'm happy to try and get one in to double check what's going on if you can let me know what you've got.
> I tried running i2cdetect on bus 7 which fails with error
> "Error: Can't use SMBus Quick Write command on this bus"
The bus itself doesn't support the Quick Write command so you need to add `-r` to the command line so that it doesn't actually try and do that.
I'll add that info to the wiki (along with my suggestion on the i2cdetect and which bus you should look for) but some example code that might be helpful can be found here as well:
> Reading from address also fails
> "sudo i2cget -y 7 0x54 0x0c
> Error: Read failed"
> Can the problem with level shifters be fixed on MAX boards?
If it was the level shifters I'd expect something like "lost bus arbitration" not an absolute read failed. Can you try the i2cdtect with the -r, and that attached, and let me know? Again it would be helpful to know what chip, and I'll snag one and get it in.
elinux-MinnowBoard mailing list
elinux-MinnowBoard at lists.elinux.org
More information about the elinux-MinnowBoard