I2C working on1 out of 4 OMEGA2+ [RESOLVED]

Arthur Dubois

Hello.

I have 4 Omega2+ and on 3 of them I cannot access the i2c. With i2cdetect -y 0 I get
the 30 ...37 and 50 ...5f. On the one that is working I can see the device connected as expected:
root@Omega-xxxx:~# i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: UU -- -- -- -- -- -- 17 -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

I get the same result if I SSH or connect through the serial port.

I am wondering if I did install a package on the working one and forgot?
Any suggestion? Any help is appreciated.

Thanks.

György Farkas

@Arthur-Dubois said in I2C working on1 out of 4 OMEGA2+:

I have 4 Omega2+ and on 3 of them I cannot access the i2c. With i2cdetect -y 0 I get
the 30 ...37 and 50 ...5f. On the one that is working I can see the device connected as expected:
root@Omega-xxxx:~# i2cdetect -y 0

More correctly you should have written:
I have 4 Omega2+ and I2C works on each of them but the output of the i2cdetect command wrong on 3 of them.
i2cdetect(8) - Linux man page

I am wondering if I did install a package on the working one and forgot?

You updated the firmware to v0.2.0 b194 only on the "working one" - the others have some older FW.
Please check it with oupgrade -v.

Arthur Dubois

You are correct. I checked the firmware on the one with the correct i2cdetect output,
it is Version: 0.2.0 b194 while the other ones are : ' 0.1.9 b159' but after doing 'oupgrade' it is now 0.1.10 b160 and not 0.2.0 b194

Doing 'oupgrade' again give this message:
~# oupgrade

Device Firmware Version: 0.1.10 b160
Checking latest version online...
Repo Firmware Version: 0.1.10 b160
Comparing version numbers
Device firmware is up to date!

I guess it fetches the upgrade from the wrong place. Any further suggestion?

Thanks for the help.

György Farkas

@Arthur-Dubois Please try oupgrade -l -f
Good luck!

Arthur Dubois

that worked, thank you György.