No idea how this can create an I2C interface on GPIO10/11 and why the heck this should become I2C-11Alright, i Got it working by removing the bus parameter from the i2c-gpio dtoverlay test.
used this :It created i2c 11Code:
dtoverlay=i2c-gpio,i2c_gpio_sda=2,i2c_gpio_scl=3..Code:
i@raspberrypi:~ $ sudo i2cdetect -y 11 0 1 2 3 4 5 6 7 8 9 a b c d e f00: -- -- -- -- -- -- -- -- 10: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
Your issue is thisWhen you have the SW I2C registered as I2C5 then your target will also have to point on that bus.Code:
target = <&i2c1>;
And in addition, why don't you combine your custom overlay with the SW I2C overlay? Then users can use simple/simpler overrides where needed.
My bad it was a mistake ..
correct setup which i used was
Code:
dtoverlay=i2c-gpio,i2c_gpio_sda=10,i2c_gpio_scl=11 recognised by the overlay. So i changed the target to i2c-gpio and didnt mention any bus parameter in config.txt setup. And then it worked.
It created i2c-11 and the overlay also recognised the device and reserved it.
How do i combine the custom goodix overlay with sw i2c overlay? any pointers will be helpful.
So far by this solution, users can use the custom goodix overlay with target mentioned as i2c-gpio and setup the software i2c on pins as per their wish and not mentioned the bus parameter in the config.txt
I ineed wish to enable the bus parameter in SW i2c setup so that the standard GOODIX overlay and any custom overlays can easily recognise the software i2c pins via "target = <&i2c1>"
Statistics: Posted by BalajiNarasimhan — Fri Jan 19, 2024 3:20 am