I am using the latest release Pi OS Lite, Aug 2020 version. I am developing an application using Pi4J. I am referring to pins via this Pinout: https://pi4j.com/1.2/pins/model-3b-plus-rev1.html
I am using both I2C buses, 0 and 1, in my application. To enable I2C-0 I added "dtparam=i2c_vc=on" to the config.txt file. I am also using GPIO 11 (BCM pin 7) as a digital out. This works just fine with the Raspberry Pi Zero W. However, when I changed to a Pi 3B+ (and bumped up the OS to the next release, but not sure that is the issue), the following occurs:
When I include "dtparam=i2c_vc=on" to the config.txt file I get access to the I2C-O bus, as expected. However, in addition to /dev/i2c-0 appearing, I also get /dev/i2c-10 and /dev/i2c-11 and when attempting to provision GPIO-11 in Pi4J, I no longer have access to GPIO-11 (BCM pin 7). My guess is that the mysterious appearance of I2C-11 and disappearance of GPIO-11 are related. As I was using GPIO-11 for something and I have already fabricated a PCB, this puts me into a bit of a bind. I would much rather use the 3B+ and not have to patch the physical hardware. This does not appear to be an issue with Pi4J. My guess/hope is that there is probably a trivial solution with device overlays, but no luck searching for this specific problem. Any help/pointers would be greatly appreciated.