Hot answers tagged

3

I had the exact same problem. Solutions are: Turn on the screen first. I give it 4 seconds. Slower SD cards won't have this problem, since the Pi waits longer before checking for a monitor. Add/uncomment hdmi_force_hotplug=1 in /boot/config.txt. Turn off OpenGL. sudo raspi-config --> Advanced Options --> GL Driver --> G1 Legacy. Get a HDMI screen.


2

is there a possibility to see output (f.e. std cout << ...) from my program which was started from rc.local script when i am logged into my Rpi via SSH? A process started by init (which includes stuff in rc.local) may not fare well if it outputs anything to stdout, which is why it is common practice to start them this way if you don't care about the ...


2

It turns out I was using the wrong Library. The device I have is a SH1106, not a SSD1306. When using the proper library (Like this one) It works fine.


2

Yes, perfectly possible. Obviously just make sure you have easy access to the button in your enclosure. You can do that with more or less any sort of hdmi device. For example I have a ps4 connected to my TV along with a Nintendo switch. All I have to do is turn the TV on and press the button on the switch to flick between the two.


2

Well, now the Raspberry Pi 4 model B has come out with two Micro HDMI ports, so I think that gives the best solution to the problem? If you don't want a Pi 4, it seems that buying two Pis may still be the next best option. But I would use x2x instead of Synergy to connect them, because it is free software. For additional displays, I noticed that there are ...


1

Unlikely. The Pi's GPIO peripheral supports clearing a set of GPIO in one instruction and setting a set of GPIO in one instruction. You specify the GPIO to clear/set with a 32-bit mask. E.g. to select GPIO 0-7 you would set a bit mask of 0x000000FF. The unselected GPIO are unaffected by the clear/set operation. For simplicity the following examples ...


1

Yes I think it is possible, for example you can use FIFO file: ~$ mkfifo /tmp/input.audio.fifo Write a python programm like this (warning, this script record only 60sec of audio, you can adjust this): Python code REF. To install: python -m pip install pyaudio """PyAudio example: Record a few seconds of audio and save to a WAVE file.""" import ...


1

There appear to be two possibilities. something is connected to GPIO 24 and GPIO 25 which is pulling those GPIO low. The Pi is broken. I suggest you remove everything from the expansion header and run one or both of wiringPi's pintest or (my) pigpio's gpiotest.


1

I was also getting the same error. But now it is working for me. First you install I2S microphone as shown here: https://learn.adafruit.com/adafruit-i2s-mems-microphone-breakout/raspberry-pi-wiring-and-test After that while you are installing I2S amplifier go to the detailed installation section and skip the first 2 steps and start from "Create asound.conf ...


1

According to this: https://www.raspberrypi.org/documentation/configuration/config-txt/video.md If in your cofig.txt you set: sdtv_disable_colourburst=1 then the composite output of RPi is monochrome.


1

Just in case anyone came across this and has the same issue (which I did) the solution is that the a/v cable is probably polarized incorrectly, ie swap the ground so it goes top the outside (shield) and video is to the center pin of the composite video connector


1

sudo tvservice -p will turn on HDMI output if it was disabled for some reason. Check out the other options of this command.


1

Sorry to react almost 7 years later... I believe this problem could be related and solved to overscan. Either set your TV to display every pixels without cutting the border. Or, on the Pi specify that some pixels are not visible and should not be used. And this can be done in /boot/config.txt # uncomment this if your display has a black border of unused ...


Only top voted, non community-wiki answers of a minimum length are eligible