element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Software Application Development Touchscreen Issue
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 7 replies
  • Subscribers 312 subscribers
  • Views 475 views
  • Users 0 members are here
Related

Touchscreen Issue

Former Member
Former Member over 9 years ago

Hi,

I am setting up an application using the Xylon reference design for the MicroZed + Avnet 7" touchscreen.  The graphics work fine but the touchscreen is not working.

I managed to find this text in the boot sequence so it may help shed light on the issue:

tmg120_ts 0-0020: tmg120_ts: failed to read firmware version
tmg120_ts: probe of 0-0020 failed with error -5

Is anyone know what is/could be wrong and what I should do about it?

Thanks,

Tim

  • Sign in to reply
  • Cancel
  • Former Member
    0 Former Member over 9 years ago

    After looking at the Microzed example code that came with the kit I found the chip was at I2C address 1F rather than 20 as pointed to in my Linux driver.  I changed that and then the message went away and was replaced with one that said the status was 0xEA.  However it doesn't seem to work still.

    Tim

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • zedhed
    0 zedhed over 9 years ago

    Hi Tim,

    The issue you are seeing stems from a Linux driver that was never updated for this reference design to support the newer ALI3 touch controller command set.

    Since this appears to be targeted to your MicroZed, one simple option would be to connect a mouse to MicroZed USB host port in order to gain access to the pointer in order to launch demos from the icons on the home screen.

    I see that your local Avnet FAE is also involved so I can work with them to we can see if there are any other options that can help get your demo working.

    Regards,

    -Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago in reply to zedhed

    Hi, Kevin

    I've also been troubled with the same issue for days. So according to what you explained, the newer ALI3 touch controller is actually not supported by even the latest Linux driver. So when is Avnet going to update the Linux driver to support the newer ALI3 touch controller? It is very important to me because my project requires that the touch screen must be supported under a Linux OS. Thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago in reply to Former Member

    Hello,

    Has the issue been solved? I also want to use this touch screen. Do you get new Linux driver of tms120?
    thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago in reply to Former Member

    Hello,
    I am currently working with the MicroZed board interfaced with an I/O career card and an ALI3 based touchscreen. I am also facing the same problem as yours about the capacitive controller. I performed the same operations and got the same results, without getting the controller to work properly. I also found a sourcecode on the ELMG website (http://www.elmgdigitalpower.com/touchscreen-driver-tmg120/). I compiled it successfully for my kernel but, still, I can't get the controller to work. I can't figure out what am I missing, if there is some parameters to be set properly in my devicetree file or something else. May I ask you if you solved this issue and, if yes, may I ask how did you make it?

    Thanks in advance.
    Best regards,

    Emmanuel

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • zedhed
    0 zedhed over 9 years ago in reply to Former Member

    Hi Emmanuel,

    Is there any sign that your display is communicating with the driver?

    There does need to be a device tree entry to describe the slave device you are targeting.  Xylon did the integration work to get this driver working on their reference design so I would recommend downloading that package and using their device tree as a reference for what entries are needed for your own device tree.

    http://www.logicbricks.com/logicBRICKS/Reference-logicBRICKS-Design/Xylon-Advanced-Display-Controller-MicroZed.aspx

    Regards,

    -Kevin

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 9 years ago in reply to zedhed

    Hello Kevin,

    There has been some improvement. I was actually confronted to another problem. I have been using the 3.6.0 version of the kernel for Xilinx and applied the patch, as indicated in the tutorial I found on this site about the installation of Ubuntu on the MicroZed (with the I/O career and the ALI3 touchscreen). When I used the devicetree.dts file provided by the kernel, I had indeed nothing in the /dev/input directory but "mice". When I took instead the devicetree.dts file I found in the Ubuntu image sources, I got the peripheral created correctly. After examining both the files, I saw that the IRQ values for the tmg120 node set by default in the kernel were wrong. But after setting the right values, still no reaction from the controller when I press the screen.
    I then replaced, in the sources of the 3.6 kernel, the tmg120_ts.c file provided by Tim King and recompiled. Now I am able to see the cursor move on the screen when I press it, however I can't get it calibrated properly. I do not know if this is because the screen is extremely sensitive (I am also working in an "electrically noisy" environment if I may say so) or because the driver needs to be improved (however thank you Tim for your work which allowed me to make a major step further!)
    I am now giving a look at the reference design provided by Xylon as you suggest.
    Thanks a lot for your help.

    Best regards,


    Emmanuel

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube