Hi, In IXORA V1.1A datasheet on page 26 is probably CTRL+C CTRL+V typo. Capacitive touch connector should not be DF13C-6P-1.25V(51). Is it FH12-10S-0.5SVA(54) ? Is there any recommended flat cable type for it? Is there any cap. touch driver support in your angstrom linux images for Apalis TK1 or I need to write my own driver?
Is there any cap. touch driver support in your angstrom linux images for Apalis TK1 or I need to write my own driver?
So far we at least have not integrated any specific such support as we also do not yet sell any capacitive touch solution which would be compatible with Apalis TK1. That said our BSPs for all other modules did support our former Fusion aka Touch Revolution based 7 and 10 inch capacitive multi touch solutions plus we are in the process of integrating support for our new 7 inch based one now available from our web shop to be released by end of Q3. Based on that similar support could be integrated for Apalis TK1 quite easily I guess. Furthermore you may find more drivers available in the kernel sources but they are as of yet untested from our side.
In IXORA V1.1A datasheet on page 26 is probably CTRL+C CTRL+V typo. Capacitive touch connector should not be DF13C-6P-1.25V(51). Is it FH12-10S-0.5SVA(54)?
Dear @marsaf, you are definitely right! that is a copy and paste mistake, we will definitely correct it in the next document revision.
Is there any recommended flat cable type for it?
I think that the best recommendation I can provide here is checking the specification contained on page 3 of this document:
Normally a standard 0.5mm pitch, same side FFCs available on Digikey should work fine.
In addition, I would like to mention that you will soon able to order the product “Capacitive Touch Display 7” Parallel V1.0A" from our webshop: it gets deliverd with the cable.
I really hope this helps, please don’t hesitate to use again the Toradex community if required.
I am using NewHaven display, which has probably the same I2C touch interface as Fusion displays. M.
Then I would recommend to try it e.g. on Apalis T30 or Apalis iMX6 where this should work more or less out-of-the-box. If it turns out that the Fusion driver is suitable it may be easily ported to Apalis TK1 as well. If not one would have to find out what exact driver would be suitable for your exact device and go from there.
We are also looking for Capacitive Touch for an Apalis TK1 based design running under Linux. Do I understand correctly from Marcel’s answer that the planned support for the new 7-inch does not support TK1? Would it be a Projected Capacitive Touch type controller? Assuming the driver code can be ported easily, what controller chip is planned so I may consider integrating it into our carrier.
We are also looking for Capacitive Touch for an Apalis TK1 based design running under Linux. Do I understand correctly from Marcel’s answer that the planned support for the new 7-inch does not support TK1?
Yes, as it is a parallel RGB screen which can not easily be connected to Apalis TK1 only featuring eDP resp. LVDS
Would it be a Projected Capacitive Touch type controller
Yes.
Assuming the driver code can be ported easily, what controller chip is planned so I may consider integrating it into our carrier.
Please find resp. driver in our -next branches e.g. here. As for the Apalis TK1 we are currently finalising a 10 inch capacitive touch display (e.g. using LVDS) which will be compatible with Apalis TK1 as well.
There are two 24bit parallel RGB displays on the accessories webpage for TK1 ( NVIDIA Tegra K1 System/Computer on Module - Apalis TK1 SoM ). From what I know, neither of them is ready for TK1 connection (with Toradex carrier board), isn´t it? So they are not direct accessories, because one has to build LVDS bridge for them. Marking them as an accessory may be confusing. We will wait for true LVDS accessory displays.
Yes, you are absolutely correct. I guess when introducing those two new display products our product management wrongly selected Apalis TK1 as being compatible. I reported this now and it should be corrected shortly.
Thanks for reporting this and I am really sorry for any inconvenience this may have caused.