The Atmel MaXTouch controllers have a configuration file saved in their internal NVRAM. On rare occasions, one may need those files for some purpose.
Attention: it is very likely that you don't need to get the configuration from the controller. Avoid messing up with it, so you avoid permanently damaging the controller.
This article focuses on specifically how to retrieve the configuration from the Capacitive Touch Display 10.1" LVDS on Torizon. It most likely works for the Capacitive Touch Display 7" Parallel, or at least very similar instructions. The configuration is retrieved using the mxt-app and you should read the README.md of the repo for further details.
This article complies to the Typographic Conventions for Torizon Documentation.
Build a container named
mxt-app using the Dockerfile below:
Warning: the Dockerfile provided in this article may not comply with best practices. It is intended as a quickstart only.
# cd /home/torizon # mkdir mxt # docker run --rm -it --privileged -v /dev:/dev -v /tmp:/tmp -v /run/udev/:/run/udev/ -v /sys:/sys -v /home/torizon/mxt:/mxt mxt-app
You'll later save the config file in the bind-mount /home/torizon/mxt.
In the interactive bash session inside the container, find the i2c controller and address:
## ls /sys/bus/i2c/drivers/atmel_mxt_ts/ 4-004a bind uevent unbind
In this case, it is 4-004a. Now you can dump the config to a file:
## cd mxt ## mxt-app -d i2c-dev:4-004a --save mxt.xcfg Version:1.28-25-g927e026 Registered i2c-dev adapter:4 address:0x4a REPORTALL command issued Timeout Read config from device Saved config to mxt.xcfg in .xcfg format
## cd mxt ## mxt-app -d i2c-dev:4-004a --save mxt.bin Version:1.28-25-g927e026 Registered i2c-dev adapter:4 address:0x4a REPORTALL command issued Timeout Read config from device Saved config to mxt.bin in OBP_RAW format
Exit the container and copy the file to your PC from /home/torizon/mxt/mxt.xcfg using, for instance,
# scp /home/torizon/mxt/mxt.xcfg <user>@<ip>:<path to save file on your PC>