problem: "non standard" ft5406 touch not work
situation:
- compute modul v1.1, 2016-09-23-raspbian-jessie-lite
- display: 664350_010_edt_etm0700g0dh6 (800x480 5,7" tft)
- touch controller: ft5406
followed steps on https://www.raspberrypi.org/documentati ... display.md
- connected gpio0 cd1sda, gpio1 cd1scl
- dmesg says: touchscreen not detected
- int (of ft5406) not connected
- lsmod: rpi_ft5406 3324 0
- lsmod: i2c_dev 6578 0
- config.txt not touched
@ startup can see short communication between compute modul , touch on oscilloscope (on scl , sda), guess 6 bytes. have idea why communication between compute modul , "non standard display" touch ft5406 controller breaks?
situation:
- compute modul v1.1, 2016-09-23-raspbian-jessie-lite
- display: 664350_010_edt_etm0700g0dh6 (800x480 5,7" tft)
- touch controller: ft5406
followed steps on https://www.raspberrypi.org/documentati ... display.md
- connected gpio0 cd1sda, gpio1 cd1scl
- dmesg says: touchscreen not detected
- int (of ft5406) not connected
- lsmod: rpi_ft5406 3324 0
- lsmod: i2c_dev 6578 0
- config.txt not touched
@ startup can see short communication between compute modul , touch on oscilloscope (on scl , sda), guess 6 bytes. have idea why communication between compute modul , "non standard display" touch ft5406 controller breaks?
can have several reasons why communication stops ..raspiator wrote:problem: "non standard" ft5406 touch not work
situation:
- compute modul v1.1, 2016-09-23-raspbian-jessie-lite
- display: 664350_010_edt_etm0700g0dh6 (800x480 5,7" tft)
- touch controller: ft5406
followed steps on https://www.raspberrypi.org/documentati ... display.md
- connected gpio0 cd1sda, gpio1 cd1scl
- dmesg says: touchscreen not detected
- int (of ft5406) not connected
- lsmod: rpi_ft5406 3324 0
- lsmod: i2c_dev 6578 0
- config.txt not touched
@ startup can see short communication between compute modul , touch on oscilloscope (on scl , sda), guess 6 bytes. have idea why communication between compute modul , "non standard display" touch ft5406 controller breaks?
why not use official 7in display, sniff i2c data traffic (i.e. using logic analyzer protocol capability (like i.e. https://www.saleae.com/) instead of scope) , let 'non standard touch' send same commands @ startup.
not expect rpi foundation answer topic...
raspberrypi
Comments
Post a Comment