LCD-show VS Pinout.xyz

I looked into the GitHub project and followed their steps as well just in case the other one was outdated, but ran into the same issue. And googling isn’t very help since anything along the lines “raspberry pi 5 lcd screen issue/driver” just returns a bunch of results for 5” screens.

That repo is full of pretty janky scripts, but I'd look at their system_restore script: https://github.com/goodtft/LCD-show/blob/master/system_restore.sh

The code changes /boot/config.txt to set the monitor driver and screen size (lines 22-32 in the code).

sudo rm -rf LCD-show git clone https://github.com/goodtft/LCD-show.git chmod -R 755 LCD-show cd LCD-show/ sudo ./LCD35-show

The driver for the display apparently breaks libcamera;

How can I get the WaveShare 3.5 inch TFT display to work on my raspy 4B that is running Manjaro. It works fine using the https://github.com/goodtft/LCD-show drivers in Raspbian which is based on Debian, but it doesn't work on Arch-based Manjaro. I tried this attempt at a port but it didn't work for me: https://github.com/Bennett-Wendorf/LCD-show/tree/arch-compatibility-part-2 Any hope on manjaro?

The supplied information here references https://github.com/goodtft/LCD-show.git as the repository to use for the display , this particular one uses "LDC28-show" but the repository works with all sorts of generic displays. after following the instructions and rebooting my screen either remind white or grey.

The library is the next: https://github.com/goodtft/LCD-show/blob/master/LCD5-show , at 18 line the I2C is enable, at line 21 the display is rotate, but I don´t see how is send the data through the I2C. That line save the data in file "boot/config.txt", but I don´t found how is used to send data over the I2C port.

Okay. I'll give that a shot in lieu of https://github.com/goodtft/LCD-show.git for #3, but thanks for your help on 1, 2, 4.

git clone https://github.com/goodtft/LCD-show.git

Obligatory shameless plug of https://pinout.xyz where I’ve been maintaining an interactive Raspberry Pi SBC pinout for some years, and the newer https://pico.pinout.xyz where I’ve tried to do the same for the Raspberry Pi Pico board. The latter also became a command-line pinout via the Python package “picopins”

I feel- and of course I’m biased- that if anything is worth bringing to the table for device pinouts it’s interactivity and accessibility. The latter, in particular, is lost in static images. I really leaned into this with the Pico Pinout, including everything from visual accessibility accommodations (avoiding low contrast text background colours), to markup for screen readers to the ability to turn off labels and reduce noise. I’m still unsure if I actually achieved my goal, but it’s been fun.

There is a great resource to be found at pinout.xyz that details a lot of boards and the pins they actually use.

All the LEDs have their negative pins together and go through two 1k resistors in series on their way to ground (any gpio ground pin). Then a short piece of jumper wire goes from the positive lead of each LED to it's GPIO pin number. Don't use the pin order number, use the GPIO number.

I wanted to create an accessible alternative to the official Pico pinout image, offering more complete pin details, light/dark modes, screen-readable text, and at least some capacity to focus on the peripherals you’re interested in. It’s a sister site to the now ancient Raspberry Pi pinout (https://pinout.xyz/) which started out life hosted on a Raspberry Pi.

GPIO PIN numbers - its a real pain with both board and BCM numbers (see pinout.xyz for details) without having to translate what the libraries use by default!

The pins are at top right corner here: https://pinout.xyz/ and you just connect TX to RX, RX to TX and GND to GND. On the software side you can use picocom on the builtin serial device. Not sure which though, seems to depend on the software and exact revision of your RPi.

You can see all the pins on the pin documented at https://pinout.xyz

Use pinout.xyz to see what pins are used for the SPI interface on your Pi.

You have mixed up the PIN numbers - the Pi has two sets on numbers (board and BCM) - see here for details