I have a waveshare 3.5 inch touch LCD display and I m trying to get it working with the latest version of Raspbian A.K.A Raspbian Jessie. I followed futurice.com 's tutorial on getting it to work (tutorial is titled I'd like some LCD on my pi) and it worked on Raspbian Wheezy just fine. All I get now is a blank white screen. All help is greatly appreciated! (I must use the official Raspbian Jessie image without NOOBS from the Raspberry pi website.) I have a Raspberry Pi 2 Mobel B +.
From the product page:
Why the LCD doesn't work with my Raspbian? To use the LCD with the
Raspberry Pi official image, driver should be installed first. Please
refer to the user manual. However, for the first testing, you may want
to use our provided image directly. Why the LCD still doesn't work
with the Waveshare provided image? Make sure the hardware connection
is correct and connects fine. Make sure the image in TF card is burnt
correctly. The PWR will keep on and the ACT will keep blinking when
the Raspberry Pi starts up successfully, in case both of the two LEDs
keep on, it is possible that the image was burnt incorrectly OR the TF
card was in bad contact. Which power supply should I use? It is
strongly recommended to use a stand-alone 5V/2A power adapter, because
the PC's USB port might doesn't have enough power to support the Pi
and LCD. For more info, please check the wiki page
You can find more info on their wiki.
It sounds like you either need to use their Raspian image, or install the driver for this display on your existing Raspian install:
wget http://www.waveshare.net/w/upload/7/73/LCD-show.tar.gz
tar xvf LCD-show.tar.gz
cd LCD-show/
sudo ./LCD35-show
Related
My Node.js project utilizes CEC control and VLC where the app turns on the TV and chooses the HDMI port that the VLC video stream will be viewed on at a scheduled time.
Everything worked on Buster except that too many indeterminate crashes with segmentation faults occur with cec-client.
Since I am nearing a 'production' release, I thought it best to upgrade the OS to Bullseye and find a cec-client replacement. I found cec-ctl and made it asynchronous - ctl-cec works perfectly, everytime, no crashes. BUT, now VLC does not render anything, not even a black screen. Doing a 'ps' command during a time that a video should be playing, I can see that VLC is running.
What I tried: It turns out that changing the /boot/config.txt dtoverlay=vc4-fkms-v3d (Buster) to dtoverlay=vc4-kms-v3d (Bullseye) causes the problem. The Buster version of dtoverlay seems to be required for VLC to run, and The Bullseye version of dtoverlay is required for a /dev/cec0 to be created and used by ctl-cec.
All I can see from my inexperienced view is mutual exclusivity, but this doesn't feel like this is the final answer. Using both dtoverlay version (Buster/Bullseye) will brick the pi (speaking from the very recent experience of one not well-versed in dtoverlays).
I also tried: I Googled this problem to the extent of my search skills and have not been able to resolve this problem.
Any help is greatly appreciated!
Raspbian OS: Bullseye (Desktop)
Raspberry Pi 3 B+
App: Node.js based with ability to make config changes and set schedules via an external browser within the LAN.
The solution for my project, after days of Googling, turned out to be TOO simple (found here: https://www.reddit.com/r/archlinuxarm/comments/lg4z5u/no_hdmi_audio_via_alsa_on_raspberry_pi_400/):
sudo apt install pulseaudio
along with:
dtoverlay=vc4-kms-v3d
VLC and cec-ctl now work together perfectly on Raspberry Pi 3B+/Bullseye
I installed "onboard" as a virtual keyboard on the system. It looked much nicer and more useful than matchbox. I went into the settings and chose the auto open option when I edit the post. after that i restarted my raspberry pi. As it didn't come on automatically, I couldn't run it from the terminal or the menu normally. The error I get when I try to run it from terminal
Hej blackmamba,
I had the same issue with the on screen keyboard florence. After I installed at-spi2-core, it didn't crash anymore, though i could not get it to open automatically.
So I tried installing onboard and everything worked quiet well. Might be a hint..
regards, jarvis
Raspberry Pi B+
5.10.63 Kernel
Debian Buster 10
Waveshare 10.1" HDMI LCD Touch Display
I am trying to set up Supercollider on my Raspberry Pi 3 A+ on Raspbian Lite using this guide. Jackd2 and Supercollider both compile fine, and there are no errors when I try to run Supercollider or the jack_simple_client test. However, regardless of different sample rates, buffer sizes, number of periods etc. used in booting the jack server the audio always comes out heavily distorted, with loud high pitched squealing and low popping noises.
Using the speaker-test command from ALSA creates a clean, non distorted test tone. Previously trying pyo as a DSP module would also suffer from the same issue if I used Jack, but would work fine otherwise. This leads me to believe that there is some issue in the communication between jack and ALSA. Power supply is likely not the problem as well. My installed jack version is 1.9.17 and ALSA is k5.4.83-v7+. I am new to working with Linux audio/Jack, so any help is much appreciated!
Things I would try:
Try jack2
Get a fresh SD card, and use the version of jack that comes with raspbian and then either try building again or just trying to also get SuperCollider via apt.
sudo apt-get install cmake libasound2-dev libsamplerate0-dev libsndfile1-dev libavahi-client-dev libicu-dev libreadline-dev libfftw3-dev libxt-dev libcwiid1 libcwiid-dev subversion libqt4-dev libqtwebkit-dev libjack-jackd2-dev
Check how it sounds out of the HDMI port or a USB audio adaptor or a hat. The headphone jack tends to sound terrible anyway on raspberry pis, so if something else works, that's you answer.
I've been working with Alsa around 4 years ago, but remember I had the problem.
First I thought that my device was the reason, and it turned out to be that the noise was coming from wrong channel, and I had to force set alsa channels manually with cli commands and later in config files.
Try to check that alsa does not assign wrong channel when Jack is up.
I'd like to use Raspberry Pi 4 to collect data from several BLE mesh supported devices (beacons) that uses a chip like nRF52832, nRF52833 or nRF52840.
I know that Pi 4 comes with bluetooth 5.0.
My question is, can I use Pi 4 as it is without any hat, cape etc. connected to collect data from the beacons that uses those chips and communicates by using the BLE mesh technology.
Yes, you should be able to use the Raspberry Pi for mesh functionality depending on the version of BlueZ that is available there. Mesh functionality was initially added in BlueZ v5.47 (September 2017) and subsequent versions of BlueZ have had bug fixes and additions to this feature. You can find more information here:-
http://www.bluez.org/
You can check the version of BlueZ that is on your Raspberry Pi through the following command:-
bluetoothctl --version
I hope this helps.
My raspberry pi is installed with the latest raspbian image, and now I am trying to program my SenseHAT. The status is :
The firmware boots up successfully, the rainbow is displayed on the
screen and Sense HAT, and it proceeds.
The OS(up-to-date raspbian) start loading with the splash screen, but
it is stuck at somewhere when it says udisks2.service,
All the OS modules are installed,
I2C is enabled at /boot/config.txt
dt_overlay is configured at /boot/config.txt.
Anybody has faced this freezing problem before? My raspberry pi 3 and Sense HAT simply not getting along with each other.