I'd misread the schematic. You've got a DPI display attached, so you can't use i2c-1 on GPIOs 2&3. The buildroot must have configured a bit-bashed I2C bus on GPIOs 10 & 11.
"dtoverlay=i2c-gpio,i2c_gpio_sda=10,i2c_gpio_scl=11" should do that, and it'll create the bus as probably i2c-12 (check with "i2cdetect -l").
The issue then is that there is no easy way of chaining I2C devices onto bit-bashed buses through overlays. I think there is a way around this by being able to set "target-path" for the fragment instead of "target". I wonder if we can implement that generally as an override.
"dtoverlay=i2c-gpio,i2c_gpio_sda=10,i2c_gpio_scl=11" should do that, and it'll create the bus as probably i2c-12 (check with "i2cdetect -l").
The issue then is that there is no easy way of chaining I2C devices onto bit-bashed buses through overlays. I think there is a way around this by being able to set "target-path" for the fragment instead of "target". I wonder if we can implement that generally as an override.
Statistics: Posted by 6by9 — Mon Dec 16, 2024 2:58 pm