July 08, , This page was last modified on 5 September , at The difference between these two cases is that when it is a ‘cold’ start processor has undefined state on GPIO pins. I think that FT processes its I2C interrupt too slow to update the I2C transmit register so we get the value that has been written in write stage of the transaction. Details can be found in the user manuals for Allwinner chips, in the section TP touch panel. If you get lucky, you might find firmware supporting your device from this repository. Now I tested it with another host which can wait for 1 ms between writing register address and issuing next start condition.
|Date Added:||1 November 2013|
|File Size:||62.51 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
July 10, According to Device Tree documentation for FT5x06 chipsadd following entry in somlabs-visionsom-6ull.
That’s why I was confused. Started by coran21 Board TFTs.
The I2C protocol between the two displays should be the same. The most urgent problem remains with 4. If you get lucky, you might find firmware supporting your device from this repository.
Above description also defines two optional properties for Touchscreens:.
CONFIG_TOUCHSCREEN_EDT_FT5X06: EDT FocalTech FT5x06 I2C Touchscreen support
I very highly doubt you have liinux displays, but if you would like to send them back to us for analysis, you may email nhtech newhavendisplay. I suspect that all this issues could force FT5x06 to hang. Then you need to write the image file to microSD card. Now I tested it with another host which can wait for 1 ms between writing register address and issuing next start condition.
Spontaneous cursor movement can be seen with a threshold of 3 and glass strart to work at threshold 5.
Regardless, they are the same function. The rresults are the same.
And it started to work properly! You may be correct, since the WAKE signal operates as you have described. We tried 3 different 4. I had not run into this issue before using our testers, linus it seems it is highly dependent on which processor is being used. Then I proposed to pull the flat cable out of connector and push it back while the u-boot is running. Content is available under Creative Commons Attribution unless otherwise noted.
drivers/input/touchscreen/ftc – kernel/bcm – Git at Google
This means that there will be a lot of communication on the i2c port since this has to happen once every few ms. But then u-boot starts and places GPIO pins in a known state. Driver recognizes both displays via I2C, handshakes, etc. We tried both kHz and kHz bus speed. Personal tools Create account Log in. I think you should also test this and add this information into display datasheet.
October 19, Mainly the I2C pins are connected to any i2c port on the CPU and is used to communicate with the touchscreen. Usually any touchscreen has a startup procedure during which resets are sent to the touchscreen by the cpu to indicate this procedure. In this case display works. So we still have problem with it. To be sure that your SD card has enough space for it, please remember to resize it before installing xfce4 package – more information: This page has been accessed 55, times.
Page Discussion View source History.