Info checksum error read=0005D6 with mxt640UD

[biccius]

I'm running mxt-app from a raspberry pi using i2c native interface with a mxt640
It actually works on a mxt640U and i get following responses:

raspberrypi@raspberrypi:~/mxt-app $ ./mxt-app -d i2c-dev:1-004b -i

Device registered on i2c-dev adapter:1 address:0x4b

Family: 166 Variant: 1 Firmware V1.1.AA Objects: 41
Matrix size: X32Y20
Information Block CRC: 0xFE4DE3

Type Start Size Instances ReportIds Name
-----------------------------------------------------------------
T37   256   130     1        0-0    DEBUG_DIAGNOSTIC_T37
T44   386     1     1        0-0    SPT_MESSAGECOUNT_T44
T5    387    11     1        0-0    GEN_MESSAGEPROCESSOR_T5
T6    398     7     1        1-1    GEN_COMMANDPROCESSOR_T6
T68   405    73     1        2-2    SERIAL_DATA_COMMAND_T68
T38   478    64     1        0-0    SPT_USERDATA_T38
T71   542   200     1        0-0    SPT_DYNAMICCONFIGURATIONCONTAINER_T71
T110  742    40    12        0-0    SPT_SELFCAPTUNINGPARAMS_T110
T7   1222     7     1        0-0    GEN_POWERCONFIG_T7
T8   1229    15     1        0-0    GEN_ACQUISITIONCONFIG_T8
T15  1244    11     1        3-3    TOUCH_KEYARRAY_T15
T18  1255     2     1        0-0    SPT_COMMSCONFIG_T18
T19  1257    16     1        4-4    SPT_GPIOPWM_T19
T25  1273    16     1        5-5    SPT_SELFTEST_T25
T40  1289     7     1        0-0    PROCI_GRIPSUPPRESSION_T40
T42  1296    14     1        0-0    PROCI_TOUCHSUPPRESSION_T42
T43  1310    15     1        6-6    SPT_DIGITIZER_T43
T46  1325    18     1        7-7    SPT_CTECONFIG_T46
T47  1343    47     1        0-0    PROCI_STYLUS_T47
T56  1390    36     1        8-8    PROCI_SHIELDLESS_T56
T61  1426     5     6        9-14   SPT_TIMER_T61
T65  1456    23     3       15-17   PROCI_LENSBENDING_T65
T70  1525    10    20       18-37   SPT_DYNAMICCONFIGURATIONCONTROLLER_T70
T72  1725    89     1       38-38   PROCG_NOISESUPPRESSION_T72
T77  1814     2     1        0-0    SPT_CTESCANCONFIG_T77
T78  1816    12     1        0-0    PROCI_GLOVEDETECTION_T78
T79  1828     4     3        0-0    SPT_TOUCHEVENTTRIGGER_T79
T80  1840    14     1       39-39   PROCI_RETRANSMISSIONCOMPENSATION_T80
T81  1854    18     2       40-41   PROCI_UNLOCKGESTURE_T81
T93  1890    30     1       42-42   PROCI_TOUCHSEQUENCELOGGER_T93
T100 1920    68     1       43-60   TOUCH_MULTITOUCHSCREEN_T100
T104 1988    11     1        0-0    SPT_AUXTOUCHCONFIG_T104
T108 1999    75     1       61-61   PROCG_NOISESUPSELFCAP_T108
T109 2074     9     1       62-62   SPT_SELFCAPGLOBALCONFIG_T109
T111 2083    32     2        0-0    SPT_SELFCAPCONFIG_T111
T112 2147     5     1       63-63   PROCI_SELFCAPGRIPSUPPRESSION_T112
T113 2152     3     1        0-0    SPT_PROXMEASURECONFIG_T113
T115 2155    20     1       64-64   PROCI_SYMBOLGESTURE_T115
T116 2175   255     1        0-0    SPT_SYMBOLGESTURECONFIG_T116
T121 2430     3     1        0-0    PROCI_SENSOR_CORRECTION_T121
T132 2433    18     1       65-65   SPT_MESSAGEFILTER_T132

Connecting the same interface with a mxt640UD, i'm experiencing the following issue:

raspberrypi@raspberrypi:~/mxt-app $ ./mxt-app -d i2c-dev:1-004b -i

Device registered on i2c-dev adapter:1 address:0x4b
**Info checksum error calc=04DFFC read=0005D6**
raspberrypi@raspberrypi:~/mxt-app $ 

If i repeat the command i get checksum calculation changed and read is still the same.

In both cases the device answer to 0x4B address:

raspberrypi@raspberrypi:~/mxt-app $ i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- 4b -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --        

Do you have any tips i can try in order to communicate with mxt640UD?

[mgong98]

Hi, Fabrizio. An info checksum error indicates that you have a problem with the information memory block of the chip. This location holds the Family ID, Variant ID, Firmware, # of objects, matrix size information along with a few others. If this checksum is wrong, there is an I2C read issue and the data being read from 0x4B is not consistent with what you have in the Info checksum bytes at the end of this memory block. The calculation is coming up wrong and the comparison fails, so there is something wrong with I2C or there is a read error. When you boot up the unit, does the information found in the directory, /sys/bus/i2c/drivers/atmel_mxt_ts/1-004b/ look okay and is consistent with the version of firmware you are using in the 640UD? The driver has a bunch of sysfs files that can be ‘cat’ to see the content. Fw_version, hw_version, config_crc should match what you have in the device. If not, then mxt-app won’t work either as there is an I2C issue. You may want to double check if the reset from the driver is sufficient, I believe it has increased from 300ms to 1s with newer devices that have BIST or POST tests. Thanks From: Fabrizio Benatti ***@***.***> Sent: Monday, November 28, 2022 7:32 AM To: atmel-maxtouch/mxt-app ***@***.***> Cc: Subscribed ***@***.***> Subject: [atmel-maxtouch/mxt-app] Info checksum error read=0005D6 with mxt640UD (Issue #105) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe I'm running mxt-app from a raspberry pi using i2c native interface with a mxt640 It actually works on a mxt640U and i get following responses: ***@***.***:~/mxt-app $ ./mxt-app -d i2c-dev:1-004b -i Device registered on i2c-dev adapter:1 address:0x4b Family: 166 Variant: 1 Firmware V1.1.AA Objects: 41 Matrix size: X32Y20 Information Block CRC: 0xFE4DE3 Type Start Size Instances ReportIds Name

…

----------------------------------------------------------------- T37 256 130 1 0-0 DEBUG_DIAGNOSTIC_T37 T44 386 1 1 0-0 SPT_MESSAGECOUNT_T44 T5 387 11 1 0-0 GEN_MESSAGEPROCESSOR_T5 T6 398 7 1 1-1 GEN_COMMANDPROCESSOR_T6 T68 405 73 1 2-2 SERIAL_DATA_COMMAND_T68 T38 478 64 1 0-0 SPT_USERDATA_T38 T71 542 200 1 0-0 SPT_DYNAMICCONFIGURATIONCONTAINER_T71 T110 742 40 12 0-0 SPT_SELFCAPTUNINGPARAMS_T110 T7 1222 7 1 0-0 GEN_POWERCONFIG_T7 T8 1229 15 1 0-0 GEN_ACQUISITIONCONFIG_T8 T15 1244 11 1 3-3 TOUCH_KEYARRAY_T15 T18 1255 2 1 0-0 SPT_COMMSCONFIG_T18 T19 1257 16 1 4-4 SPT_GPIOPWM_T19 T25 1273 16 1 5-5 SPT_SELFTEST_T25 T40 1289 7 1 0-0 PROCI_GRIPSUPPRESSION_T40 T42 1296 14 1 0-0 PROCI_TOUCHSUPPRESSION_T42 T43 1310 15 1 6-6 SPT_DIGITIZER_T43 T46 1325 18 1 7-7 SPT_CTECONFIG_T46 T47 1343 47 1 0-0 PROCI_STYLUS_T47 T56 1390 36 1 8-8 PROCI_SHIELDLESS_T56 T61 1426 5 6 9-14 SPT_TIMER_T61 T65 1456 23 3 15-17 PROCI_LENSBENDING_T65 T70 1525 10 20 18-37 SPT_DYNAMICCONFIGURATIONCONTROLLER_T70 T72 1725 89 1 38-38 PROCG_NOISESUPPRESSION_T72 T77 1814 2 1 0-0 SPT_CTESCANCONFIG_T77 T78 1816 12 1 0-0 PROCI_GLOVEDETECTION_T78 T79 1828 4 3 0-0 SPT_TOUCHEVENTTRIGGER_T79 T80 1840 14 1 39-39 PROCI_RETRANSMISSIONCOMPENSATION_T80 T81 1854 18 2 40-41 PROCI_UNLOCKGESTURE_T81 T93 1890 30 1 42-42 PROCI_TOUCHSEQUENCELOGGER_T93 T100 1920 68 1 43-60 TOUCH_MULTITOUCHSCREEN_T100 T104 1988 11 1 0-0 SPT_AUXTOUCHCONFIG_T104 T108 1999 75 1 61-61 PROCG_NOISESUPSELFCAP_T108 T109 2074 9 1 62-62 SPT_SELFCAPGLOBALCONFIG_T109 T111 2083 32 2 0-0 SPT_SELFCAPCONFIG_T111 T112 2147 5 1 63-63 PROCI_SELFCAPGRIPSUPPRESSION_T112 T113 2152 3 1 0-0 SPT_PROXMEASURECONFIG_T113 T115 2155 20 1 64-64 PROCI_SYMBOLGESTURE_T115 T116 2175 255 1 0-0 SPT_SYMBOLGESTURECONFIG_T116 T121 2430 3 1 0-0 PROCI_SENSOR_CORRECTION_T121 T132 2433 18 1 65-65 SPT_MESSAGEFILTER_T132 Connecting the same interface with a mxt640UD, i'm experiencing the following issue: ***@***.***:~/mxt-app $ ./mxt-app -d i2c-dev:1-004b -i Device registered on i2c-dev adapter:1 address:0x4b Info checksum error calc=04DFFC read=0005D6 ***@***.***:~/mxt-app $ Do you have any tips i can try? — Reply to this email directly, view it on GitHub<#105>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANL63K7VMF2YVCGLM3DEKLWKTF6NANCNFSM6AAAAAASNO3DEY>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>

[biccius]

Thank you for the reply

I think the problem is quite different.
We have a MXT640UD-HA and we learned that the protocol of the 'UD-HA' version is completely different from that of the 'UD'.

By the way, I think your tool is incompatible with the 'UD-HA' version chip

Can you confirm this for me?

[mgong98]

Yes, the protocol is different with the UD-HA chips. They ae used for functionality safety and have the requirement for the TX Seq num and the CRC8 on address writes. The mxt-app has been updated to talk to this device. Please try the latest version of mxt-app and let me know if you have any issues. I cannot tell from the screen dumps if you are using the latest. From: Fabrizio Benatti ***@***.***> Sent: Tuesday, November 29, 2022 7:49 AM To: atmel-maxtouch/mxt-app ***@***.***> Cc: Michael Gong - C40415 ***@***.***>; Comment ***@***.***> Subject: Re: [atmel-maxtouch/mxt-app] Info checksum error read=0005D6 with mxt640UD (Issue #105) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe Thank you for the reply I think the problem is quite different. We have a MXT640UD-HA<https://www.microchip.com/en-us/product/ATMXT640UD> and we learned that the protocol of the 'UD-HA' version is completely different from that of the 'UD'. By the way, I think your tool is incompatible with the 'UD-HA' version chip Can you confirm this for me? — Reply to this email directly, view it on GitHub<#105 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANL63KQSAUIHAUGRFSQJ4DWKYQXFANCNFSM6AAAAAASNO3DEY>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[biccius]

I'm currently using v.1.36
How do I enable replies with MXT640UD-HA ?

If i send the line command

raspberrypi@raspberrypi:~/mxt-app $ ./mxt-app -d i2c-dev:1-004b -i

I get wrong checksum calculation error. So I imagine there is something to be activated to send the sequence numbers, but even examining the code, it is not clear to me how.

[mgong98]

Please also try ./mxt-app -i This uses the sysfs framework. I will check on a board here. From: Fabrizio Benatti ***@***.***> Sent: Thursday, December 1, 2022 6:10 AM To: atmel-maxtouch/mxt-app ***@***.***> Cc: Michael Gong - C40415 ***@***.***>; Comment ***@***.***> Subject: Re: [atmel-maxtouch/mxt-app] Info checksum error read=0005D6 with mxt640UD (Issue #105) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe I'm currently using v.1.36 How do I enable replies with MXT640UD-HA ? If i send the line command ***@***.***:~/mxt-app $ ./mxt-app -d i2c-dev:1-004b -i I get wrong checksum calculation error — Reply to this email directly, view it on GitHub<#105 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANL63NB43AZDOWFSKHC4MTWLCWSVANCNFSM6AAAAAASNO3DEY>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[biccius]

I currently have the raspberry's SDA and SCL pins connected directly to module as well as VCC and GND.

In this configuration the only way I have without recompiling a new kernel is to use the following command:

/mxt-app $ ./mxt-app -d i2c-dev:1-004b -i

which, however, fails for the HA version.

[mgong98]

By default, both the non -d and -d option should work. It is telling the mxt-app to use the sysfs interface versus the debugfs interface. Do you have an option to recompile the mxt-app on Github. https://github.com/atmel-maxtouch/mxt-app From: Fabrizio Benatti ***@***.***> Sent: Friday, December 2, 2022 12:14 AM To: atmel-maxtouch/mxt-app ***@***.***> Cc: Michael Gong - C40415 ***@***.***>; Comment ***@***.***> Subject: Re: [atmel-maxtouch/mxt-app] Info checksum error read=0005D6 with mxt640UD (Issue #105) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe I currently have the raspberry's SDA and SCL pins connected directly to module as well as VCC and GND. In this configuration the only way I have without recompiling a new kernel is to use the following command: /mxt-app $ ./mxt-app -d i2c-dev:1-004b -i which, however, fails for the HA version. — Reply to this email directly, view it on GitHub<#105 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANL63PJSOSSNXMWHGOH3PDWLGVV3ANCNFSM6AAAAAASNO3DEY>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[biccius]

Excuse me for insisting, but from my tests, I2C communication with the MXT640UD-HA device, using mxt-app does not work.

I'm running version 1.36

On my /sys/bus/i2c/drivers folder i have "stmpe-i2c" that i think is the driver for my i2c device on raspberry pi3b+

With a i2c scan command i get, so i think my hardware should be ok

aspberrypi@raspberrypi:/sys/bus/i2c/drivers $ i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- 4b -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --          

But when i launch the command /mxt-app -i -d i2c-dev:1-004b i get the following error:

Device registered on i2c-dev adapter:1 address:0x4b
Info checksum error calc=6A194D read=0005D6

So it seems that the device answer to read info block request with a wrong checksum.

With the "U" version it worked perfectly and looking at the library it seemed to me that the "HA" part is actually considered, but I can't get it to work.

Please help.

[mgong98]

I have just tested the 640UD and mxt-app with the following links. https://github.com/atmel-maxtouch/maXTouch_linux.git https://github.com/atmel-maxtouch/mxt-app.git Both of these were from the master branch and working with i2c-dev and sysfs Below is a dump from using mxt-app. The 640UD-HA board uses firmware 1.0.AA. Can you confirm that the Linux driver includes the new read and write routines for the HA device? The latest updates to the Linux driver and mxt-app are required for HA devices. Thanks

…

--------Using i2c-dev --------------------- ***@***.***:~# ./mxt-app -d i2- c-dev:1-004b Device registered on i2c-dev adapter:1 address:0x4b Device registered on debug_fs path:/sys/kernel/debug/atmel_mxt_ts/ Command line tool for Atmel maXTouch chips version: 1.36 Select one of the options: Enter L: (L)oad config file Enter S: (S)ave config file Enter I: Read (I)nfo block and Config CRC Enter D: Rea(D) individual object config Enter W: (W)rite individual object Enter T: Run sel(T)-test Enter F: (F)lash firmware to chip Enter B: (B)ackup the config data to NVM Enter R: (R)eset the maxtouch device Enter C: (C)alibrate the maxtouch device Enter M: Display raw (M)essages Enter U: D(U)mp Diagnostic data Enter Q: (Q)uit the application i Reading info block..... Family: 166 Variant: 21 Firmware V1.0.AA Objects: 43 Matrix size: X32Y20 Information Block CRC: 0x4C9291 Type Start Size Instances ReportIds Name ----------------------------------------------------------------- T117 268 215 6 0-0 SPT_DATACONTAINER_T117 T37 1558 130 1 0-0 DEBUG_DIAGNOSTIC_T37 T144 1688 2 1 0-0 SPT_MESSAGECOUNT_T144 T5 1690 12 1 0-0 GEN_MESSAGEPROCESSOR_T5 T6 1702 7 1 1-1 GEN_COMMANDPROCESSOR_T6 T38 1709 64 1 0-0 SPT_USERDATA_T38 T14 1773 65 1 0-0 PROCI_KEYTHRESHOLD_T14 T16 1838 33 1 0-0 PROCG_SIGNALFILTER_T16 T71 1871 200 1 0-0 SPT_DYNAMICCONFIGURATIONCONTAINER_T71 T110 2071 40 12 0-0 SPT_SELFCAPTUNINGPARAMS_T110 T118 2551 3 1 2-2 SPT_DATACONTAINERCTRL_T118 T141 2554 3 32 0-0 UNKNOWN_T141 T145 2650 1 1 0-0 SPT_IGNORENODESCONTROL_T145 T7 2651 7 1 0-0 GEN_POWERCONFIG_T7 T8 2658 15 1 0-0 GEN_ACQUISITIONCONFIG_T8 T10 2673 11 1 3-3 SPT_SELFTESTCONTROL_T10 T11 2684 4 1 0-0 SPT_SELFTESTPINFAULT_T11 T12 2688 10 2 0-0 SPT_SELFTESTSIGLIMIT_T12 T15 2708 11 1 4-4 TOUCH_KEYARRAY_T15 T18 2719 12 2 0-0 SPT_COMMSCONFIG_T18 T19 2743 16 1 5-5 SPT_GPIOPWM_T19 T24 2759 19 1 6-9 PROCI_ONETOUCHGESTUREPROCESSOR_T24 T27 2778 7 1 10-10 PROCI_TWOTOUCHGESTUREPROCESSOR_T27 T40 2785 7 1 0-0 PROCI_GRIPSUPPRESSION_T40 T42 2792 14 1 0-0 PROCI_TOUCHSUPPRESSION_T42 T46 2806 24 1 11-11 SPT_CTECONFIG_T46 T47 2830 47 1 0-0 PROCI_STYLUS_T47 T56 2877 36 1 12-12 PROCI_SHIELDLESS_T56 T61 2913 5 6 13-18 SPT_TIMER_T61 T65 2943 23 3 19-21 PROCI_LENSBENDING_T65 T70 3012 10 20 22-41 SPT_DYNAMICCONFIGURATIONCONTROLLER_T70 T72 3212 89 1 42-42 PROCG_NOISESUPPRESSION_T72 T78 3301 12 1 0-0 PROCI_GLOVEDETECTION_T78 T79 3313 4 3 0-0 SPT_TOUCHEVENTTRIGGER_T79 T80 3325 15 1 43-43 PROCI_RETRANSMISSIONCOMPENSATION_T80 T100 3340 76 1 44-61 TOUCH_MULTITOUCHSCREEN_T100 T104 3416 11 1 0-0 SPT_AUXTOUCHCONFIG_T104 T108 3427 75 1 62-62 PROCG_NOISESUPSELFCAP_T108 T109 3502 17 1 63-63 SPT_SELFCAPGLOBALCONFIG_T109 T111 3519 32 2 0-0 SPT_SELFCAPCONFIG_T111 T112 3583 5 1 64-64 PROCI_SELFCAPGRIPSUPPRESSION_T112 T113 3588 7 1 0-0 SPT_PROXMEASURECONFIG_T113 T133 3595 42 2 0-0 SPT_SELFCAPVOLTAGEMOD_T133 Reading config crc..... REPORTALL command issued Configuration CRC: 0xD1A64F

--------Using sysfs-------------------------- ***@***.***:~# ./mxt-app --info Seaching for device at 0x4b Device registered on sysfs path:/sys/bus/i2c/drivers/atmel_mxt_ts/1-004b Family: 166 Variant: 21 Firmware V1.0.AA Objects: 43 Matrix size: X32Y20 Information Block CRC: 0x4C9291 Type Start Size Instances ReportIds Name ----------------------------------------------------------------- T117 268 215 6 0-0 SPT_DATACONTAINER_T117 T37 1558 130 1 0-0 DEBUG_DIAGNOSTIC_T37 T144 1688 2 1 0-0 SPT_MESSAGECOUNT_T144 T5 1690 12 1 0-0 GEN_MESSAGEPROCESSOR_T5 T6 1702 7 1 1-1 GEN_COMMANDPROCESSOR_T6 T38 1709 64 1 0-0 SPT_USERDATA_T38 T14 1773 65 1 0-0 PROCI_KEYTHRESHOLD_T14 T16 1838 33 1 0-0 PROCG_SIGNALFILTER_T16 T71 1871 200 1 0-0 SPT_DYNAMICCONFIGURATIONCONTAINER_T71 T110 2071 40 12 0-0 SPT_SELFCAPTUNINGPARAMS_T110 T118 2551 3 1 2-2 SPT_DATACONTAINERCTRL_T118 T141 2554 3 32 0-0 UNKNOWN_T141 T145 2650 1 1 0-0 SPT_IGNORENODESCONTROL_T145 T7 2651 7 1 0-0 GEN_POWERCONFIG_T7 T8 2658 15 1 0-0 GEN_ACQUISITIONCONFIG_T8 T10 2673 11 1 3-3 SPT_SELFTESTCONTROL_T10 T11 2684 4 1 0-0 SPT_SELFTESTPINFAULT_T11 T12 2688 10 2 0-0 SPT_SELFTESTSIGLIMIT_T12 T15 2708 11 1 4-4 TOUCH_KEYARRAY_T15 T18 2719 12 2 0-0 SPT_COMMSCONFIG_T18 T19 2743 16 1 5-5 SPT_GPIOPWM_T19 T24 2759 19 1 6-9 PROCI_ONETOUCHGESTUREPROCESSOR_T24 T27 2778 7 1 10-10 PROCI_TWOTOUCHGESTUREPROCESSOR_T27 T40 2785 7 1 0-0 PROCI_GRIPSUPPRESSION_T40 T42 2792 14 1 0-0 PROCI_TOUCHSUPPRESSION_T42 T46 2806 24 1 11-11 SPT_CTECONFIG_T46 T47 2830 47 1 0-0 PROCI_STYLUS_T47 T56 2877 36 1 12-12 PROCI_SHIELDLESS_T56 T61 2913 5 6 13-18 SPT_TIMER_T61 T65 2943 23 3 19-21 PROCI_LENSBENDING_T65 T70 3012 10 20 22-41 SPT_DYNAMICCONFIGURATIONCONTROLLER_T70 T72 3212 89 1 42-42 PROCG_NOISESUPPRESSION_T72 T78 3301 12 1 0-0 PROCI_GLOVEDETECTION_T78 T79 3313 4 3 0-0 SPT_TOUCHEVENTTRIGGER_T79 T80 3325 15 1 43-43 PROCI_RETRANSMISSIONCOMPENSATION_T80 T100 3340 76 1 44-61 TOUCH_MULTITOUCHSCREEN_T100 T104 3416 11 1 0-0 SPT_AUXTOUCHCONFIG_T104 T108 3427 75 1 62-62 PROCG_NOISESUPSELFCAP_T108 T109 3502 17 1 63-63 SPT_SELFCAPGLOBALCONFIG_T109 T111 3519 32 2 0-0 SPT_SELFCAPCONFIG_T111 T112 3583 5 1 64-64 PROCI_SELFCAPGRIPSUPPRESSION_T112 T113 3588 7 1 0-0 SPT_PROXMEASURECONFIG_T113 T133 3595 42 2 0-0 SPT_SELFCAPVOLTAGEMOD_T133 Thanks From: Fabrizio Benatti ***@***.***> Sent: Thursday, June 29, 2023 8:24 AM To: atmel-maxtouch/mxt-app ***@***.***> Cc: Michael Gong - C40415 ***@***.***>; Comment ***@***.***> Subject: Re: [atmel-maxtouch/mxt-app] Info checksum error read=0005D6 with mxt640UD (Issue #105) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe Excuse me for insisting, but from my tests, I2C communication with the MXT640UD-HA device, using mxt-app does not work. I'm running version 1.36 On my /sys/bus/i2c/drivers folder i have "stmpe-i2c" that i think is the driver for my i2c device on raspberry pi3b+ With a i2c scan command i get, so i think my hardware should be ok ***@***.***:/sys/bus/i2c/drivers $ i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- 4b -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- But when i launch the command /mxt-app -i -d i2c-dev:1-004b i get the following error: Device registered on i2c-dev adapter:1 address:0x4b Info checksum error calc=6A194D read=0005D6 So it seems that the device answer to read info block request with a wrong checksum. With the "U" version it worked perfectly and looking at the library it seemed to me that the "HA" part is actually considered, but I can't get it to work. Please help. — Reply to this email directly, view it on GitHub<#105 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANL63J6HABG5IGTELFZ3VTXNWMXVANCNFSM6AAAAAASNO3DEY>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[biccius]

It doesn't seem to work and I honestly can't figure out why.

The kernel on my raspberry is 6.1.37 and /sys/bus/i2c/drivers/atmel_mxt_ts/ directory exist but folder "1-004B" is not present.

Only SDA, SCL and GND pins are connected between 640UD-HA and rpi

I've checked with oscilloscope and signals are ok

I continue to get checksum error calculation

[mgong98]

If you do not have full folder down to the 1-004B, then the driver didn’t really load correctly. The 1-004b is created when the OS finds the device on Bus 1 and slave address 0x4b. 0x4B being the only slave address we support for the chip. The i2c-detect -y 1 scans all of bus 1 but doesn’t mean the driver was installed. Can you double check your device tree and all the other files that are associated with the compile of the atmel_mxt_ts.c KCONFIG, Makefile in the /drivers/input/touchscreen directory of your kernel. .config at root for your kernel should have CONFIG_TOUCHSCREEN_ATMEL_MXT=y. Please see the WIKI below. https://github.com/atmel-maxtouch/maXTouch_linux/wiki From: Fabrizio Benatti ***@***.***> Sent: Thursday, July 6, 2023 4:04 AM To: atmel-maxtouch/mxt-app ***@***.***> Cc: Michael Gong - C40415 ***@***.***>; Comment ***@***.***> Subject: Re: [atmel-maxtouch/mxt-app] Info checksum error read=0005D6 with mxt640UD (Issue #105) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe It doesn't seem to work and I honestly can't figure out why. The kernel on my raspberry is 6.1.37 and /sys/bus/i2c/drivers/atmel_mxt_ts/ directory exist but folder "1-004B" is not present. Only SDA, SCL and GND pins are connected between 640UD-HA and rpi [immagine]<https://user-images.githubusercontent.com/27350014/251427200-2fa66190-303b-45f1-973f-ee125ffa51e5.png> I've checked with oscilloscope and signals are ok I continue to get checksum error calculation — Reply to this email directly, view it on GitHub<#105 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANL63NBSLW4K6LBUUBVCODXO2LSNANCNFSM6AAAAAASNO3DEY>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[mgong98]

Hi, Fabrizio. Can you double check where the /CHG line is connected? This would be needed if accessing the part in general and could effect the bootup. Thanks From: Fabrizio Benatti ***@***.***> Sent: Thursday, July 6, 2023 4:04 AM To: atmel-maxtouch/mxt-app ***@***.***> Cc: Michael Gong - C40415 ***@***.***>; Comment ***@***.***> Subject: Re: [atmel-maxtouch/mxt-app] Info checksum error read=0005D6 with mxt640UD (Issue #105) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe It doesn't seem to work and I honestly can't figure out why. The kernel on my raspberry is 6.1.37 and /sys/bus/i2c/drivers/atmel_mxt_ts/ directory exist but folder "1-004B" is not present. Only SDA, SCL and GND pins are connected between 640UD-HA and rpi [immagine]<https://user-images.githubusercontent.com/27350014/251427200-2fa66190-303b-45f1-973f-ee125ffa51e5.png> I've checked with oscilloscope and signals are ok I continue to get checksum error calculation — Reply to this email directly, view it on GitHub<#105 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANL63NBSLW4K6LBUUBVCODXO2LSNANCNFSM6AAAAAASNO3DEY>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[biccius]

the CHG and RESET lines are kept high by pull-up as shown in the module diagrams:

When we use "pure" I2C interface with mxt-app, is required the control of CHG line via GPIO?

Thanks for the important support

[mgong98]

Can you provide a direct email address for further assistance? Thanks From: Fabrizio Benatti ***@***.***> Sent: Friday, July 7, 2023 12:10 AM To: atmel-maxtouch/mxt-app ***@***.***> Cc: Michael Gong - C40415 ***@***.***>; Comment ***@***.***> Subject: Re: [atmel-maxtouch/mxt-app] Info checksum error read=0005D6 with mxt640UD (Issue #105) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe the CHG and RESET lines are kept high by pull-up as shown in the module diagrams: [immagine]<https://user-images.githubusercontent.com/27350014/251663288-1b47b4f4-5ecf-43cf-9e61-acbce629ad09.png> When we use "pure" I2C interface with mxt-app, is required the control of CHG line via GPIO? Thanks for the important support — Reply to this email directly, view it on GitHub<#105 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANL63IFBWZYNNBSLHNHS53XO6Y4XANCNFSM6AAAAAASNO3DEY>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

[mgong98]

Hi, Fabrizio. I believe I know the problem now. Because the driver is not showing up, the kernel has not created the crc_enabled file both for the sysfs interface and the debugfs interface. The file is created to indicate the maXTouch device supports the HA protocol. For sysfs, the file is found in the /sys/bus/i2c/drivers/atmel_mxt_ts/1-004b/ directory. For debugfs, the file is found in the /sys/kernel/debug/atmel_mxt_ts/ directory. There is no way to tell what I2C protocol is supported when using a chip with the HA protocol, so this needs to be flagged by the Linux driver. Along with this is the tx seq no byte that increments on each write. The Tx seq no starts from 0x00 when the maXTouch device boots. The value is stored in the directory to be passed to mxt-app. If using mxt-app standalone without any driver, these flags are unknown, so the mxt-app fails and reads incorrect data. In this case the Infoblock does not match. I would first look at why the atmel_mxt_ts driver is not getting installed. From: Fabrizio Benatti ***@***.***> Sent: Thursday, July 6, 2023 4:04 AM To: atmel-maxtouch/mxt-app ***@***.***> Cc: Michael Gong - C40415 ***@***.***>; Comment ***@***.***> Subject: Re: [atmel-maxtouch/mxt-app] Info checksum error read=0005D6 with mxt640UD (Issue #105) EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe It doesn't seem to work and I honestly can't figure out why. The kernel on my raspberry is 6.1.37 and /sys/bus/i2c/drivers/atmel_mxt_ts/ directory exist but folder "1-004B" is not present. Only SDA, SCL and GND pins are connected between 640UD-HA and rpi [immagine]<https://user-images.githubusercontent.com/27350014/251427200-2fa66190-303b-45f1-973f-ee125ffa51e5.png> I've checked with oscilloscope and signals are ok I continue to get checksum error calculation — Reply to this email directly, view it on GitHub<#105 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AANL63NBSLW4K6LBUUBVCODXO2LSNANCNFSM6AAAAAASNO3DEY>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>