Raspberry pi with 3.2 TFT Screen

drejc

I'm trying to run RuneAudio on Raspberry Pi 3B with a waveshare 3.2TFT touchscreen

Running RuneAudio on RPi works fine on HDMI and with the small TFT screen.
But after I have enabled the screen drivers for the touchscreen the default UI view is not loaded and I see the terminal window on the TFT screen.

Before that (on HDMI) the default RuneAudio UI was loaded a few seconds after booting up.

Any suggestions how to troubleshoot this.

The corresponding script looks like this:

sudo cp -rf ./etc/X11/xorg.conf.d/99-calibration.conf-32  /etc/X11/xorg.conf.d/99-calibration.conf
sudo cp ./waveshare32b-overlay.dtb /boot/overlays/waveshare32b.dtbo
sudo cp ./waveshare32b-overlay.dtb /boot/overlays/
sudo cp -rf ./usr/share/X11/xorg.conf.d/99-fbturbo.conf  /usr/share/X11/xorg.conf.d/

hondagx35

Hi drejc,

you have to switch the output to the correct framebuffer.

See here.

Frank

drejc

The link you gave is for setting up the TFT screen. Not sure to which part you are referencing as it is a long post.

But setting up the 3.2 screen is not my problem ... the screen works fine ... I can see the terminal and I can do the calibration ... etc.
The problem is that the RuneAudio UI that previously loaded on boot to the HDMI screen now stays in terminal mode on the TFT.

So please point me to the correct location in the post ... or maybe I am missing something.

PS: The given post references the Rasbian distribution, but RuneAudio is based on Arch linux.

Yatsushiro

I think it's this bit thats important:

1. First we need to configure the fbturbo video driver to output the display of the Raspberry Pi to the SPI bus instead of the HDMI bus. At the command prompt, enter: sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf.

In this file, find the line that says: Option “fbdev” “/dev/fb0” and change the fb0 to fb1:

LCD 99-fbturbo step 1

The fb0 option tells the video driver to output to HDMI, and the fb1 option tells it to output to the LCD screen. The file should now look like this:

lcd 99-fbturbo step 2

Press Ctrl-X then Y to exit nano and save the changes.

You yourself said your UI displayed correctly on an attached HMDI screen, but you're now using an SPI display, so you need to change the frame buffer from fb0 to fb1

drejc

This is what I currently have in the 99-fbturbo.conf file:

Section "Device"
        Identifier      "Allwinner A10/A13 FBDEV"
        Driver          "fbturbo"
        Option          "fbdev" "/dev/fb1"

        Option          "SwapbuffersWait" "true"
EndSection

To repeat my question ... I see the terminal screen on the 3.2TFT ... but (I assume) xinit doesn't work or doesn't start up correctly.

drejc

Ok ... after some poking around ... I have found following log (from xserver when starting up)

[   762.509] Build Date: 12 February 2016  02:01:40AM
[   762.510]  
[   762.511] Current version of pixman: 0.34.0
[   762.515]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[   762.515] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   762.522] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 10 08:57:43 2017
[   762.525] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   762.526] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   762.527] (==) No Layout section.  Using the first Screen section.
[   762.527] (==) No screen section available. Using defaults.
[   762.527] (**) |-->Screen "Default Screen Section" (0)
[   762.527] (**) |   |-->Monitor "<default monitor>"
[   762.528] (==) No device specified for screen "Default Screen Section".
        Using the first device section listed.
[   762.528] (**) |   |-->Device "Allwinner A10/A13 FBDEV"
[   762.528] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[   762.528] (==) Automatically adding devices
[   762.528] (==) Automatically enabling devices
[   762.528] (==) Automatically adding GPU devices
[   762.528] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   762.528] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[   762.528]    Entry deleted from font path.
[   762.528] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   762.528]    Entry deleted from font path.
[   762.528]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[   762.528] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   762.528]    Entry deleted from font path.
[   762.528]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   762.529] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/OTF/
[   762.529] (==) ModulePath set to "/usr/lib/xorg/modules"
[   762.529] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[   762.529] (II) Loader magic: 0x1e0ee0
[   762.529] (II) Module ABI versions:
[   762.529]    X.Org ANSI C Emulation: 0.4
[   762.529]    X.Org Video Driver: 20.0
[   762.529]    X.Org XInput driver : 22.1
[   762.529]    X.Org Server Extension : 9.0
[   762.532] (++) using VT number 1

[   762.532] (--) controlling tty is VT number 1, auto-enabling KeepTty
[   762.534] (EE) systemd-logind: failed to get session: Unit systemd-logind.service is masked.
[   762.535] (II) no primary bus or device found
[   762.535] (II) LoadModule: "glx"
[   762.536] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   762.556] (II) Module glx: vendor="X.Org Foundation"
[   762.557]    compiled for 1.18.1, module version = 1.0.0
[   762.557]    ABI class: X.Org Server Extension, version 9.0
[   762.557] (==) AIGLX enabled
[   762.557] (II) LoadModule: "fbturbo"
[   762.558] (WW) Warning, couldn't open module fbturbo
[   762.558] (II) UnloadModule: "fbturbo"
[   762.558] (II) Unloading fbturbo
[   762.558] (EE) Failed to load module "fbturbo" (module does not exist, 0)
[   762.558] (EE) No drivers available.
[   762.558] (EE) 
Fatal server error:
[   762.560] (EE) no screens found(EE) 
[   762.561] (EE)

The interesting part is:

[   762.558] (WW) Warning, couldn't open module fbturbo

So this is probably my problem ... any suggestions

drejc

YEY .. GOT IT ...

Section "Device" 
# WaveShare SpotPear 3.5", framebuffer 1
Identifier "uga" 
driver "fbdev" 
Option "fbdev" "/dev/fb1" 
Option "ShadowFB" "off"
EndSection 

Section "Monitor" 
# Primary monitor. WaveShare SpotPear 480x320
Identifier "WSSP" 
EndSection 

Section "Screen" 
Identifier "primary" 
Device "uga" 
Monitor "WSSP" 
EndSection 

Section "ServerLayout" 
Identifier "default" 
Screen 0 "primary" 0 0 
EndSection

Needs to be posted into /etc/X11/xorg.conf.d/99-calibration.conf file ... screen starts up ... touch works

Only downside ... the Rune UI is not adjusted to such a small screen.

hondagx35

Hi drejc,

Only downside ... the Rune UI is not adjusted to such a small screen.

The local browser (display) feature is made for the original raspberry TFT (800 x 480).
What you can do is to adapt the scaling in midori configuration.
Check the file /home/root/.config/midori/config and change zoom-level.

[settings]
default-encoding==UTF-8
enforce-96-dpi=true
enable-developer-extras=true
enable-site-specific-quirks=true
enable-javascript=true
default-charset=ISO-8859-1
last-window-width=800
last-window-height=480
last-panel-position=523
last-panel-page=5
location-entry-search=
toolbar-items=Back,Forward,ReloadStop,Location,Search,
find-while-typing=true
zoom-level=0.7
middle-click-opens-selection=false
homepage=http://localhost
tabhome=http://localhost
download-folder=/home/army
http-proxy=127.0.0.1:8118
maximum-cache-size=50
maximum-history-age=0
load-on-startup=MIDORI_STARTUP_HOMEPAGE
proxy-type=MIDORI_PROXY_NONE
user-agent=Mozilla/5.0 (X11; Linux) AppleWebKit/538.15 (KHTML, like Gecko) Chrome/18.0.1025.133 Safari/538.15 Midori/0.5
user-stylesheet-uri=file:///root/.local/share/midori/styles/local-styles.css

[extensions]
libaddons.so=true

Frank

Yatsushiro

I'd also look at installing Rerns UI updates, with some features and options that should mak eit work better on smaller screens:

#4207

drejc

Cool will definitely play around with it, but with a 320x240 touchscreen you are really limited. And touch with fingers needs large target areas.

Apart from that it might be a good idea to make on UI with only basic controls (limited for really small screens)
In my case I would only need a play/pause button, play queue, volume control and power off, as I intend to use this screen only for basic controls.

Other things can be adjusted on a proper screen, or via smart-phone.

If someone can point me to the correct PHP, CSS and JavaScript files I can give it a try.