Capacitive touch screen

37 views
Skip to first unread message

evilwulfie

unread,
Feb 24, 2018, 1:13:19 PM2/24/18
to Beagle Board
Does anybody happen to have a Capacitive touch screen using
the edt_ft5x06 driver hooked up to a bone ?

If anybody does can you send me the output of "i2cdump  1 0x38"

I have a buydisplay.com tft with cap touch.

it uses a ft5x06 controller

It may be that the current driver built into the kernel will not
function with a non etd touch panel

Its all hooked up correctly I see the device @ 0x38 I think i have the
overlay correct it looks like
all other overlays when it comes to this type of touch panel
i see nothing using these commands related to a display

dmesg | grep i2c
dmesg | grep input

I can see the IRQ pin go low when i press on the display

I dont see any interrupts assigned although i asked for one in the overlay


section in fragment@0 of overlay

                        edt_ft5x06_pins: pinmux_edt_ft5x06_pins {
                                pinctrl-single,pins = <
                                        BONE_P9_23 (PIN_INPUT_PULLUP |
MUX_MODE7)       // interrupt for touch
                                >;

here is fragment 1 where touch is

        fragment@1 {
                target = <&i2c1>;
                __overlay__ {
                        pinctrl-names = "default";
                        pinctrl-0 = <&bb_i2c1_pins>;
                        status = "okay";

                        clock-frequency = <400000>;

                        /* shut up DTC warnings */
                        #address-cells = <1>;
                        #size-cells = <0>;

                        // touch screen controller on ER-TFTM070-5

                        touch: edt-ft5x06@38 {
                            status = "okay";
                            compatible =
"edt,edt-ft5306","edt,edt-ft5406","edt,edt-ft5206","edt,edt-ft5x06";

                            pinctrl-names = "default";
                            pinctrl-0 = <&edt_ft5x06_pins>;

                            reg = <0x38>;
                            interrupt-parent = <&gpio1>;   // gpio1_17 
pin P9_23
                            interrupts = <0x17 0x0>;
                            //reset-gpios = <&gpio2 6 1>;

                            touchscreen-size-x = <800>;
                            touchscreen-size-y = <480>;
                        };

It all looks fine to me but i am at a loss as to why things are not
loaded or detected

IF anybody sees something obvious or knows anything about this please
help :)






Robert Nelson

unread,
Feb 24, 2018, 1:28:59 PM2/24/18
to Beagle Board, evilwulfie
gpio1_17 -> 17

0x17 -> 23 -> gpio1_23...

Regards,

--
Robert Nelson
https://rcn-ee.com/

evilwulfie

unread,
Feb 24, 2018, 1:33:27 PM2/24/18
to Robert Nelson, Beagle Board
interrupt-parent = <&gpio1>; // gpio1_17
pin P9_23
interrupts = <0x17 0x0>;

gpio1_17 -> 17

0x17 -> 23 -> gpio1_23...


 interrupts = <0x17 0x0> change to interrupts = <0x23 0x0> ?

This is SO confusing sometimes

Robert Nelson

unread,
Feb 24, 2018, 2:01:49 PM2/24/18
to evilwulfie, Beagle Board


On Feb 24, 2018 12:33 PM, "evilwulfie" <evilw...@gmail.com> wrote:
                            interrupt-parent = <&gpio1>;   // gpio1_17
pin P9_23
                            interrupts = <0x17 0x0>;

gpio1_17 -> 17

0x17 -> 23 -> gpio1_23...


 interrupts = <0x17 0x0> change to interrupts = <0x23 0x0>  ?

This is SO confusing sometimes


No if it's pin gpio1_17 that's interrupt 17 decimal, not hex.

Regards,

evilwulfie

unread,
Feb 24, 2018, 2:06:30 PM2/24/18
to Robert Nelson, Beagle Board
bangs head on table
Reply all
Reply to author
Forward
0 new messages