barish 1 Report post February 7 I did the following upgrades this morning libcurl3:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), libgd3:armhf (2.2.4-2+deb9u3, 2.2.4-2+deb9u4), armbian-config:armhf (5.72, 5.74), linux-headers-next-sunxi:armhf (5.70, 5.73), linux-image-next-sunxi:armhf (5.70, 5.73), curl:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), libcurl3-gnutls:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), linux-dtb-next-sunxi:armhf (5.70, 5.73), base-files:armhf (9.9+deb9u6, 9.9+deb9u7) and found my I2C bus not working anymore. I did a scan on the 4 buses (Olinuxino Micro A20) and found a device on i2c-1 instead of i2c-0, changed my settings and all worked again, so I guess one of the updates must have changed the labeling of the busses? Is this by accident or on purpuse? 0 Share this post Link to post Share on other sites
Igor 1363 Report post February 7 2 minutes ago, barish said: Is this by accident or on purpuse? Most likely settings were changed upstream since I don't recall seeing anyone around Armbian fiddling around this. 1 Share this post Link to post Share on other sites
martinayotte 306 Report post February 7 13 minutes ago, barish said: found a device on i2c-1 instead of i2c-0 If you do a "i2cdetect -l", you will probably see that i2c-0 is dedicated to "sun4i_hdmi_i2c adapter", which maybe wasn't present before ... 2 Share this post Link to post Share on other sites
barish Topic author 1 Report post February 8 19 hours ago, martinayotte said: If you do a "i2cdetect -l", you will probably see that i2c-0 is dedicated to "sun4i_hdmi_i2c adapter", which maybe wasn't present before ... This is indeed the case. Thanks for this information, the change must have crept in lately. If I had the energy I could find out which of the i2c adapters on the Olinuxino were labeled as "hdmi", but right now, since I don't need to know, I won't... 0 Share this post Link to post Share on other sites
Bï Ĺý 0 Report post Wednesday at 10:25 AM On 2/7/2019 at 6:00 PM, barish said: I did the following upgrades this morning libcurl3:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), libgd3:armhf (2.2.4-2+deb9u3, 2.2.4-2+deb9u4), armbian-config:armhf (5.72, 5.74), linux-headers-next-sunxi:armhf (5.70, 5.73), linux-image-next-sunxi:armhf (5.70, 5.73), curl:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), libcurl3-gnutls:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), linux-dtb-next-sunxi:armhf (5.70, 5.73), base-files:armhf (9.9+deb9u6, 9.9+deb9u7) and found my I2C bus not working anymore. I did a scan on the 4 buses (Olinuxino Micro A20) and found a device on i2c-1 instead of i2c-0, changed my settings and all worked again, so I guess one of the updates must have changed the labeling of the busses? Is this by accident or on purpuse? Bluestacks Kodi Lucky Patcher Hi barish I solved the problem by re-implementing I2C in the PIC. There were many things that had to be changed in order to make the implementation more robust. None of them implied removing clock stretching since that is impossible in a PIC (at least in most PICs) since they are slow and need some time to process things. Why I2C communication worked with #893 and then worked no more with newer firmware versions is something that our changes do not explain. One clear thing is that the PIC now responds much faster than before to any communication request. To sum up, our current version (with ongoing tests at the moment) is far better and works with the latest published firmware version as of today. The previous I2C version does not work and we are not exploring that road (unless anyone apart from me was interested). 0 Share this post Link to post Share on other sites
