element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • 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
Raspberry Pi
  • Products
  • More
Raspberry Pi
Raspberry Pi Forum Official 7" Touchscreen error, touch not functional
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 5 replies
  • Subscribers 654 subscribers
  • Views 2046 views
  • Users 0 members are here
Related

Official 7" Touchscreen error, touch not functional

MarionTheGoat
MarionTheGoat over 1 year ago

I just purchased two Raspberry Pi model 4B 4GB along with two Element14 7" touch screen displays from SparkFun.  Yesterday I downloaded the latest Pi Imager and wrote the current 64-bit Debian with Desktop to SD card and assembled the hardware for one set per current instructions.  Everything is spanking new.

The screen displays fine... but the touch is non-functional.  Much of the discussion on this topic centers on ft5406, but it appears that's all out of date.  I did a dmesg | grep -i ft5 and it returned the following :

edt_ft5x06 10-0038: supply vcc not found, using dummy regulator

edt_ft5x06 10-0038: supply iovcc not found, using dummy regulator

edt_ft5x06: 10-0038 touchscreen probe failed

edt_ft5x06: probe of 10-0038 failed with error -5

I'm unable to find any posts on this.  Not sure what the regulator messages are about but that may be a red herring...  looks like the probe failure is a major indicator though.

I've repeatedly checked the ribbon cable, have even substituted the ribbon cable from the other display kit.  Not sure where to go from here.  I have reasonable technical skills but I'm no expert on the Pi stack.

Help?

Thanks,

Lonnie

  • Sign in to reply
  • Cancel
Parents
  • shabaz
    0 shabaz over 1 year ago

    Other instructions are ambiguous. If you follow this blog post to the letter, playing close attention to all the photos there too (pay attention to the touchscreen flex photo, and examine the connector there too, in case it is opened or disconnected), it will work, provided that there is no fault with the display or software issues:  Raspberry Pi 7” Capacitive Touch Display: Assembly and Enclosure 

    If you deviate from that, or go off and use some other power supply rather than the official one, then all bets are off.

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • MarionTheGoat
    0 MarionTheGoat over 1 year ago in reply to shabaz

    Thank you for the response --  I did follow the instructions in the link to the letter... with the exception of soldering the power wires.  Other sources suggested use of pin 4 instead of pin2 for +5v but doesn't look like that matters and I've tried both. 

    I went ahead and assembled the second Pi / Display set... and moved the SD card over to them ( I only have one to work with at the moment ).  Get the exact same result.  So hardware is identical to my initial case, and same exact OS. 

    I've made no changes or additional installations on the OS... I did try a couple settings in /boot/config.txt which I've since removed.  I also did invert the display ( necessary ) in the Preferences... setting that back to Normal doesn't have any effect on the issue.  I've only changed one thing in any given experiment and then reverted.

    So I'm concluding that the OS or supporting libraries the Pi folks currently have out there has a problem with the touchscreen somehow... being that both the 4B and the display have been around a while, doesn't seem like hardware itself would be at fault here.  But the problem renders the display half-useless.  

    I'm expecting others are going to experience the same issue.  error -5 is above my pay grade, I've run out of ideas.

    L

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • shabaz
    0 shabaz over 1 year ago in reply to MarionTheGoat

    If you have a Pi 3B lying around, it would be worth trying that out too, just to narrow down further. The reason is, the 7" display was created in the era of Pi 3B, and Pi 4B is temperamental in terms of its power requirements, and the processor has significant differences that can break operation with software or drivers for the older Pi 3B.  I've encountered this so frequently with other hardware. that I automatically prefer to use a Pi 3B if I can help it, over a Pi 4B, if I'm interfacing to hardware and using software that is out of my control. 

    This might not be a solution if you absolutely need the performance of a Pi 4 of course. It depends on your end use-case.

    Anyway, since you have followed the blog post to the letter, I think you certainly have connected it correctly, and it may be worth raising the issue on the Pi forum (i.e. raspberrypi.com forum) too, for anyone familiar with the drivers for it to recall if anything has changed in this area with the latest OS.

    I have a single 7" touchscreen but it is in use (with a Pi 3B running an older release), so I cannot test that unfortunately. The touch part is indeed useful to have (the display is quite low-res, so only really usable for appliance/kiosk-like tasks, not for general use as a computer display, so the touch interface is convenient).

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • MarionTheGoat
    +1 MarionTheGoat over 1 year ago in reply to MarionTheGoat

    I did manage to find the exact issue posted here : https://github.com/raspberrypi/linux/issues/5619  Looks like kernel 6.1.53 broke the touchscreen... I ended up with 6.1.54 from the Pi Installer... Doing a sudo rpi-update stable took the firmware to .58 which seems to have fixed the issue.

    This issue is now closed.

    • Cancel
    • Vote Up +5 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
Reply
  • MarionTheGoat
    +1 MarionTheGoat over 1 year ago in reply to MarionTheGoat

    I did manage to find the exact issue posted here : https://github.com/raspberrypi/linux/issues/5619  Looks like kernel 6.1.53 broke the touchscreen... I ended up with 6.1.54 from the Pi Installer... Doing a sudo rpi-update stable took the firmware to .58 which seems to have fixed the issue.

    This issue is now closed.

    • Cancel
    • Vote Up +5 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
Children
  • shabaz
    0 shabaz over 1 year ago in reply to MarionTheGoat

    Glad it's resolved, and thanks for posting details about the solution!

    • Cancel
    • Vote Up +1 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