lupus666 Posted November 22, 2016 Share Posted November 22, 2016 Hi, I have recently upgraded Armbian as suggested with: apt-get updateapt-get upgradeapt-get install -fapt-get upgradeapt-get autoremove -y After that i2c-0 stopped working: Output if i2cdetect -y 0 before upgrade: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- 77 After upgrade: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- UU Also reading/writing from/to this device does not work anymore after upgrade. If I plug the device to i2c-1 it works even after the upgrade. So only i2c-0 is broken after upgrade. A strange thing is: If I unplug the device from i2c-0 and run i2cdetect again it still shows UU at the address of the device although it is not connected anymore. Link to comment Share on other sites More sharing options...
mariuszb Posted November 22, 2016 Share Posted November 22, 2016 See https://forum.armbian.com/index.php/topic/2917-bmp085-module/ Link to comment Share on other sites More sharing options...
lupus666 Posted November 22, 2016 Author Share Posted November 22, 2016 Thank you very much! Link to comment Share on other sites More sharing options...
tkaiser Posted November 22, 2016 Share Posted November 22, 2016 Does that mean that everyone now has to blacklist bmp085 module on H3 devices? If so, please file an issue at https://github.com/igorpecovnik/lib/issuesso that we either blacklist this on every H3 device by default or exclude this driver from the fat FriendlyARM Matrix package (since I really doubt that much people use this) Link to comment Share on other sites More sharing options...
mariuszb Posted November 22, 2016 Share Posted November 22, 2016 Maybe this module came too late, and many people took advantage of other software. According to me, each new user will benefit from this module. (eg. I have blocked this module now because I had my own software, but may, however, I will use this module in future) Let it be Link to comment Share on other sites More sharing options...
Recommended Posts