BRT Community

Hi everyone.

What if I need to change a register on the CTP IC, how can I achieve it?

Thanks a lot.

Have a great weekend

OK, Thank you all for this.
If I load the AN_336 configuration code, then it doesn't works at all even after changing the 0x30b17c register to 40, probably because it tries to identify the IC ID/Vendor, and it fails duo to that its HYCON and not FocalTech, so its not working.

If there is any way to avoid the ID checking stuff (or other solution), I will be very happy to try it.

Thanks a lot again

OK, so after applying this Hot-fix it just works.
I have to check it further about the responsiveness and few more characteristics to mark this as completely solved, but for now it seems just fine.

Tomorrow I will take care for the further testing.

Will report to you here.

Anyway, a great advance, so thanks for everyone.

BTW, there is a way to configure it to be around 100KHz instead 57KHz?

Warm regards

First of all, Thanks for everyone who's trying to help here, THANKS! 

Now, to explain our situation:
We've already manufactured 100 PCBs (They're quite expensive duo to some components we use there) with the direct connection of CTP to EVE, and it was working great with our LCD module which used Goodix IC, but after increasing the outer glass thickness of our LCD Module for withstanding a vandalism of our product, we have to replace the IC to the HYCON one which supports this, so we now stuck.
In addition, a development round of handling the touch events on the MCU is quite a task for us now, and might delay our product launch, which we want to avoid of course.
So we need a solution to work around this issue.

Now to the point about the replies here:
1. It is definitely true that chip ID registers of the HY vs FT is not the same, BUT, It doesn't seems that EVE checks any registers about the chip ID, so this should be fine.
2. Thanks for the clarification about the clock stretching, but it seems that it don't needs clock stretching when running at about 100KHz (you can see the logics in my posts above), so this should be even better at 57KHz (fast enough for Touch input).
3. From my understanding the all HY families is compatible since their demo code links is directing to the same files, so I assume it should just the same, isn't?

Later today I will be on the office and will try the patch BRT supplied here, and will report back.

Again, I want to thank you all about your assistance.

Hi,

After testing it connected directly to the MCU I2C lines it seems on the signals that it needs clock stretching.
It works perfect with a much slower clock (about 4 times slower - probably 100KHz vs 400KHz which the FT813 probably uses).
See the attached image with a slower clock when connected to the MCU.

Please follow me to the right solution on how to slow down the clock for the CTP I2C.

Thanks a lot

Hi,

After obtaining a logic analyser, I got the lines data, attached on the image here.

Can you please inspect them to see what's going on? (I'm not completely understands this, shame on me haha).

Thanks a lot

Hi,

I'm also trying to use this CTP IC (HY4635) and no luck.
The reason why I'm not using host mode is that HY461x series have the same API so it should work without any issue.

Please froward me to the right direction on how to solve it.

My EVE chip is FT813Q

Thanks a lot