After receiving numerous requests for assistance via PM, for the benefit of the Volumio community:
Issue Summary:
After upgrading to Volumio version 3.779, users reported that the Raspberry Pi official touchscreen display stopped functioning. This was due to missing or misconfigured parameters in the system configuration.
Resolution:
To resolve the issue, you need to update the /boot/usrconfig.txt file with the necessary parameters and overlays to enable the touchscreen functionality. Follow these steps:
Steps to Fix:
- Access the Raspberry Pi: Use SSH or connect a keyboard and monitor to access the terminal.
- Edit the Configuration File: Open the /boot/usrconfig.txt file using a text editor:
sudo nano /boot/usrconfig.txt
- Add or Update the Following Parameters:
# Set device scope
[all]
# Enable display vc4 autodetection
display_auto_detect=1
# Add touchscreen-specific overlays
dtoverlay=rpi-ft5406
dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch
# Ensure backlight control works
gpio=18=op,dh
Save and Exit: In nano, press CTRL+O, then Enter to save. Press CTRL+X to exit.
Reboot the Device: Apply the changes by rebooting the Raspberry Pi:
sudo reboot
Explanation of Parameters:
- [all]: Any configuration specified under the scope
[all]
in the configuration file applies to all devices connected to the Raspberry Pi. - display_auto_detect=1: Automatic Display Detection. When set to
1
, the Raspberry Pi will automatically detect the type of display connected at boot time (e.g., an HDMI monitor or the official Raspberry Pi touchscreen). - dtoverlay=rpi-ft5406: Activates the touchscreen controller.
- dtoverlay=vc4-kms-v3d & dtoverlay=vc4-kms-dsi-7inch: Configure the graphics and display for the official 7-inch touchscreen.
- gpio=18=op,dh: Configures GPIO 18 for backlight control.
The Touch Display Plugin
There is a dedicated thread for configuring and use of the plug-in and as such, all related questions should be posted here:
Additional Notes:
- Make sure to power down after making changes.
- If the issue persists, double-check the edits and connections.
- If using HDMI simultaneously, you might need additional configuration.
This fix has resolved the issue for most users experiencing problems with version 3.779 or newer. Let us know if further assistance is needed!
Kind Regards,