2018/03/11

Running Volumio 2 on a Raspberry Pi 2 model B with a 3.5" Touchscreen


I was pleasantly surprised with how well Volumio 2 runs out of the box on my old Raspberry Pi 2 model B using an external USB DAC (in my case, Behringer UCA222). As a next step, I wanted to add a small 3.5 inch display that connects to the 26 GPIO pins of my Pi 2 B.

The setup of the 3.5" LCD screen is a bit tougher than expected, but after a lot of googling and trial&error I got the LCD touchscreen fully working with Volumio 2. It seems like the same display is sold under different brands.

These are the steps to get the display working:
  • get Volumio running on your Raspberry Pi:
  • install and activate the Touch Plugin
    • 2019-02: the plugin install was stuck with an interactive keyboard choice. I ran the follwing commands on the raspberry pi (ssh volumio)
      sudo dpkg --configure -a
      sudo apt-get install -y xinit xorg openbox libexif12
    • try to remove / reinstall the plugin
  • connect to your Raspberry Pi CLI through ssh (username: volumio; password: volumio) and execute the following commands
    • download the display driver:
      git clone https://github.com/goodtft/LCD-show
    • run these few commands (handpicked from the LCD35-show script -- do NOT run the script!):
      cd LCD-show/
      sudo mkdir /etc/X11/xorg.conf.d
      sudo cp ./usr/tft35a-overlay.dtb /boot/overlays/
      sudo cp ./usr/tft35a-overlay.dtb /boot/overlays/tft35a.dtbo
      sudo cp -rf ./usr/99-calibration.conf-35  /etc/X11/xorg.conf.d/99-calibration.conf
      sudo mkdir -p /usr/share/X11/xorg.conf.d/
      sudo cp -rf ./usr/99-fbturbo.conf  /usr/share/X11/xorg.conf.d/
    • modify the 99-calibration.conf file and add the Driver "evdev" option
      • sudo nano /etc/X11/xorg.conf.d/99-calibration.conf
      • the file should be:
        Section "InputClass"
          Identifier "calibration"
          MatchProduct "ADS7846 Touchscreen"
          Option "Calibration" "3936 227 268 3880"
          Option "SwapAxes" "1"
          Driver "evdev"
        EndSection
      • save the file (Control-X)
    • modify the /boot/config.txt
      • sudo nano /boot/config.txt
      • add the last line:
        initramfs volumio.initrd
        gpu_mem=32
        max_usb_current=1
        dtparam=audio=on
        audio_pwm_mode=2
        dtparam=i2c_arm=on
        disable_splash=1
        hdmi_force_hotplug=1
        dtoverlay=tft35a
      • save the file (Control-X)
    • install missing packages:
      • sudo apt update
      • sudo apt install lightdm
      • sudo apt install xserver-xorg-input-evdev
After a reboot, everything works fine :). 


The final product is functional, but not perfect: the boot time takes a few minutes and chromium in kiosk mode is not very snappy. This might be a limitation of the older Raspberry Pi hardware. But as a simple display and for basic pause/play interaction, it works.

You can add some finetuning by preventing the "crashed tabs" dialog from chromium and by disable the sleep mode.

sudo nano /opt/volumiokiosk.sh
#!/bin/bash
#prevent sleep (remove any other xset commands)
xset -dpms
xset s off

#prevent the 'crashed' dialog box: (keep each sed on 1 line)
sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' /data/volumiokiosk/Default/Preferences
sed -i 's/"exit_type":"Crashed"/"exit_type":"None"/' /data/volumiokiosk/Default/Preferences

openbox-session &
while true; do
  /usr/bin/chromium-browser \
    --no-touch-pinch \
    --kiosk \
    --no-first-run \
    --disable-3d-apis \
    --disable-breakpad \
    --disable-crash-reporter \
    --disable-infobars \
    --disable-session-crashed-bubble \
    --disable-translate \
    --user-data-dir='/data/volumiokiosk'        --no-sandbox     http://localhost:3000
done

2019-03:  some additional tweaks.
  • If you want to hide the mouse cursor:
sudo nano /lib/systemd/system/volumio-kiosk.service
ExecStart=/usr/bin/startx /etc/X11/Xsession /opt/volumiokiosk.sh -- -nocursor
  • hacking the css for a more compact layout for the 3,5" display (warning: layout on phones is a bit off)
cp /volumio/http/www/styles/app-*.css /volumio/http/www/styles/app-css.orig
sed -i "s/\(\#trackManager{.*\)top:50/\1top:85/g" /volumio/http/www/styles/app-*.css
sed -i "s/\.knobWrapper{position/@media \(max-width:767px\){.knobWrapper{zoom:.40;position:relative;width:210px;height:210px;margin:0 auto 15px}}.knobWrapper{position/g" /volumio/http/www/styles/app-*.css

References:


11 comments:

Zach said...

I used this method of yours last month and it was working fine.

I attempted to follow your updated instructions and use the previous Volumio image, unfortunately it no longer works.

Michaël Peeters said...

some ideas:
- make sure to backup your sd-card before any change / update
- before applying the LCD-specific config, validate that Volumio is fully working with an hdmi screen plugged in.
- I added the full /boot/config.txt contents
- compare the output from your working setup and the broken one:
- sudo lsmod
fb_ili9486 3213 1
fbtft 32647 1 fb_ili9486
ads7846 13075 0
syscopyarea 3161 1 fbtft
sysfillrect 3716 1 fbtft
sysimgblt 2422 1 fbtft
fb_sys_fops 1677 1 fbtft
- dmesg
[ 19.777376] ads7846 spi0.1: touchscreen, irq 177
[ 19.787946] input: ADS7846 Touchscreen as /devices/platform/soc/20204000.spi/spi_master/spi0/spi0.1/input/input3
[ 19.971009] fbtft: module is from the staging directory, the quality is unknown, you have been warned.
[ 20.352359] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned.
[ 20.353534] fbtft_of_value: regwidth = 16
[ 20.353551] fbtft_of_value: buswidth = 8
[ 20.353564] fbtft_of_value: debug = 0
[ 20.353571] fbtft_of_value: rotate = 90
[ 20.353578] fbtft_of_value: fps = 30
[ 20.353586] fbtft_of_value: txbuflen = 32768
- contents /var/log/Xorg*log should contain:
[ 78.217] (II) FBTURBO(0): hardware: fb_ili9486 (video memory: 300kB)
[ 78.217] (**) FBTURBO(0): Option "fbdev" "/dev/fb1"

Zach said...

Thanks Michael for your quick response:

Here are my outputs:


evdev 24576 1
ads7846 20480 0
fb_ili9486 16384 2
fbtft 45056 1 fb_ili9486
syscopyarea 16384 1 fbtft
sysfillrect 16384 1 fbtft
sysimgblt 16384 1 fbtft
hwmon 16384 1 ads7846
fb_sys_fops 16384 1 fbtft




[ 10.826388] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 10.827632] snd_bcm2835: unknown parameter 'index' ignored
[ 10.834071] bcm2835_alsa bcm2835_alsa: card created with 8 channels
[ 11.043016] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 11.221343] fbtft: module is from the staging directory, the quality is unknown, you have been warned.
[ 11.231581] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 11.232023] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 11.243028] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned.
[ 11.243905] fbtft_of_value: regwidth = 16
[ 11.243917] fbtft_of_value: buswidth = 8
[ 11.243925] fbtft_of_value: debug = 0
[ 11.243932] fbtft_of_value: rotate = 90
[ 11.243939] fbtft_of_value: fps = 30
[ 11.243946] fbtft_of_value: txbuflen = 32768
[ 11.252139] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43455-sdio.bin for chip 0x004345(17221) rev 0x000006
[ 11.252567] usbcore: registered new interface driver brcmfmac
[ 11.254386] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 11.443050] snd-rpi-hifiberry-dacplus soc:sound: pcm512x-hifi <-> 3f203000.i2s mapping ok
[ 11.725752] random: crng init done
[ 11.725774] random: 7 urandom warning(s) missed due to ratelimiting
[ 11.802078] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[ 11.802699] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 9.10.105 Compiler: 1.29.4 ClmImport: 1.36.3 Creation: 2018-03-09 18:56:28
[ 11.808184] systemd-journald[167]: Received request to flush runtime journal from PID 1
[ 11.935844] graphics fb1: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 32 KiB buffer memory, fps=33, spi0.0 at 16 MHz
[ 11.936812] ads7846 spi0.1: spi0.1 supply vcc not found, using dummy regulator
[ 11.937400] ads7846 spi0.1: touchscreen, irq 170
[ 11.937990] input: ADS7846 Touchscreen as /devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/input/input0
[ 12.178539] brcmfmac: power management disabled
[ 13.114607] brcmfmac: power management disabled
[ 13.921990] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 14.384618] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 14.515992] nf_conntrack version 0.5.0 (14336 buckets, 57344 max)
[ 20.891589] brcmfmac: power management disabled
[ 35.351953] Under-voltage detected! (0x00050005)
[ 43.671805] Voltage normalised (0x00000000)


zach said...

this is what I got for the xorg log

[ 16.691] (II) FBTURBO(0): if this is wrong and needs to be fixed, please check ./configure log
[ 16.696] (==) RandR enabled
[ 16.731] (II) SELinux: Disabled on system
[ 16.749] (II) AIGLX: Screen 0 is not DRI2 capable
[ 16.749] (EE) AIGLX: reverting to software rendering
[ 18.470] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 18.471] (II) AIGLX: Loaded and initialized swrast
[ 18.471] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 18.853] (II) config/udev: Adding input device ADS7846 Touchscreen (/dev/input/event0)
[ 18.853] (**) ADS7846 Touchscreen: Applying InputClass "evdev touchscreen catchall"
[ 18.853] (**) ADS7846 Touchscreen: Applying InputClass "libinput touchscreen catchall"
[ 18.853] (**) ADS7846 Touchscreen: Applying InputClass "calibration"
[ 18.853] (II) LoadModule: "evdev"
[ 18.854] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 18.891] (II) Module evdev: vendor="X.Org Foundation"
[ 18.891] compiled for 1.18.4, module version = 2.10.3
[ 18.891] Module class: X.Org XInput Driver
[ 18.891] ABI class: X.Org XInput driver, version 22.1
[ 18.891] (II) Using input driver 'evdev' for 'ADS7846 Touchscreen'
[ 18.891] (**) ADS7846 Touchscreen: always reports core events
[ 18.891] (**) evdev: ADS7846 Touchscreen: Device: "/dev/input/event0"
[ 18.891] (--) evdev: ADS7846 Touchscreen: Vendor 0 Product 0
[ 18.891] (--) evdev: ADS7846 Touchscreen: Found absolute axes
[ 18.891] (--) evdev: ADS7846 Touchscreen: Found x and y absolute axes
[ 18.892] (--) evdev: ADS7846 Touchscreen: Found absolute touchscreen
[ 18.892] (**) Option "SwapAxes" "1"
[ 18.892] (II) evdev: ADS7846 Touchscreen: Configuring as touchscreen
[ 18.892] (**) evdev: ADS7846 Touchscreen: YAxisMapping: buttons 4 and 5
[ 18.892] (**) evdev: ADS7846 Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWh$
[ 18.892] (**) Option "config_info" "udev:/sys/devices/platform/soc/3f204000.spi/spi_master/spi0/spi$
[ 18.892] (II) XINPUT: Adding extended input device "ADS7846 Touchscreen" (type: TOUCHSCREEN, id 6)
[ 18.892] (II) evdev: ADS7846 Touchscreen: initialized for absolute axes.
[ 18.892] (**) ADS7846 Touchscreen: (accel) keeping acceleration scheme 1
[ 18.892] (**) ADS7846 Touchscreen: (accel) acceleration profile 0
[ 18.892] (**) ADS7846 Touchscreen: (accel) acceleration factor: 2.000
[ 18.892] (**) ADS7846 Touchscreen: (accel) acceleration threshold: 4
[ 18.893] (II) config/udev: Adding input device ADS7846 Touchscreen (/dev/input/mouse0)
[ 18.894] (**) ADS7846 Touchscreen: Applying InputClass "calibration"
[ 18.894] (II) Using input driver 'evdev' for 'ADS7846 Touchscreen'
[ 18.894] (**) ADS7846 Touchscreen: always reports core events
[ 18.894] (**) evdev: ADS7846 Touchscreen: Device: "/dev/input/mouse0"
[ 18.894] (EE) evdev: ADS7846 Touchscreen: Unable to query fd: Inappropriate ioctl for device
[ 19.030] (EE) PreInit returned 2 for "ADS7846 Touchscreen"
[ 19.030] (II) UnloadModule: "evdev"


Let me know if there is something here that I am not seeing.

Thank you!

Michaël Peeters said...

Hi Zach,
In your logs I see the following "error":

Under-voltage detected! (0x00050005)

Might indicate an issue with your USB Power. Definitely try with another power source

Other than that, I'm afraid I'm out of ideas. It seems like you're using a more recent Raspberry Pi (Model 3?). Might be that I'm more lucky with the "Raspberry Pi Model B Rev 2" ?

You could also try to setup a bare bone raspbian with LCD and try to compare what config might make a difference? (e.g. /boot/config.txt).

Michaël



zach said...

Thank your for your help, but unfortunately after 43 separate installs from scratch, it is a complete failure.

I am starting to believe that there is more to it than the script you have provided, as I have looked elsewhere and have not been able to get it running.

It doesn't even detect the device from the drivers.

Michaël Peeters said...

hi zach,

some questions
- did you test with other power adapters?
- are you using a rpi 3?
- did you try plain raspbian
- did you try with another older volumio instance? https://volumio.org/forum/older-volumio-versions-img-files-t7009.html

from your logs (Xorg), it seems like the screen is OK?


Anyway, i'm afraid i'm out of ideas... i can send you my image to test, contact me on mich dot peeters
at gmail


Matthias said...

Thanks for your howto.
I tried to get my 3.5 touchscreen running with my Pi3 and the volumio plugin, but it didn't work.
Using your howto I managed it but there is a little problem I can not solve.

When using the stylus as input the touchscreen seems to be mirrored. When moving to the right the arrow is pointing to the left. Same with up and down.
How ca I fix this? Is there a way to calibrate the screen?

Also I would like to rotate the screen by 180 degree.
I tried to edit
/boot/config.txt
and add this line:
lcd_rotate=2
this didn't do anything.

Do you have any idea?

Thanks
Matthias

Michaël Peeters said...

hi Matthias,

the stylus input is configured in /etc/X11/xorg.conf.d/99-calibration.conf
check the Calibration and SwapAxes options. Start with the original configuration from github for those items instead of mine.
Michaël

Matthias said...

Hi Michael,
I will try if that work for me.
I hoped there would be a calibration script.

Thanks
Matthias

Michaël Peeters said...

Hi Matthias,

I did some experiments last year with calibration scripts, but in my case it wasn't needed, the default settings are ok.

Anyway, you can research it further:

- "xinput-calibrator": sudo apt install xinput-calibrator
see: https://www.raspberrypi.org/forums/viewtopic.php?t=78805
- https://github.com/gamelaster/evdev-calibration