So i searched to figure out how to get this to work and no luck that i found anything but people getting white screens. I did manage to get it work but haven’t got it to work with a desktop environment, works great for console and DietPi-Cloudshell. just follow below instructions and it should work, possibly work with other waveshare screens.
select “1 : Display Options”
select “3 : LCD Panel addon”
exit and reboot
~$ sudo apt install git
~$ sudo git clone https://github.com/waveshare/LCD-show.git
~$ cd LCD-show/
~$ sudo ./LCD35-show
wait for rebbot
~$ sudo nano /DietPi/config.txt
change “framebuffer_width=320” to “framebuffer_width=480”
change “framebuffer_height=240” to “framebuffer_height=320”
change “dtoverlay=waveshare32” to “dtoverlay=waveshare35a”
~$ sudo reboot
Thank you so much for this! After hours of trying to get this going, this worked like a charm!
Jep, many thanks for sharing, I hope me or someone finds time to implement into DietPi: https://github.com/MichaIng/DietPi/issues/2394
I still haven’t figured out how to get it to run with a desktop environment I wish someone could help but I’m at ends meet with this, no expert just messing around
The biggest thing is the dtoverlay needs to be added but I don’t know how to other than to load the driver for the screen
Thanks for this, finally managed to get something other than a white screen running…
anyone have an idea how i can get PADD to load?
I’m able to do it on ‘lite’ RPi image but on this would be ideal
it has to be possible somehow
I am trying to do the same thing and cannot believe there are no newer threads to be found.
I almost got a waveshare 3.5" B working following the steps above, but not quite.
Now there seem to be two screen buffers on top of each other - the tty1 I want (ie. login) and another showing DietPi Preboot information like the cpu governor info, and whenever I write something eg. try to log in, or run padd, the DietPi-preboot-text overwrites the screen and the stuff I want just flickers…
Answering my own questiong, killing off process “fbcp” did the trick!
This was started in /etc/rc.local from wher I can disable it from running on boot.