* i2c-bcm2835: Unable to read from i2c0
@ 2016-01-28 21:43 Stefan Wahren
[not found] ` <56AA8B75.9060801-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>
0 siblings, 1 reply; 4+ messages in thread
From: Stefan Wahren @ 2016-01-28 21:43 UTC (permalink / raw)
To: linux-rpi-kernel, linux-i2c
Hi,
i'm using a Raspberry Pi B (rev 1) and Linux kernel 4.5rc-1. I have
connected a PiGlow (SN3218 at address 0x54) to the P1 Header. The I2C
bus clock is set to 100 kHz. Every time i want to read data from i2c0
the following error appear:
[ 94.343612] i2c-bcm2835 20205000.i2c: i2c transfer failed: 100
According to the BCM2835 datasheet this should be an ERR ACK (Slave has
not acknowledged its address).
> i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
> i2cdetect -q -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- 54 -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Strangly writing data to the SN3218 works.
Does anyone have an explanation for this error?
Regards
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread[parent not found: <56AA8B75.9060801-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>]
* Re: i2c-bcm2835: Unable to read from i2c0 [not found] ` <56AA8B75.9060801-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org> @ 2016-01-28 22:49 ` Phil [not found] ` <7de3fd0b-7973-476c-a009-e9a1fb032a80-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Phil @ 2016-01-28 22:49 UTC (permalink / raw) To: Stefan Wahren; +Cc: linux-rpi-kernel, linux-i2c-u79uwXL29TY76Z2rM5mHXA A few questions: 1) What has changed in your system? Have you ever been able to use the PiGlow? 2) What is the state of the GPIOs? Phil On 28 Jan 2016 9:43 p.m., Stefan Wahren <info@lategoodbye.de> wrote: > > Hi, > > i'm using a Raspberry Pi B (rev 1) and Linux kernel 4.5rc-1. I have > connected a PiGlow (SN3218 at address 0x54) to the P1 Header. The I2C > bus clock is set to 100 kHz. Every time i want to read data from i2c0 > the following error appear: > > [ 94.343612] i2c-bcm2835 20205000.i2c: i2c transfer failed: 100 > > According to the BCM2835 datasheet this should be an ERR ACK (Slave has > not acknowledged its address). > > > i2cdetect -y 0 > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- > > > i2cdetect -q -y 0 > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: -- -- -- -- -- -- -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 50: -- -- -- -- 54 -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- > > Strangly writing data to the SN3218 works. > > Does anyone have an explanation for this error? > > Regards > Stefan > > _______________________________________________ > linux-rpi-kernel mailing list > linux-rpi-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-rpi-kernel _______________________________________________ linux-rpi-kernel mailing list linux-rpi-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-rpi-kernel ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <7de3fd0b-7973-476c-a009-e9a1fb032a80-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>]
* Re: i2c-bcm2835: Unable to read from i2c0 [not found] ` <7de3fd0b-7973-476c-a009-e9a1fb032a80-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org> @ 2016-01-29 18:16 ` Stefan Wahren [not found] ` <56ABAC83.4000402-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org> 0 siblings, 1 reply; 4+ messages in thread From: Stefan Wahren @ 2016-01-29 18:16 UTC (permalink / raw) To: Phil; +Cc: linux-rpi-kernel, linux-i2c-u79uwXL29TY76Z2rM5mHXA Hi Phil, Am 28.01.2016 um 23:49 schrieb Phil: > A few questions: > > 1) What has changed in your system? Have you ever been able to use the PiGlow? please avoid top-posting. I'm using I2C just for a short time, so i don't know if there was a different behavior before. I tested the PiGlow with the following kernel versions: Raspbian Wheezy 3.18 Raspbian Jessie 4.1.13 Mainline 4.5rc-1 All of them show the same detect behavior (see below). Writing to the SN3218 works good, i can enable and disable the LEDs ... But i can't read back any values. I've replaced the PiGlow with a Adafruit Si1145. After that the chip is detected in both cases, but the error messages (i2c transfer failed) still appear. > > 2) What is the state of the GPIOs? What do you mean? configuration of both I2C0 pins? Do you want a register dump? Thanks Stefan > > Phil > > On 28 Jan 2016 9:43 p.m., Stefan Wahren <info-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org> wrote: >> >> Hi, >> >> i'm using a Raspberry Pi B (rev 1) and Linux kernel 4.5rc-1. I have >> connected a PiGlow (SN3218 at address 0x54) to the P1 Header. The I2C >> bus clock is set to 100 kHz. Every time i want to read data from i2c0 >> the following error appear: >> >> [ 94.343612] i2c-bcm2835 20205000.i2c: i2c transfer failed: 100 >> >> According to the BCM2835 datasheet this should be an ERR ACK (Slave has >> not acknowledged its address). >> >>> i2cdetect -y 0 >> 0 1 2 3 4 5 6 7 8 9 a b c d e f >> 00: -- -- -- -- -- -- -- -- -- -- -- -- -- >> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 70: -- -- -- -- -- -- -- -- >> >>> i2cdetect -q -y 0 >> 0 1 2 3 4 5 6 7 8 9 a b c d e f >> 00: -- -- -- -- -- -- -- -- -- -- -- -- -- >> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 50: -- -- -- -- 54 -- -- -- -- -- -- -- -- -- -- -- >> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- >> 70: -- -- -- -- -- -- -- -- >> >> Strangly writing data to the SN3218 works. >> >> Does anyone have an explanation for this error? >> >> Regards >> Stefan >> >> _______________________________________________ >> linux-rpi-kernel mailing list >> linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org >> http://lists.infradead.org/mailman/listinfo/linux-rpi-kernel ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <56ABAC83.4000402-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>]
* Re: i2c-bcm2835: Unable to read from i2c0 [not found] ` <56ABAC83.4000402-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org> @ 2016-01-29 18:47 ` Phil 0 siblings, 0 replies; 4+ messages in thread From: Phil @ 2016-01-29 18:47 UTC (permalink / raw) To: Stefan Wahren; +Cc: linux-rpi-kernel, linux-i2c-u79uwXL29TY76Z2rM5mHXA > > 2) What is the state of the GPIOs? > > What do you mean? configuration of both I2C0 pins? > > Do you want a register dump? There are a number of utilities that will display the configuration of all pins - raspi-gpio is the one I use. My intention was to confirm that the I2C0 function was not multiply mapped, but you can do that yourself, and from what you say it probably isn't. You are likely to get more answers on the Raspberry Pi forums. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-01-29 18:47 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-28 21:43 i2c-bcm2835: Unable to read from i2c0 Stefan Wahren
[not found] ` <56AA8B75.9060801-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>
2016-01-28 22:49 ` Phil
[not found] ` <7de3fd0b-7973-476c-a009-e9a1fb032a80-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2016-01-29 18:16 ` Stefan Wahren
[not found] ` <56ABAC83.4000402-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>
2016-01-29 18:47 ` Phil
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox