Display UI on Waveshare 3.5 inch TFT

Display UI on Waveshare 3.5 inch TFT - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Display UI on Waveshare 3.5 inch TFT (/showthread.php?tid=258)

Pages: 1 2

RE: Display UI on Waveshare 3.5 inch TFT - seta_vn - 07-17-2018

i got the same problem with Moode 4.2 but mine is the 5" waveshare screen

RE: Display UI on Waveshare 3.5 inch TFT - eric00886 - 11-15-2020

(06-28-2018, 08:56 AM)marcelvb Wrote: Hello,

I´m a newbie to moode audio and manage to get it working and install the drivers to my touchscreen. The screen goes from white to black so the dev fb1 works. The problem is the screen stays black and i can not see the UI, in the systems menu ive checked the touchscreen an lcd are -on-. What am i'm doing wrong? Is there someone with the same screen who can write me a tutorial?
Realy impressed by the sound, keep up the good work!

Is anything new coming up? I have the same issues.

RE: Display UI on Waveshare 3.5 inch TFT - Alaini93 - 11-19-2020

And why not using the latest 6.7.1 Moode?
try first to install your hdmi screen without installing the driver.
My config.txt looks like that, I have a Kuman 3.5 hdmi and another small one 1.3" screen

disable_splash=1
disable_overscan=1
hdmi_drive=2
hdmi_blanking=1
hdmi_ignore_edid_audio=1
hdmi_force_hotplug=1
hdmi_group=2
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=audio=off
dtoverlay=hifiberry-dacplus
#dtoverlay=disable-wifi
#dtoverlay=disable-bt
dtparam=i2c_arm_baudrate=400000
#hdmi_group=1
hdmi_mode=4
dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900
display_hdmi_rotate=2
avoid_warnings=1

it will not be touchscreen at first.

RE: Display UI on Waveshare 3.5 inch TFT - eric00886 - 11-21-2020

(11-19-2020, 05:53 PM)Alaini93 Wrote: And why not using the latest 6.7.1 Moode?
try first to install your hdmi screen without installing the driver.
My config.txt looks like that, I have a Kuman 3.5 hdmi and another small one 1.3" screen

disable_splash=1
disable_overscan=1
hdmi_drive=2
hdmi_blanking=1
hdmi_force_edid_audio=1
hdmi_force_hotplug=1
hdmi_group=2
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=audio=off
dtoverlay=hifiberry-dacplus
#dtoverlay=disable-wifi
#dtoverlay=disable-bt
dtparam=i2c_arm_baudrate=400000
hdmi_group=1
hdmi_mode=1
dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900
display_hdmi_rotate=2
avoid_warnings=1

it will not be touchscreen at first.

Thanks for your reply. I study your config.txt first.

I use Moode Audio 6.7.1 and 7 hdmi waveshare touchscreen work well. Local UI is very good design. Big Grin

Now, I got problem in 3.5 SPI touchscreen. This is a process full of fun and tears and the only problem is I am still in the process. Confused

RE: Display UI on Waveshare 3.5 inch TFT - Alaini93 - 11-21-2020

At first I got a 3.5 spi, I couldn't figure it out, so I switched to a 3.5 hdmi to show the UI.

RE: Display UI on Waveshare 3.5 inch TFT - eric00886 - 11-21-2020

(11-21-2020, 04:39 AM)Alaini93 Wrote: At first I got a 3.5 spi, I couldn't figure it out, so I switched to a 3.5 hdmi to show the UI.

Yes, HMI cable is good, but SPI cable need to "try".

As study here: some spi driver will rewrite some file Moode Audio needed then broken the system. Sad

RE: Display UI on Waveshare 3.5 inch TFT - gattonero - 04-23-2021

(11-21-2020, 12:50 AM)eric00886 Wrote:
(11-19-2020, 05:53 PM)Alaini93 Wrote: And why not using the latest 6.7.1 Moode?
try first to install your hdmi screen without installing the driver.
...
it will not be touchscreen at first.

Thanks for your reply. I study your config.txt first.

I use Moode Audio 6.7.1 and 7 hdmi waveshare touchscreen work well. Local UI is very good design.
Now, I got problem in 3.5 SPI touchscreen. This is a process full of fun and tears and the only problem is I am still in the process.

Hello

Newbie here.

I have the Adafruit 3.5TFT installed on a RPi3, with a nicely working Moode (release 7.10) that I've been enjoying for about a week. It's all working fine, minus the display.
The screen I've received yesterday, I've been trying to install with the usual procedures, then tried the ones from here: https://cdn-learn.adafruit.com/downloads/pdf/adafruit-pitft-3-dot-5-touch-screen-for-raspberry-pi.pdf, to no avail.
I 've used the code

Code:
cd ~

sudo apt-get install -y git python3-pip

sudo pip3 install --upgrade adafruit-python-shell click==7.0

git clone https://github.com/adafruit/Raspberry-Pi-Installer-Scripts.git

cd Raspberry-Pi-Installer-Scripts

followed by

Code:
sudo python3 adafruit-pitft.py --display=35r --rotation=90 --install-type=fbcp

All went ok.
Then I'm asked to reboot, which goes on, but when I reconnect Putty (I've created the blank SSH file in the /root) it's a new session and the command that follows

Code:
sudo python3 adafruit-pitft.py

which is supposed to allow me all the config, no surprise it gives me:

Quote:"python3: can't open file 'adafruit-pitft.py': [Errno 2] No such file or directory"

So nothing else happens.
The screen has always stayed white never showing anything... at least I know it powers up and it's something related to the OS and not the Moode Audio release.

Anything particular I should look for? I understand that my poor knowledge of the commands doesn't allow me to understand the process so I'll be very grateful for any help, surely I've forgot something form the start!

thanks!

Andreas

RE: Display UI on Waveshare 3.5 inch TFT - Alaini93 - 04-23-2021

Hi Gattonero,
you said you have an "Adafruit 3.5TFT installed" and working.
what is your new screen? the same?

I found out, a good screen that works out of the box without the need for driver, is an OSOYOO 3.5" DSI Touchscreen.
HDMI screens need script for the touchscreen to work, I never bother since I don't use touch screen on this small display.
SPI screens are a pain to install. I wonder how you made your first screen worked, because drivers, usually, mess up Moode OS.
(I tried all 3 of them)

RE: Display UI on Waveshare 3.5 inch TFT - gattonero - 04-24-2021

Thank you for our reply.

I'll rephrase it: Moode 7.10 release working ok on its own. A week after I've added the Adafruit 3.5" screen, the MPD and GUI via web all works fine, but the screen has never done anything more than a blank white.

I'll try now with a blank Raspbian install, good thing to have many unused SD cards Big Grin

RE: Display UI on Waveshare 3.5 inch TFT - DocSavage - 10-01-2021

Waveshare display* (XPT2046) tested with Moode 7.40:

* my display is in landscape mode / upside down so technically it is rotated by 270 degrees. Please edit your configs accordingly.

Install driver / necessary packages:

Code:
git clone https://github.com/waveshare/LCD-show.git

sudo cp ./LCD-show/waveshare35a-overlay.dtb /boot/overlays/waveshare35a.dtbo

sudo cp ./LCD-show/waveshare35a-overlay.dtb /boot/overlays/

sudo dpkg -i -B ./LCD-show/xinput-calibrator_0.7.5-1_armhf.deb

sudo apt install xinput

sudo mkdir -p /etc/X11/xorg.conf.d

Edit /boot/cmdline.txt:

Code:
net.ifnames=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo

Edit /boot/config.txt

Code:
disable_splash=1

disable_overscan=1

hdmi_blanking=1

hdmi_force_edid_audio=1

hdmi_force_hotplug=1

dtparam=i2c_arm=on

dtparam=i2s=on

dtparam=audio=on

#dtoverlay=disable-wifi

#dtoverlay=disable-bt

dtparam=spi=on

dtoverlay=waveshare35a,rotate=270

max_usb_current=1

config_hdmi_boost=7

hdmi_drive=1

hdmi_ignore_edid=0xa5000080

hdmi_group=2

hdmi_mode=1

hdmi_mode=87

hdmi_cvt 480 320 60 6 0 0 0

display_rotate=1

framebuffer_width=480

framebuffer_height=320

framebuffer_aspect=-1

[pi4]

max_framebuffers=2

Edit /etc/X11/xorg.conf.d/99-fbdev.conf:

Code:
Section "Device"

        Identifier      "Allwinner A10/A13 FBDEV"

        Driver          "fbdev"

        Option          "fbdev" "/dev/fb1"

        Option          "SwapbuffersWait" "true"

EndSection

In my case the touch x/y axes had to be swapped and the pointer offset had to be adjusted slightly.
Unfortunately, the usual xorg calibration configs didn't work.

So (in your home dir) edit ~/.xinitrc

Code:
# Turn off display power management

xset -dpms

# Screensaver timeout in secs or 'off' for no timeout

xset s 60

# Capture screen size

#SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $2","$3 }')"

SCREENSIZE="480,320"

# see https://wiki.archlinux.org/title/Calibrating_Touchscreen

DISPLAY=:0 xinput set-prop "ADS7846 Touchscreen" "Coordinate Transformation Matrix" 0 1.09 -0.065  -1.09 0 1.04  0 0 1

# Launch chromium browser

# --disk-cache-dir=/dev/null

chromium-browser --app=http://localhost/ --window-size=$SCREENSIZE --window-position=0,0 --no-first-run --enable-features=OverlayScrollbar --disable-infobars --disable-session-crashed-bubble

Now your screen should work after enabling local display in moode:
[configure]->[System]->[Local UI display]