The display says it uses all of the IO, and they just break out the one i2c port for you to use for expansion. I must admit I have not got my head around BCM and actual pin numbers, when I saw you write earlier about Pins 10/11 etc....
At the bottom of the page here; https://learn.pimoroni.com/article/gett ... nced-users
it has about the i2c and sym link. I didn't have much luck with that.
The pin outs for the display are here;
https://pinout.xyz/pinout/hyperpixel#
You can see nothing left to play with, and the i2c-3 port they have broken out is listed as the touch screen interface, which has address 0x15 in the i2cdetect -y 3
I'm not sure when the i2c port got redesignated to i2c-3. I'll be doing a complete rebuild soon and take note, I'd say it happens when the driver is installed.
The overlay they install on is on Github; https://github.com/pimoroni/hyperpixel2 ... verlay.dts
It has the i2c setup. I'm not fully familiar with overlay syntax but this bit sets it up;
At the bottom of the page here; https://learn.pimoroni.com/article/gett ... nced-users
it has about the i2c and sym link. I didn't have much luck with that.
The pin outs for the display are here;
https://pinout.xyz/pinout/hyperpixel#
You can see nothing left to play with, and the i2c-3 port they have broken out is listed as the touch screen interface, which has address 0x15 in the i2cdetect -y 3
I'm not sure when the i2c port got redesignated to i2c-3. I'll be doing a complete rebuild soon and take note, I'd say it happens when the driver is installed.
The overlay they install on is on Github; https://github.com/pimoroni/hyperpixel2 ... verlay.dts
It has the i2c setup. I'm not fully familiar with overlay syntax but this bit sets it up;
Code:
fragment@3 { target-path = "/"; __overlay__ { i2c_gpio: i2c@0 { compatible = "i2c-gpio"; gpios = <&gpio 10 0 &gpio 11 0 >; i2c-gpio,delay-us = <4>; #address-cells = <1>; #size-cells = <0>; }; }; };Statistics: Posted by midworld08 — Wed May 22, 2024 2:00 am