Hi Bob
It is a good suggestion, and should avoid the issue.
However, I have reviewed the library I use for I2C and unfortunately I can't see any support for extra I2C buses. Also, the OLED initialisation and display library I use depends on this I2C library, and so any change to support extra I2C buses in the current code is probably not straightforward.
For the future, the U8G2 library has been ported to ARM and I have created a project that assembles this into a library package for Raspbian (but still needs some extra utility functions). It supports software I2C, but I am unsure of its speed or if it can take advantage of the i2c_gpio driver. I will ultimately switch to using this library for mpd_oled
https://github.com/antiprism/libu8g2arm_test
Adrian.
It is a good suggestion, and should avoid the issue.
However, I have reviewed the library I use for I2C and unfortunately I can't see any support for extra I2C buses. Also, the OLED initialisation and display library I use depends on this I2C library, and so any change to support extra I2C buses in the current code is probably not straightforward.
For the future, the U8G2 library has been ported to ARM and I have created a project that assembles this into a library package for Raspbian (but still needs some extra utility functions). It supports software I2C, but I am unsure of its speed or if it can take advantage of the i2c_gpio driver. I will ultimately switch to using this library for mpd_oled
https://github.com/antiprism/libu8g2arm_test
Adrian.
