Problem PicorePlayer with ELECROW Touch Display 7" 1024x600 with Jivelite

[kjansik]

The hdmi config would not have much to do with the touch configuration, as the touch is USB. The only thing that matters is that the touch library can figure out the display resolution

I do believe USB should be OK. RPI4 has USB 3.0 and USB 2, I tried both. My suspicion is that touch is receiving wrong info about display. In the case mouse cursor is on, after next touch cursor is moving on the right bottom (lower) corner of screen, after first touch cursor regularly goes out (overscan?) of screen. Ts_calibrate shows following cordinates:

sudo TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/event0 /usr/loc
al/bin/ts_calibrate
xres = 800, yres = 480
Took 1 samples...
Top left : X = 1024 Y = 600
Took 1 samples...
Top right : X = 1024 Y = 600
Took 1 samples...
Bot right : X = 1024 Y = 600
Took 1 samples...
Bot left : X = 1024 Y = 600
Took 1 samples...
Center : X = 1024 Y = 600
ts_calibrate: determinant is too small -- 0.000000
Calibration failed.
​​

Coordinates X,Y remains unchanged for every resolution and skin set. xres, yres values are set by default Pointercal file, change doesn't influence calibration result.

Many user with HDMI screen 1024x600 claimed that those screens are working only with 800x480 resolution properly. I got Waveshare HDMI C 1024x600 and it worked without any problem with 1024x600. VU meters got problem, it is discussed and solved in forum.

Why touch does not understand the screen is out of my abilities, I do not have any clue how to proceed, where to search answers.

[paul-]

The hdmi config would not have much to do with the touch configuration, as the touch is USB. The only thing that matters is that the touch library can figure out the display resolution

[kjansik]

I don’t argue the quality difference, but then you have to deal with poor support from the hardware vendor. Have you ran some other test software to ensure you don’t have. Faulty screen?

Screen is described on site http://www.lcdwiki.com/7inch_HDMI_Display-H. Even chinese seller provides solid support.
Device is working absolutely flawlessly with Raspi Bullseye. No calibration needed, just basic settings. Windows 11 OK!!
I tried with Raspi 3B+ and Raspi 4B 2Gb. I tried with PicorePlayer 6.0, 6.1, 8.0, 8.2 (32bit and 64bit version). I installed TinyCore with Xorg and GUI, same problem: Every touch resulted on same place. I have suspicion that hdmi_timing setting plays some role: on TinyCore sometimes seems touch ended on different place.
So far: problem is related to TinyCore/PiCoreplayer environment.
Screen itself seems to be very good quality: nice colors, good viewing angles, clean connection for external source and Raspi, backlight regulation. pricing reasonable, delivered in two weeks...
I am not giving up...

[paul-]

I don’t argue the quality difference, but then you have to deal with poor support from the hardware vendor. Have you ran some other test software to ensure you don’t have. Faulty screen?

[kjansik]

[

The official raspberry pi display (DSI display) works seamlessly with picoreplayer and doesn't require any editing of files. It is certainly an easier solution than the HDMI screens.

Official raspberry pi display is poor quality - upside down, viewing angles, colors etc. Waveshare LCD is far better, installation easy, but case is ugly and display expensive. I am struggling with rare problem (every touch resulted on the same place), several people experienced it, but no solution is published until now.

[agburnsky]

[

Additional question: DSI LCD? would it be safe choice for pCP player?

The official raspberry pi display (DSI display) works seamlessly with picoreplayer and doesn't require any editing of files. It is certainly an easier solution than the HDMI screens.

[kjansik]

Hi Paul-,

may be you can help me concerning problems with my touch screen: you are the opinion am experiencing driver problem: I looked at the driver provided by http://www.lcdwiki.com/7inch_HDMI_Display-H. Relevant part of driver provided shows as follow:

 [TABLE]
  [TR]
  [TD]source ./system_config.sh[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "hdmi_force_hotplug=1" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "dtparam=i2c_arm=on" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "dtparam=spi=on" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "enable_uart=1" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "display_rotate=0" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "max_usb_current=1" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "config_hdmi_boost=7" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "hdmi_group=2" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "hdmi_mode=87" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "hdmi_drive=1" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo echo "hdmi_cvt 1024 600 60 6 0 0 0" >> ./boot/config.txt.bak[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]sudo cp -rf ./boot/config.txt.bak /boot/config.txt[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]#sudo cp -rf ./boot/config-7C-1024x600.txt /boot/config.txt[/TD]
  [/TR]
  [TR]
  [TD] [/TD]
  [TD]#if test "$root_dev" = "/dev/mmcblk0p7";then[/TD]
  [/TR]
  [/TABLE]
 ​

I modified pCP config.txt according the settings I found in this code - no success. I looked at https://github.com/libts/tslib once more and seems to be clear, problem is not the calibration.
I run ts_calibrate with ts_test and received following (example touched few points on screen):

[email protected]:~$ sudo TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/event0 /usr/loc
al/bin/ts_test
1675955024.758178:   1010    584    255
1675955024.865101:   1010    584      0
1675955028.297668:   1010    584    255
1675955028.404595:   1010    584      0
1675955029.993832:   1010    584    255
1675955030.090831:   1010    584      0
1675955031.871100:   1010    584    255
1675955031.989097:   1010    584      0
1675955033.853371:   1010    584    255
1675955033.950372:   1010    584      0
​

I tried ts_test_mt and didn't receive any answer on console, crosshair disappeared after first touch and screen was irresponsive. Message on screen was : 1 touch contacts supported (driver).

I will appreciate any help, hint , any idea.....
Many thanks in advance

[kjansik]

Additional question: DSI LCD? would it be safe choice for pCP player?

[kjansik]

Can you provide any advice how to get and install driver on tinyCore? I tried register on tinyCore forum, there are 5 (!) different tests whether you are human, I didn't manage last test due to sliders, which I cannot move (on different browsers). This LCD display seems to be very good - for my players I tried different LCDs, official 7 inch, which is poor, Waveshare 7 inch C which is ugly and now I stuck without silver line.

[Greg Erskine]

Those install scripts are for Raspberry Pi OS not piCore.

[kjansik]

I am afraid you are right. I read the git you mentioned already. I found driver on the site http://www.lcdwiki.com/10.1inch_HDMI_Display-H, which is exactly the same device. Due to the fact, I am very old noob (74y), I tried but probably did not manage install the driver properly. Instruction are:

sudo rm -rf LCD-show

git clone https://github.com/goodtft/LCD-show.git
chmod -R 755 LCD-show
cd LCD-show/

and install just :
sudo ./LCD7H-show
I did everything on my pCP, but without any effect. I tried display with with Bullseye image, no problem at all, flawlessly! Those LCD7H-show file is just simple script, i do not understand how it should change something in Kernel.It is my 4th player I built and now I am on dead end.
If you can provide any hint, i would be grateful.

[paul-]

It appears you have a screen or a driver problem. This has nothing to do with ts_calibrate not being able to calibrate. I would run ts_test to see if you get different values anywhere on your screen. You can read about the TS lib here. https://github.com/libts/tslib

[kjansik]

Hi Peter,
I am struggling since10 days with exactly same device you have successfully installed:

[email protected]:/mnt/mmcblk0p1$ cat /proc/bus/input/devices
I: Bus=0003 Vendor=0484 Product=5750 Version=0101
N: Name="QDtech MPI7003 Touchscreen"
P: Phys=usb-0000:01:00.0-1.2/input0
S: Sysfs=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:0484:5750.0001/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: PROP=0
B: EV=1b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=100 3
B: MSC=10



I exactly followed your instruction, unfortunately i am stuck from first day on following problem: any touch results on same place (coordinates) on the display - example: TS-Calibrate fails:

sudo TSLIB_FBDEVICE=/dev/fb0 TSLIB_TSDEVICE=/dev/input/event0 /usr/loc
al/bin/ts_calibrate
xres = 800, yres = 480
Took 1 samples...
Top left : X = 1024 Y = 600
Took 1 samples...
Top right : X = 1024 Y = 600
Took 1 samples...
Bot right : X = 1024 Y = 600
Took 1 samples...
Bot left : X = 1024 Y = 600
Took 1 samples...
Center : X = 1024 Y = 600
ts_calibrate: determinant is too small -- 0.000000
Calibration failed.

Please, provide provide me your Pointercal file from your device, I would try to use it in RO mode to force my device from dead point. I spent hours on Google, there are several identical cases, but no solution, except one case who did it with false Pointercal file. Unfortunately, i am not able to find it more .. In case you would send me PM, i am speaking German.
Many thanks in advance
Kveto Jansík

[peddanet]

Interesting you have hdmi and a spi screen configured. Why is the piscreen entry there if your screen is hdmi?

I owed you a good answer to your question!!
Meanwhile I changed the config and I updated piCorePlayer to v8.2.0 (so then config also changes besides the custom made changes!). I refer here to my custom made changes regarding hdmi and spi:

I use HDMI settings:

SPI settings commented out/delete it:

#dtoverlay=piscreen,speed=24000000,rotate=90

HDMI Settings:

max_framebuffer_height=600
max_framebuffer_width=1024
max_usb_current=1
config_hdmi_boost=10
hdmi_group=2
hdmi_mode=1
hdmi_mode=88
hdmi_drive=1

So now I got back to your comment: Sorry to confuse you and me. But I had 4 different devices, and somehow I messed the information here in this thread unfortunately. So this 7" device is directly connected via HDMI and USB (for touch) into the Pi 3b, so no specific settings via SPI!

I will correct my settings above in the starting of the thread! I will also open a new thread for my 5" device, which is connected differently (via DSI - Display Serial Interface). i did not find a specification for DSI, as it is closed source, but as it is the only connection, it is clear that it connects both Touch and Display (maybe only from Pi3 above).

[peddanet]

Update PiCorePlayer to 8.2.0 led to changes in configuration

Update from 8.1.0 to 8.2.0 went flawlessly via the web GUI (Main Page -> pcpUpdates):

• Minor Update Button
• Full Update Button (inkl. some dialogs and 2x reboot (sometimes only 1 time reboot (other devices of mine))

After that doing on my four devices, everything went fine, besides my Elecrow 7" radio (this one!), the touch was upside-down. Recalibrating with ts_calibrate did not solve the issue. So I worked on the options and compared them to my former made changes (see above in the thread).


Options changed slightly in config.txt (m1/c1/vi config.txt):
After updating to picoreplayer 8.2.0 option display_rotate=2 was proven to be obsolete. lcd_rotate=0 did the swap of the touch matrix (this issue arose after update from v8.1.0 and did funnily not affect the graphics itself funnily (because that is what you first assume reading this option, for touch you do the ts_calibrate, my assumption. However the calibration was alright, and issue of "upside down" touch after upate wasn't solved!
However I test lcd_rotate=0 (so uncomment it in my proposition down below!) and I did not check if display_rotate does the same job (uncommented below, but now deleted) :

• delete/comment display_rotate (was after deleted automatically after update)
• comment in/change lcd_rotate=0 (was set automatically to 2 after update)