piscreen v2 with raspbian buster

[ronvanewijk]

Hi, my old piscreen v1 died on me and I ordered a new one which seems to be a version2.

Connecting it to my raspberryPi model 3B+ nothing happens. If I run some tests, the touchscreen seems to work but the screen stays black.

I did run the sudo vcdbg log msg:

ron@wps:~ $ sudo vcdbg log msg
[sudo] password for ron:
001378.450: brfs: File read: /mfs/sd/config.txt
001379.469: brfs: File read: 1780 bytes
001405.869: HDMI:EDID error reading EDID block 0 attempt 0
001407.131: HDMI:EDID error reading EDID block 0 attempt 1
001408.391: HDMI:EDID error reading EDID block 0 attempt 2
001409.652: HDMI:EDID error reading EDID block 0 attempt 3
001410.912: HDMI:EDID error reading EDID block 0 attempt 4
001412.173: HDMI:EDID error reading EDID block 0 attempt 5
001413.433: HDMI:EDID error reading EDID block 0 attempt 6
001414.694: HDMI:EDID error reading EDID block 0 attempt 7
001415.954: HDMI:EDID error reading EDID block 0 attempt 8
001417.215: HDMI:EDID error reading EDID block 0 attempt 9
001418.233: HDMI:EDID giving up on reading EDID block 0
001422.305: brfs: File read: /mfs/sd/config.txt
001423.230: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
001435.015: brfs: File read: 1780 bytes
001440.170: gpioman: gpioman_get_pin_num: pin WL_LPO_CLK not defined
001440.194: gpioman: gpioman_get_pin_num: pin BT_ON not defined
001440.213: gpioman: gpioman_get_pin_num: pin WL_ON not defined
001614.880: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined
001616.120: gpioman: gpioman_get_pin_num: pin LEDS_PWR_OK not defined
001616.174: *** Restart logging
001617.074: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
001618.337: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
001619.601: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
001620.864: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
001622.127: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
001623.390: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
001624.654: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
001625.917: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
001627.180: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
001628.444: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
001629.466: hdmi: HDMI:EDID giving up on reading EDID block 0
001629.796: hdmi: HDMI:EDID error reading EDID block 0 attempt 0
001631.062: hdmi: HDMI:EDID error reading EDID block 0 attempt 1
001632.328: hdmi: HDMI:EDID error reading EDID block 0 attempt 2
001633.594: hdmi: HDMI:EDID error reading EDID block 0 attempt 3
001634.860: hdmi: HDMI:EDID error reading EDID block 0 attempt 4
001636.126: hdmi: HDMI:EDID error reading EDID block 0 attempt 5
001637.393: hdmi: HDMI:EDID error reading EDID block 0 attempt 6
001638.658: hdmi: HDMI:EDID error reading EDID block 0 attempt 7
001639.924: hdmi: HDMI:EDID error reading EDID block 0 attempt 8
001641.189: hdmi: HDMI:EDID error reading EDID block 0 attempt 9
001642.213: hdmi: HDMI:EDID giving up on reading EDID block 0
001642.260: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
001642.281: HDMI0: hdmi_pixel_encoding: 162000000
001642.527: vec: vec_middleware_power_on: vec_base: 0x7e806000 rev-id 0x00002708 @ vec: 0x7e806100 @ 0x00000420 enc: 0x7e806060 @ 0x00000220 cgmsae: 0x7e80605c @ 0x00000000
001647.950: dtb_file ‘bcm2709-rpi-2-b.dtb’
001653.424: brfs: File read: /mfs/sd/bcm2709-rpi-2-b.dtb
001653.446: Loading ‘bcm2709-rpi-2-b.dtb’ to 0x100 size 0x66bb
001690.664: brfs: File read: 26299 bytes
001702.456: brfs: File read: /mfs/sd/overlays/overlay_map.dtb
001909.925: brfs: File read: 1371 bytes
001914.249: brfs: File read: /mfs/sd/config.txt
001915.373: brfs: File read: 1780 bytes
001923.310: brfs: File read: /mfs/sd/overlays/piscreen2r.dtbo
001956.212: Loaded overlay ‘piscreen2r’
001956.283: dtparam: audio=on
002153.892: brfs: File read: 2593 bytes
002157.245: brfs: File read: /mfs/sd/overlays/piscreen2r.dtbo
002191.088: Loaded overlay ‘piscreen2r’
002348.967: brfs: File read: 2593 bytes
002352.137: brfs: File read: /mfs/sd/cmdline.txt
002352.208: Read command line from file ‘cmdline.txt’:
002352.235: ‘dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=b01edc0e-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait net.ifnames=0 fbcon=map:10 fbcon=rotate:2 fbcon=font:ProFont6x11’
004447.814: gpioman: gpioman_get_pin_num: pin EMMC_ENABLE not defined
004590.619: gpioman: gpioman_get_pin_num: pin WL_ON not defined
004603.390: brfs: File read: 208 bytes
004980.938: brfs: File read: /mfs/sd/kernel7.img
004980.963: Loading ‘kernel7.img’ to 0x8000 size 0x557138
004980.995: Device tree loaded to 0x2eff9100 (size 0x6ea5)
004983.035: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
008136.250: vchiq_core: vchiq_init_state: slot_zero = 0xf7580000, is_master = 1

 

Can you please help me to figure out what is wrong?

Thanks,

Ron

[Mark Williams]

In /boot/config.txt , can you confirm you have deleted the old config for PiScreenV1 and only have the new config.
dtoverlay=piscreen2r

Did you use evtestto confirm if the touchscreen is working?
if not, you can install it with sudo apt-get install evtest

Please confirm if the screen is “white” or “black”

What about when you enable the console on the PiScreen… do you see this?

https://ozzmaker.com/enable-console-on-piscreen/

Mark --OzzMaker.com --

[ronvanewijk]

Hi Mark, thanks for your quick reply.

Yes, I replaced the dtoverlay with the piscreen2r value.

With “sudo evtest /dev/input/event0 ” I confirmed the touchscreen is working.

The screen stays black, no light visable.

Yes, my default is to enable the console on the display. Also not working.

The point is, I ordered two displays and both (on different Pi’s) are not working. Can’t imagine two faulty displays, so it mus be some config issue. With “sudo vcdbg log msg” I do see a lot pins not defined, also a lot of hdmi messages. Does that give you a clue?

Thanks,

Ron

 

 

[ronvanewijk]

Another clue might be that I am using the Buster version of Raspbian.

[Mark Williams]

have you changed fb0 to fb1in this file?
sudo nano /usr/share/X11/xorg.conf.d/99-fbturbo.conf

Mark --OzzMaker.com --

[ronvanewijk]

Hi Mark, no I have not installed any X utils. Should I do that for the piscreen?

Regards,

Ron

[Mark Williams]

Hi Ron.
Are you using Raspbian buster, which includes X windows?
Or Raspbian buster lite, which does not include X windows?

The file in my previous post is there by default when using the version of Raspbian which includes X windows.

I just did a test.
1. I downloaded the latest Raspbian from raspberrypi.org. Unziped file is 2020-05-27-raspios-buster-full-armhf.img
2. booted and added PiScreen config to /boot/config.txt
3. Reboot and PiScreen was still blank
4. Modified /usr/share/X11/xorg.conf.d/99-fbturbo.conf and rebooted.
5. PiScreen now shows Raspbian Desktop

Mark --OzzMaker.com --

[ronvanewijk]

Mark, thanks for testing this.

I use buster lite (no desktop, only ssh access). So maybe I should install X en use the proper config?

 

Regards,

Ron

[Mark Williams]

have you edited this file
sudo nano /boot/cmdline.txt
and added this to the end
fbcon=map:10 fbcon=rotate:2 fbcon=font:ProFont6x11

you can also do a test by showing an image

sudo apt-get install fbi
wget https://ozzmaker.com/piscreen/image-test.gif
sudo fbi -noverbose -T 1 -a -d /dev/fb1 image-test.gif

Mark --OzzMaker.com --

[ronvanewijk]

Hi Mark,

 

cmdline.txt is like you described. And the fbi shows no picture, only on the command line the used fonts.

Should I install X?

Thanks,

Ron

[ronvanewijk]

I have changed the content of /usr/share/X11/xorg.conf.d/99-fbturbo.conf to:

Section “Device”
Identifier “PiSCreen”
Driver “fbturbo”
Option “fbdev” “/dev/fb1”
EndSection

Still no display.

Regards,

Ron

[ronvanewijk]

Hi Mark,

 

do you have any suggestions for me to try out?

I am stuck with two dead displays, while the v1 worked well.

Please help,

thanks,

Ron

[Mark Williams]

Sorry for the delay with replying.

We have had faulty displays in the past… but never two at the same time.
Can you please test with a clean image.

This is what i just did to test.

1. downloaded 2020-05-27-raspios-buster-lite-armhf.img and burn to SDCARD
2. edited /boot/config.txt
   added dtoverlay=piscreen2r at the bottom
3. edit /boot/cmdline.txt
   added fbcon=map:10 fbcon=rotate:2 fbcon=font:ProFont6x11 to the end of the only line there
4. rebooted

 

After step 4 above, i was able to see the console on the PiScreen.

Mark --OzzMaker.com --

[ronvanewijk]

Hi Mark, thanks for your suggestion.

I used a fresh image on a fresh sd card (latest version is 2020-08-20-raspios-buster-armhf-lite.img).

I updated the two files:

[all]
#dtoverlay=vc4-fkms-v3d
dtoverlay=piscreen2r
pi@raspberrypi:~ $ cat /boot/cmdline.txt
console=serial0,115200 console=tty1 root=PARTUUID=33262bfd-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait fbcon=map:10 fbcon=rotate:2 fbcon=font:ProFont6x11
pi@raspberrypi:~ $

Both displays did not show the console.

There is no small switch on these v2 is there, like on the v1 display? Could I have done anything wrong?

It is just a matter of installing it on the gpio pins and that is all there is to it isn’t it?

So, could it really be the case I received two faulty displays (I find that hard to believe).

Regards,

Ron

 

[Mark Williams]

Hi Ron

Please send an email to sales @ ozzmaker.com

We will need to replace these

Mark --OzzMaker.com --

[Author]

Posts