Strange behavior on I2C. GrovePi broken or what?


#1

Hi,

I tried to continue one project last weekend with my old grovepi and did the firmware update first. After update (I think they worked before the update) my sensors started behaving badly and when I debugged it for a while, it seems that I2C bus is somehow messed up.

When I reboot my raspi and log in as soon as possible to do i2cdetect, everything is in order and I actually can read proper sensor values. After few seconds I2C bus gets messed up and sensors stops giving reasonable values.

Below i2cdetect is run two times. Time between commands is less than 15 seconds. Anyone can say is my grovepi just burnt up, did this happen because of firmware update (My GrovePi is original, not the plus model) and is there any way to fix this?

Last login: Sun Jun 28 16:12:05 2015 from vault36.local
pi@raspi2 ~ i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- 04 -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- pi@raspi2 ~ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f
30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f
50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f
70: 70 71 72 73 74 75 76 77


#2

I Found this link https://www.raspberrypi.org/forums/viewtopic.php?f=44&t=77453 and remembered that I might have loaded some 1-wire module too… Going to check this when I get home.


#3

Hey,
The problem might be because of the 1-wire sensors that you had mentioned earlier. Just make sure that nothing is connected to the I2C ports on the GrovePi.

-Karan


#4

No sensors at all connected and problem persist. I also checked that there is no 1-wire modules loaded.

Any more ideas?


#5

well, I ordered new grovepi (plus model, current is original) just to be sure… but I’m still open to any suggestions… :slight_smile:

But have You ever before seen issue like this? I would really like to know what I did wrong so I won’t do the same mistake again…

EDIT: After reading this ( https://raspberrypi.stackexchange.com/questions/26612/i2cdetect-strange-output ) post (again?) I tested my raspi without grovepi and it still gives full i2c table, so the bug is not in grove it seems.

I’m guessing that I should test my GrovePi with another raspberry pi but I don’t have any other raspi2 available, so I have to build system from sratch with raspi1 and I’m also thinking to start raspi2 from sratch… While it seems that my problem is not related directly to the grovepi, i’ll write at least one more post to close this thread.


#6

Hey,
Are you using the Dexter Industries Raspbian image or something else. There might be some mismatch with the I2C settings too that might be causing the problem.

-Karan


#7

Hi Karan,

It seems that my problem remains a mystery.
I started from the scratch and everything is working now as intented. I don’t know what i messed up last time, but obviously something… :confused:

And no, I don’t use Dexters Raspbian image but std raspberry pi raspbian image.

Thanks for your help anyway and sorry for all the fuzz…

Let’s talk more when I mess my grovepi+ in a few weeks :stuck_out_tongue:


#8

Great to hear that the GrovePi is finally working for you. Sorry for all the troubles. Do let us know if you make any interesting projects with the GrovePi.

Happy Hacking,
Karan