- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello all,
I am trying to adapt the linux driver CYTMA568 PSoC™ Automotive Multitouch for the nitrogen 6x from NXP. I would like to drive in i2c through the J5 connector of the Nitrogen.
I have followed the "Driver porting" part of the TTDL PIP User guide, so I have add parts to my dts and all the files corresponding to the driver in the correct place in my kernel.
I also include the driver in the menuconfig of the kernel.
However, at kernel boot I am facing these issues :
@
cyttsp5_i2c_adapter 0-0024: cyttsp5_init: INIT CYTTSP RST gpio=28 and IRQ gpio=30 r=0
cyttsp5_i2c_adapter 0-0024: cyttsp5_get_hid_descriptor_: failed to get HID descriptor length and version, rc=-5
cyttsp5_i2c_adapter 0-0024: cyttsp5_startup_: Error on getting HID descriptor r=-5
cyttsp5_i2c_adapter 0-0024: cyttsp5_xres: RESET CYTTSP gpio=28 r=0
cyttsp5_i2c_adapter 0-0024: cyttsp5_reset_and_wait: reset timed out
cyttsp5_i2c_adapter 0-0024: cyttsp5_startup_: Error on h/w reset r=-62
cyttsp5_i2c_adapter 0-0024: cyttsp5_xres: RESET CYTTSP gpio=28 r=0
cyttsp5_i2c_adapter 0-0024: cyttsp5_reset_and_wait: reset timed out
cyttsp5_i2c_adapter 0-0024: cyttsp5_startup_: Error on h/w reset r=-62
cyttsp5_i2c_adapter 0-0024: cyttsp5_xres: RESET CYTTSP gpio=28 r=0
cyttsp5_i2c_adapter 0-0024: cyttsp5_reset_and_wait: reset timed out
cyttsp5_i2c_adapter 0-0024: cyttsp5_startup_: Error on h/w reset r=-62
cyttsp5_i2c_adapter 0-0024: cyttsp5_hid_exec_cmd_: Fail cyttsp5_adap_transfer
cyttsp5_i2c_adapter 0-0024: cyttsp5_hid_cmd_set_power_: Failed to set power to state:1
cyttsp5_i2c_adapter 0-0024: cyttsp5_core_rt_suspend: Error on sleep
cyttsp5_i2c_adapter 0-0024: cyttsp5_probe: Fail initial startup r=-19
cyttsp5_i2c_adapter 0-0024: cyttsp5_init: INIT CYTTSP RST gpio=28 and IRQ gpio=30 r=0
cyttsp5_i2c_adapter 0-0024: cyttsp5_probe failed.
And of course the touch doesn't communicate with the Nitrogen board.
Do you have any suggestion to solve this ?
Thanks in advance for your help!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Elisabeth,
In my mind, firstly you can try to test if I2C of TMA568 is OK or not. If I2C can work and the issue is caused by the driver, print more logs, according to the log to find the root cause.
Also you could contact your local CY distributors for support.
Here are our distributors list: http://www.cypress.com/cypress-franchised-distributors. FYI.
Thanks,
Ryan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Elisabeth,
In my mind, firstly you can try to test if I2C of TMA568 is OK or not. If I2C can work and the issue is caused by the driver, print more logs, according to the log to find the root cause.
Also you could contact your local CY distributors for support.
Here are our distributors list: http://www.cypress.com/cypress-franchised-distributors. FYI.
Thanks,
Ryan