Issue with Multi-Touch solution for FT5x06

@MartinAused ,

Hardware I2C0 is mapped to Software I2C1 likewise for other channels. We have removed I2c driver from 1.5 b4 onwards, so Loading I2C1 should not come by default from the image until enabling(“DLL”=“i2cDriver.dll”) it in the driver.

We would like to suggest clean Flash 1.5 B4 image and test with our preliminary version library and other tools.

We are tested I2C_demo application with 1.5 B4 image with preliminary version library, it works.

Also, we have recently developed I2ctool and this is not yet published, please download it from here and test it on Vybrid.

We have another Capacitive touch controller over I2c interface, that has been working on Vybid 1.5B4 image.

If it is not working for you, please share your test application, probe and share I2C bus Oscilloscope waveforms, it will help us to debug the issue quickly.

@raja.tx
can you show me registers that works for I2C?
To see activity in I2C channel, I have to change " Order=0" and “Instance=0” using “[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\I2C0]” key…

now I´m going to use default windows registers, 1.5b4 and preliminary version, only changing SODIM pin for RST and Int of the source code.

I´ve just put the 1.5b4image, and it seems something os wrong with flash loading.
Waits 300 seconds!!
and then it loads…

I2C tool does not work at all. When I try to access to the app, the complete system freeze.

1 time load, 3 times wont mount the flash memory.

As I try to mount the Flash Disk, and fail, I try to execute I2C tool from SD card and this is what I get in the Serial Port.

08:39:39.605> Excetion 'Data Abort' (0x4): Thread-Id=0458110e(pth=c05052ec), Proc-Id=04af0e0a(pprc=c0505a0) 'I2CTool.exe', VMactive=04af0e0a(ppr
08:39:39.605> c=c0505ab0) 'I2CTool.exe'
08:39:39.605> PC=8002bf28(kernel.dll+0x0000ef28) RA=40040c04(coredll.dll+0x00030c04) SP=cf56f7e0, BVA=00000000
08:39:39.635> Exception 'Data Abort'(4) Thread-Id=0458110e(pth=c05052ec) PC=8002bf2c BVA=cf561ef4, dwInfo = 00000807
08:39:39.635> Exception 'Data Abort'(4) Thread-Id=0458110e(pth=c05052ec) PC=8002bf2c BVA=0000000c, dwInfo = 00000007
08:39:39.635> Exception 'Data Abort'(4) Thread-Id=0458110e(pth=c05052ec) PC=8002bf2c BVA=0000000c, dwInfo = 00000007
08:39:39.672> Exception 'Data Abort'(4) Thread-Id=0458110e(pth=c05052ec) PC=8002bf2c BVA=0000000c, dwInfo = 00000007
08:39:39.672> Exception 'Data Abort'(4) Thread-Id=0458110e(pth=c05052ec) PC=8002bf2c BVA=0000000c, dwInfo = 00000007
08:39:39.672> Exception 'Data Abort'(4) Thread-Id=0458110e(pth=c05052ec) PC=8002bf2c BVA=0000000c, dwInfo = 00000007
08:39:39.672> Exception 'Data Abort'(4) Thread-Id=0458110e(pth=c05052ec) PC=8002bf2c BVA=ffff1020, dwInfo = 00000807

@raja.tx

I think there´s maybe something about attending the interuption.
I see that the IC put the address in the bus, but there´s no interruption requested in OS.
can we check that?
I´m missing anything about it?

I´m using 1,5b2 + std lib.
and I´ve try with original register keys, and try another too.

I´ve found the main problem that I have here, and it was that in my boards I have 4k7 PullUps resistances for I2C bus, and it seems to be inssuficient as the FT5x06 hapens to need 1k pull ups for the bus, and for the ctrl lines #RST and #INT. Now I have 1.5b2 image, and the original source code taken from @guzoo (with my own GPIOs) and it´s working! I´ve only have to try this in the official 1.4 image. The 1.5b2 image have something wrong with the uSD card that freeze the system when I try to access to uSD from the explorer…

Thanks a lot and I´ll keep sharing all that i have in my hands…

@MartinAused ,

We are glad to know you found the solution for the issue.
Good luck for further development.

i tried to use your code. i got some error when rebuilding. i attached the error file. kindly give suggestion.link text

My environment is Colibri VF50 + Viola 1.2A

Please open a new question about the issue and leave the error messages inside your post.
Are you building the code using VS2008 and our latest SDK? Please provide information about that in your new post.