I am also bringing up a touchscreen that uses that controller right now. Do you have another question? To get back to the initial state you would need to power cycle it, although there shouldn’t be any hanging if you are initializing it as shown in the code I’ve posted. Michael, It seems we found a reason of the strange behavior. In fact, it is present on i2c bus but it allways reads ad last byte written to it.
|Date Added:||20 July 2016|
|File Size:||70.22 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I am also bringing up a touchscreen that uses that controller right now.
Linux/PROCESSOR-SDK-AM335X: FT5x06 capacitive touchscreen issue
Hi, Do you have external pullups on the I2C lines? And what do they think?
February 05, Please, check this issue with your displays if possible. We actually need it to be placed beyong glass liux thick as 2 mm or even 4 mm. Below is a link to the FT5x06 application note, which shows these registers: Use of the information on this site may require a license from a third party, or a license from TI. I2c address not detected by ” i2cdetect ” command root amx-evm: Hi All, any updates Most of them failed due to firmware version mismatch.
Ft5x006 are glad that we were able to resolve this issue, and will now proceed to close this thread.
Regardless, they are the same function. Will the one ground pulse of ms to WAKE signal be enough? Is there any guide how to set up touch controller settings to force it to work? This program can confuse your I2C bus, ftt5x06 data loss and worse! Navigation Main page SomLabs Website.
8. EDT ft5x06 based Polytouch devices — The Linux Kernel documentation
I2c address not detected by ” i2cdetect ” command. Menu Search through millions of questions and answers User.
Please correct me if anything is wrong in device tree configuration. Do you see any activity on them when you probe the interface? I saw using the scope that we actually have reading delay not less then byte intervals but this doesn’t work.
Following are the lof for touch screen 1. We tried 3 different 4.
linux/edt-ft5xtxt at master · git-mirror/linux · GitHub
I had not run into this issue before using our testers, but it seems it is highly dependent on which processor is being used. Hi Nathan, From the capacitive touch screen panel, Reset signal was not brought out to the connector side. 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.
I have just confirmed what I have said above, with the below code: That’s why I was confused. I have not lnux of this issue before, and have posted code I have just used confirming the register read does work. Because which kernel message is getting logged.