3

I am trying to set display of raspberry pi model B+ to 5 inch touch screen. I have mounted SD card and changed config.txt file in /boot/config/firmware folder and added following entries.

hdmi_safe=1
max_usb_current=1
hdmi_group=2
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0
hdmi_drive=1
boot_delay=1 

When I boot the raspberry pi, a rainbow splash screen appears followed by black screen and it remain stuck over there. I have followed this tutorial by waveshare for the reference. Where am I going wrong? I need some assistance.

I have followed elecrow's tutorial and updated the 'config.txt' but still no luck:

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan

#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
hdmi_force_hotplug=1
dtparam=i2c_arm=on
dtparam=spi=on
enable_uart=1
display_rotate=0
max_usb_current=1
config_hdmi_boost=7
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_drive=1
hdmi_cvt 800 480 60 6 0 0 0
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


# --- added by elecrow-pitft-setup  ---
hdmi_force_hotplug=1
max_usb_current=1
hdmi_drive=1
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0
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_rotate=0
# --- end elecrow-pitft-setup  --
| improve this question | | | | |
  • Please tag your question with the Raspberry Pi model. If it's Pi 3B like the question title says, use pi-3b or pi-3b+, if you got it right in the body, use pi-b+. – Dmitry Grigoryev Dec 9 '19 at 11:50
  • 1
    Remove hdmi_safe=1 – CoderMike Dec 12 '19 at 10:18
1

I was facing the same problem with the Raspberry pi 4 but without the touch screen. When I studied and searched I found that OS was corrupted or was not compatible to run with the Raspberry pi due to the wrong alteration.

I think you are also facing a similar issue.

Please follow this link: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=258526

Hope this will give you your answer. And if not you can ask there.

| improve this answer | | | | |
1

I suggest you get a USB to UART dongle and set up your RPi to produce boot messages to serial port. This usually involves editing cmdline.txt to make sure there is a serial console (console=serial0,115200) and there's no quiet parameter. You should be able to collect boot messages on a laptop using Putty or a similar terminal program. Get this working without the screen in the first place.

Then get your screen connected together with the UART. If you can solder, just solder the TX and RX lines on the bottom of the GPIO connector. If not, get a GPIO expansion board which lets you connect the screen and still have access to UART pins. Then check the boot log, and hopefully you'll see where it gets stuck.

And by the way, you didn't follow a Waveshare tutorial. You followed a video which seems to be posted by a youtuber which doesn't seem to be official. Here's the official Waveshare wiki, which I would use instead if I were you.

PS. If your Pi won't boot without the LCD as well, please read this sticky covering most early boot problems.

| improve this answer | | | | |
  • I did followed Waveshare's guidelines. One more thing I cannot see content of config.txt in /etc/config directory. However, it is linked with /etc/config/firmware/config.txt ... is this fine? – user1584253 Dec 10 '19 at 5:16
  • @user1584253 You're editing the wrong file. You need /boot/config.txt. – Dmitry Grigoryev Dec 13 '19 at 8:35
  • this file has no content when I try to edit it, and in its properties I can see it is linked with the config.txt file in /et/boot/firmware directory – user1584253 Dec 13 '19 at 8:59
  • When I plug in SD card in my laptop I see two drives, one is 'system-boot' and other is 'writable'. In writable drive I have config.txt in /boot directory which is linked with /boot/firmware/config.txt file. However, in 'system-boot' I can see config.txt file. So I am editing this file in 'system-boot' – user1584253 Dec 17 '19 at 18:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.