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 & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • 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
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • 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 & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Avnet Boards General Touch interface on microzed touch display does not generate interrupt
  • 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 1 reply
  • Subscribers 353 subscribers
  • Views 164 views
  • Users 0 members are here
Related

Touch interface on microzed touch display does not generate interrupt

jstoezel
jstoezel over 11 years ago

Hi:

I am running the console demonstration project that comes with the ALI3 touch display kit, running on a Microzed.


While the demo application (console version) runs and displays expected screens on the LCD, the touch interface does not seem to generate interrupts.


I can see the interrupt pulse on the PCAP Development connector (J1), pin #3 (IRQ), on the ALI3 Sharp7 adapter board. I can see the same pulse on the other side of the display port cable on connector on connector PMOD2 (CON101), pin #8 of the PMOD-ALI3 board. But the IRQ handler never gets called.


There's a few confusing (to me) observations at this point with regards to the interrupt handling. It seems the design is using the PL to PS interrupt IRQ_F2P mapped to IRQ ID 91 of the GIC's SPI. Looking at Table 7-3 of UG585, this interrupt is described as Rising edge/ high level (configured rising edge in the console application). Looking at the actual interrupt signal going from the LCD to the Microzed, the IRQ seems to be active low (low level pulses, idling high).


I guess I can see how the design can still work as is since the IRQ is configured as active on rising edge. Still it doesn't look like the interrupt vector is effectively invoked.


What would be the steps to check that the interrupt is properly enabled?

JS

  • Sign in to reply
  • Cancel
  • jstoezel
    0 jstoezel over 11 years ago

    I got this fixed. It seems that the xlconcat component has been updated since the tutorial was released. xlconcat endianess is opposite now, meaning that the IRQ_F2P mapping is opposite.

    The change in endianess means that while ali3_touch_irq should be mapped to bit 15 of the IRQ_F2P, the new version of xlconcat maps it to bit 0.

    Once I remapped the IRQ to the proper bit the touch interface started working.

    The tutorial for the touch LCD might require updating.

    • 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 © 2026 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