BRT Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - mtesmer

Pages: [1]
1
Discussion - EVE / Re: Where can I download "FNT_CVT.EXE" utility?
« on: February 16, 2022, 05:37:13 PM »
Hi,

This utility is obsolete and was replaced by "EVE Asset Builder". You might ask a BRT support direct if you still need it.

BR/

2
Discussion - EVE / Re: Multi tag problem
« on: February 15, 2022, 10:15:24 AM »
Yes, It looks like that ILI2132 version intended to be a FT compatible.

I did a very quick mock-up and connect MCU direct to a touch controller. As per comparison provided earlier my ILITEK CT is outputting whole 64 byte data payload, no matter if you press one touch or more. They "padding" data to the left so first touch data, followed by second, etc. The remain of no used data is zero and there is some validity data at the end. I attached some images from analyser for a reference. This most likely causing you a problem on multi as TC is processing data from a stream rather than from associated register. For example five touches will give you [1,2,3,4,5,0,...] but three [1,2,3,0,0,0,...], etc.

3
Discussion - EVE / Re: Multi tag problem
« on: February 09, 2022, 05:01:50 PM »
Hello,

First my apologies if I'm drifting from the topic but my problem might be similar.

I've started to play with similar ILITEK ILI2130 cap controller used on Winstar 5" TFT display and linked with BT817. Using AN336 and programmer manual, I get as far as initialising module and read data. Rudolph, You was correct. ILITEK used slightly different I2C address - 1000 001b - which I altered via REG_TOUCH_CONFIG. I stick to compatibility mode (as I do not need multi touch at this stage) and let it go. I'm seeing INT going low, SCL and SDA coming through when touch is made. I can also confirm that once screen is touched, data from controller is bursting in 9ms intervals and once touch is released controller stop outputting data. My problem is that touch value read by BT817 is always constant (REG_CTOUCH_TOUCH0_XY = 0x07010448) no matter which part of screen I'm touching. I tried to calibrate but after pressing on glowing dot, it stop flashing and I'm stuck in EVE_busy() reading 0xFEC instead of 0xFFC (as my read, write pointers do not come equal).

My init is basic:
Code: [Select]
EVE_MEM_WR16(REG_TOUCH_CONFIG, 0x0410);             /* set ILI2130 ctouch address */
EVE_MEM_WR8(REG_CTOUCH_EXTENDED, EVE_CTMODE_COMP);  /* set ctouch compatibility mode */
        EVE_MEM_WR8(REG_CTOUCH_MODE, EVE_CTMODE_ON);        /* enable cap touch */

I did not load any configuration code to RAM as I'm not yet familiar with that technique.

My question is if you both succeed in compatibility mode or the only option is to use Host mode and send touch data via MCU on that particular controller? Any way to connect and use direct on BT817?

As curiosity I switched to extended mode and data behaviour changed. The controller is sending a lot more data but only once per touch.

PS. I attached a nice comparison from Winstar highlighting key differences between FT5426 and ILI2130. Hope you will be able to read from attachments bellow (maximum total size limitation :().

Best Regards,

Pages: [1]