connection raspberry 3 b+ and witty pi 4

I applied what the manual says on page 36

pi@raspberrypi:~ $ i2cset -y 1 8 16 0x35

@ornel after running that command, have you also fully disconnected power supply of Witty Pi 4, as mentioned in the manual?

The MCU needs a power cycle to apply the new I2C address.

To answer you I rather restarted it (sudo reboot) after changing the address.

I want to emphasize that it is the fact that I have a lot of addresses displayed that led me to want to change the address and switch to x35

although I restarted the system after changing the address I still had all the addresses displayed as before.

@ornel doing "sudo reboot" would not cut the power for MCU on Witty Pi, and hence the address changing would not take effect.

However the real problem is your I2C bus. Listing all the possible addresses means the I2C bus is not working properly. You may try to remove I2C device one by one to find out which one causes this problem.

So how do I remove each I2C device one by one?

listing all possible addresses means that the I2C bus is not working properly. You can try to remove the I2C devices one by one to find out which one is causing this problem.

Since only the raspberry is connected directly to the wityPi by directly pushing one into the other, how do I remove each i2c device to find out which one is causing this problem?

Can we change the I2c adapter or create one, so that the wittypi can be detected by another adapter than the "1" ?

i.e.: sudo i2cdetect -y 2

Posted by: @ornel

↑

only the raspberry is connected directly to the wityPi

What was the state of your Witty Pi, when you ran i2cdetect command? Did the white LED on Witty Pi still blink?

If you boot your Raspberry Pi without Witty Pi physically connected, what is the output of "i2cdetect -y 1"?

La LED blanche du Witty Pi clignote toujours.

Si je démarre mon Raspberry Pi sans Witty Pi physiquement connecté, la sortie de "i2cdetect -y 1" est la même :

pi@raspberrypi:~ $ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 abcdef
00: 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

Posted by: @ornel

↑

La LED blanche du Witty Pi clignote toujours.

Si je démarre mon Raspberry Pi sans Witty Pi physiquement connecté, la sortie de "i2cdetect -y 1" est la même :

Please write in English, or at least put Google/AI translated text aside, as stated in the forum's rule.

This time I put translation for you here:

"Witty Pi's white LED is still blinking.

If I start my Raspberry Pi without a physically connected Witty Pi, the release of "I2CDetect -Y 1" is the same:"

Witty Pi's LED is blinking means it is in "sleep" mode and only wake up for a very short moment every second. Users should not expect it to response every I2C request correctly. In normal use case, Witty Pi doesn't receive I2C request during the sleep.

However, your I2C bus seems misconfigured or corrupted, because you can reproduce the issue without connecting Witty Pi to your Raspberry Pi. The result you get indicates the problem is not from Witty Pi. You may want to check with another Raspberry Pi, or diagnose the I2C bus on the current one.

I apologize for answering in French.

However, I have read your message.

Before switching to another raspberry, my question would be: how to diagnose the I2C bus on the current Raspberry Pi? To actually check that it is corrupted or misconfigured and no longer usable with my wittyPi4

Posted by: @ornel

↑

how to diagnose the I2C bus on the current Raspberry Pi?

I really can not tell. There are many possible reasons. I can only tell your I2C bus is not funtioning well according to your screenshots.

A normal I2C bus should give you a result for i2cdetect like this:

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --