FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - TurboKing

Pages: [1]
1
It is not feasible to have additional I2C lines to the CTP as I don't have an I2C bus/connection available.

I wanted to clarify if EVE checked the status of the I2C connection or simply listened for touch responses, if it is only listening then I will not be able to verify which CTP is connected, if the hardware team can verify that would be really useful.

The only alternative I have is to use one of the USERID bytes on the dsPIC I'm using to specify the I2C address and to set this when uploading/programming the code, then my application can read this byte and initialise the display correctly.

Regards.

2
I have two different screens both using the FT813 with Capacitive Touch interfaces. The first screen uses a Focaltech touch controller and the touch interface works as standard. The second screen type uses a Goodix controller and with the additional code described in AN336 also works correctly without any issues.

Each of the screens CTP interfaces uses a different I2C address and hence this must be correctly set in the code depending on the connected screen type.

Screen 1: REG_TOUCH_CONFIG = 0x0381 (Focaltech)
Screen 2: REG_TOUCH_CONFIG = 0x05D0 (Goodix)

I would like to programmatically determine whether the FT813 touch engine is able to communicate with the CTP or is in fault so that I can determine which screen type is connected. This will allow dual sourcing of the screens and a single application code.

Is there a way to check the touch engine status or to communicate directly with the CTP so I can identify the CTP/Screen type fitted? This may involve setting each I2C address in turn and checking for status/communication success if this is available.

Any help is greatly appreciated.

Pages: [1]