3 images are displayed at the same time both land scape and portraite. When shut down, Power removed and then turned back on images are still present. Resolution cannot be changed. Freq cannot be changed.
Can you provide the SKU or product link of the product?
This has already been done. No response.
Hi @dpalyu
Please copy the following code into the configuration file config.test of Raspberry Pi 4.
More info please refer to the Instructions for use.
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=82
config_hdmi_boost=4
dtparam=spi=off
dtparam=audio=on
enable_uart=1
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
hdmi_pixel_freq_limit=400000000
hdmi_group=2
hdmi_mode=87
hdmi_force_hotplug=1
config_hdmi_boost=4
disable_overscan=1
hdmi_ignore_edid=0xa5000080
hdmi_timings=720 0 100 24 52 1280 0 10 4 4 0 0 0 60 0 70000000 0
max_framebuffer_width=1280
max_framebuffer_height=1280
framebuffer_width=1280
framebuffer_height=720
Hi @dpalyu !
I messed around a lot with my new 5 inch display SKU 104990442. Initially I had the same problems - duplicate images, ghosting and so on. Tried different Pis, Pi A, Pi 2 B and Pi 3 B+ — all had same problems. So, after messing around for almost 1 full day - I figured out that it works with previous Raspbian Stretch, but not the latest Buster image. So I had to downgrade my SD card to Stretch and things started to work - like magic. No, it was not the fault of the screen - the screen worked well with Windows 10 or Linux PC, although a ghost image of the Raspbian Buster was still visible and flickering. When the Raspbian Buster wrote some (I guess wrong) memory place of the display, I had to unpower the display and wait until next day for the memory to clear to have a flicker-free display. You probably can also just leave the screen on and maybe the flicker goes away after some time.
The Raspbian Stretch version I used was from https://downloads.raspberrypi.org/raspbian/images/raspbian-2018-03-14/
So, in short, to get it working with the Instructions_for_use.pdf, find a way to downgrade to Stretch.
And, by the way, the force_trubo is clearly a typo in this pdf (only force_turbo is accepted in config.txt), I left it in, so this means it is not a necessary parameter.
I don’t have a Pi 4, so cannot try that unfortunately.
I hope the Seeed guys can confirm that it works (or doesn’t work) with Buster also. It was clearly the problem for me.
My config.txt from a Raspbian Stretch:
dtparam=i2c_arm=on
#typo here, whatever:
force_trubo=1
#going on:
gpu_freq=300
core_freq=400
hdmi_pixel_freq_limit=400000000
hdmi_drive=2
hdmi_mode=87
disable_overscan=1
# 5 inch
# removed a space from front of 720
hdmi_timings=720 0 100 33 100 1280 0 20 2 30 0 0 0 60 0 79000000 0
max_framebuffer_width=1280
max_framebuffer_height=1280
display_hdmi_rotate=1
framebuffer_width=1280
framebuffer_height=720
The exact same config.txt does not work for me in Buster.