Discussion:
[SlimDevices: Unix] picoreplayer 3.11 +waveshare 3.5 TFT + jivelite + Raspberry Pi 2B+
streampunk
2018-01-23 18:38:06 UTC
Permalink
Thanks so much for the tutorial. This is the kind of stuff I'd say that
I wouldn't have achieved by myself in a 1000 years...

An addition which might be helpful to all that use USB devices with the
Raspi (there are several posts pointing out that plugging in a mouse or
a keyboard during the setup process causes some confusion with the event
numbers).

The original do_rebootstuff.sh had some lines that dynamically detect
the event number and that are commented out in the tutorial which
hardcodes "event0" instead of "$eventno":


Code:
--------------------

if [ "$JIVELITE" = "yes" ]; then
echo -n "${BLUE}Starting Jivelite... ${NORMAL}"
# eventno=$( cat /proc/bus/input/devices | awk '/*FT5406 memory based driver*/{for(a=0;a>=0;a++){getline;{if(/mouse/==1){ print $NF;exit 0;}}}}')
# if [ x"" != x"$eventno" ];then
# export JIVE_NOCURSOR=1
export TSLIB_TSDEVICE=/dev/input/*event0*
export SDL_MOUSEDRV=TSLIB
export SDL_MOUSEDEV=$TSLIB_TSDEVICE
# fi

--------------------


This is because the search pattern "FT5406" only applies to certain
hardware componenents. But if you know the "name" of your 3.5
touchscreen, you can easily adapt the dynamic event number logic.
You get the name by typing

Code:
--------------------

cat /proc/bus/input/devices

--------------------
at the prompt (via Putty). In my case for example (a 20 Euro display
from Amazon) it reads (no USB device plugged in):

Code:
--------------------

***@piCorePlayer:~$ cat /proc/bus/input/devices
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="*ADS7846 Touchscreen*"
P: Phys=spi0.1/input0
S: Sysfs=/devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: PROP=0
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=1000003

--------------------


So if I put the name "ADS7846 Touchscreen" into do_rebootstuff.sh,
everything works perfectly, no matter what USB devices are plugged in.
This is the code (which also includes ralphy's patch from post #64:



Code:
--------------------

if [ "$JIVELITE" = "yes" ]; then
echo -n "${BLUE}Starting Jivelite... ${NORMAL}"
eventno=$( cat /proc/bus/input/devices | awk '/*ADS7846 Touchscreen*/{for(a=0;a>=0;a++){getline;{if(/mouse/==1){ print $NF;exit 0;}}}}')
if [ x"" != x"$eventno" ];then
export JIVE_NOCURSOR=1
export TSLIB_TSDEVICE=/dev/input/*$eventno*
export SDL_MOUSEDRV=TSLIB
export SDL_MOUSEDEV=$TSLIB_TSDEVICE
fi
export HOME=/home/tc
# if [ -x /opt/jivelite/bin/jivelite.sh ]; then
if [ -x /mnt/mmcblk0p2/tce/jivelite.sh ]; then
echo "${GREEN}Done.${NORMAL}"
sudo -E -b /mnt/mmcblk0p2/tce/jivelite.sh >/dev/null 2>&1
elif [ -x /opt/jivelite/bin/jivelite.sh ]; then
echo "${GREEN}Done.${NORMAL}"
sudo -E -b /opt/jivelite/bin/jivelite.sh >/dev/null 2>&1
else
echo "${RED}There is a problem with the Jivelite installation. Please remove and reinstall jivelite.${NORMAL}"
fi
fi

--------------------

Best regards
Martin



PCP (always latest version) on RasPi 3 with PhatDac (player & server)
PCP on several RasPis 2 +3
2 Airplay speakers (Sony SA-NS510) integrated via Airplay Bridge Plugin
------------------------------------------------------------------------
streampunk's Profile: http://forums.slimdevices.com/member.php?userid=66210
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
streampunk
2018-01-26 12:06:20 UTC
Permalink
Hi,
for all that are using the touchscreen display in sel constructed mobile
devices (i.e. running on battery power), it would be great to have an
option to put the screen and its backlight into standby after a certain
time.
It seems that this is not really trivial, as the touchscreen needs to be
present at boot time and can't simply be switched off and on after
booting. There are lots of threads on this, e.g.
https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=120968&start=150
The power saving mode integrated into PCP/jivelite only works with the
official display.
I found the pinout here:
https://diyhacking.com/raspberry-pi-touchscreen-lcd-tutorial/ - its for
the 3.2 Inch display, but I suppose that its identical for the 3.5.
Has anybody succeeded in finding a solution for a power saving mode for
the touchscreen?
Best regards
Martin



PCP (always latest version) on RasPi 3 with PhatDac (player & server)
PCP on several RasPis 2 +3
2 Airplay speakers (Sony SA-NS510) integrated via Airplay Bridge Plugin
------------------------------------------------------------------------
streampunk's Profile: http://forums.slimdevices.com/member.php?userid=66210
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-26 21:53:56 UTC
Permalink
Does anyone have a 3.5" TFT up and running on a pCP with LMS also
installed? I've run into some weird issues trying to add LMS to a
working player.

I added a USB hard drive and enabled LMS and had it working, but when I
rebooted after enabling LMS autostart, the TFT no longer starts up when
Jivelite loads. Here's where it gets weird. Took me a while to figure
it out, but If I stop LMS the screen comes back to life. Then I can
start LMS and all works fine, screen works, touch works, DAC works, etc.
Basically everythings good until you restart and then I have to stop
LMS for the screen to start again.

I tried changing the order of things in dorebootstuff to try to load
Jivelite first, but I totally borked the system and locked it up during
boot. I'll keep tinkering with that, but in the meantime I thought I'd
check in here to see if I'm missing something obvious or if anybody else
has seen this behavior. I don't understand why LMS would prevent the
screen from receiving the Jivelite output.

Current setup is pCP 3.22, Pi3, pHatDAC, 3.5"TFT. Hardware all works
fine without LMS enabled.
Be glad to share any settings that might help.


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-01-27 15:11:33 UTC
Permalink
streampunk wrote:
> Hi,
> for all that are using the touchscreen display in self constructed
> mobile devices (i.e. running on battery power), it would be great to
> have an option to put the screen and its backlight into standby after a
> certain time.
> It seems that this is not really trivial, as the touchscreen needs to be
> present at boot time and can't simply be switched off and on after
> booting. There are lots of threads on this, e.g.
> https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=120968&start=150
> The power saving mode integrated into PCP/jivelite only works with the
> official display.
> I found the pinout here:
> https://diyhacking.com/raspberry-pi-touchscreen-lcd-tutorial/ - its for
> the 3.2 Inch display, but I suppose that its identical for the 3.5.
> Has anybody succeeded in finding a solution for a power saving mode for
> the touchscreen?
> Best regards
> Martin
In the past i spended some time to that problem and i cant find a
solution. I think there is no way to control the backlight of that
cheap displays. The controler chip is direct wired to 5V and has no
backlight pin. The hdmi versions of the waveshare displays have a
mechanical backlightswitch. For that ones you can found tutorials for
switching off the backlight via gpio.


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-27 20:32:43 UTC
Permalink
update on the failure of the TFT screen to start when LMS is
autostarted

When LMS is allowed to autostart, /dev/fb1 is not created:

Code:
--------------------
crw-rw---- 1 root staff 29, 0 Dec 31 1969 /dev/fb0
--------------------

When LMS is not autostarted, /dev/fb1 exists and jivelite starts on the
tft

Code:
--------------------
crw-rw---- 1 root staff 29, 0 Dec 31 1969 /dev/fb0
crw-rw---- 1 root staff 29, 1 Jan 27 13:42 /dev/fb1
--------------------

I guess I have a chicken/egg problem. I don't yet know/understand
enough about the framebuffer creation process, so I don't know what is
causing this issue. Why is the starting of LMS in the dorebootsuff
script causing the fb1 framebuffer to not get created? I don't see
anything in the LMS portion of the script that would effect the creation
of the framebuffer. Any ideas?


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-01-27 22:52:24 UTC
Permalink
@rmac321

Look here, maybe it helps:
http://forums.slimdevices.com/newreply.php?do=newreply&p=896587


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-28 04:30:44 UTC
Permalink
Another datapoint in my tft not starting when lms is autostarted saga.


fbtft doesn't appear in dmesg unless LMS autostart is off or if LMS is
manually stopped. Here is an example of fbtft finally showing up after
I manually stop LMS. Note nothing happens after 20 seconds until at 254
seconds I manually stopped LMS and then fbtft is enabled, /dev/fb1 is
created and jivelite finally breaks free from its 3 second while loop
and starts the screen.


Code:
--------------------
...
[ 15.263634] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 15.344685] fuse init (API version 7.26)
[ 20.205918] brcmfmac: power management disabled
[ 20.217741] brcmfmac: power management disabled
[ 254.930465] fbtft: module is from the staging directory, the quality is unknown, you have been warned.
[ 254.932766] flexfb: module is from the staging directory, the quality is unknown, you have been warned.
[ 254.942131] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned.
[ 254.943311] ads7846 spi0.1: ads7846 spi0.1 1000kHz 8 bits mode=0x00
[ 254.943349] bcm2708_fb soc:fb: soc:fb id=-1 pdata? no
...

--------------------


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-01-28 07:28:29 UTC
Permalink
We talked about this problem a few weeks ago.
Maybe my solution will help: 'link'
(http://forums.slimdevices.com/showthread.php?107366-picoreplayer-3-11-waveshare-3-5-TFT-jivelite-Raspberry-Pi-2B&p=896587&viewfull=1#post896587)


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-29 01:31:04 UTC
Permalink
piplayer,
Thanks, for the link. I have to admit, I missed that or forgot about it
as it didn't apply to my situation yet back when I read this thread the
first couple times last month.

The bad news is it didn't work. I unsquashed pcp-jivelite.tcz, edited
the script, resquashed and replaced. Switched the line in
do_rebootstuff back to that script. On reboot, same symptoms. I
verified that the revised script was persistent. Maybe I need to undo
some of the other NJW edits to the do_rebootstuff script, but I still
don't see what in that script is keeping the framebuffer from being
created and the jivelite binary from starting.

Bottom line: What in the LMS section of do_rebootstuff.sh causes the
Jivelite section from not running properly? I just don't see a culprit.


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-29 03:30:48 UTC
Permalink
Additional edits to do_rebootstuff.sh fix the symptom, but don't explain
the cause.

By adding a line that stops LMS at the beginning of the Jivelite section
of the do_rebootstuff script

Code:
--------------------
sudo /usr/local/etc/init.d/slimserver stop
--------------------

jivelite starts after about a 20 second delay.
Since that worked, I added a line at the end of the Jivelite section to
start LMS back up

Code:
--------------------
sudo /usr/local/etc/init.d/slimserver start
--------------------

That re-breaks it. Adding that to The Jivelite portion or even adding
it at the very end of do_rebootstuff causes jivelite to never start.
I tried adding a sleep command before LMS is restarted, but even
sleeping for 2 minutes doesn't allow jivelite to start.
The only way I've found to restart LMS is to call a separate script to
restart LMS.

Code:
--------------------
sudo /mnt/mmcblk0p2/tce/start_lms.sh >/dev/null 2>&1
--------------------

I still need someone who understands linux better than me to explain why
Jivelite doesn't start unless LMS is stopped and why issuing a command
in do_rebootstuff to restart LMS after jivelite is called still prevents
Jivelite from starting.


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-01-29 14:59:36 UTC
Permalink
The last idea I have is to disable slimserver autostart and put a
startup command in a user command line on the picorplayer web interface.
In my opinion, these commands are executed at the very end of
do_rebootstuff.sh. At this time Jivelite should be up and running. But I
dont know if it works.


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
Greg Erskine
2018-01-29 21:03:36 UTC
Permalink
FYI

[Main page] in [Beta] mode > [Diagnostics] > [Boot] shows you the boot
process.

Current order in do_rebootstuff.sh: LMS, User commands, Jivelite

regards
Greg


------------------------------------------------------------------------
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-29 21:47:57 UTC
Permalink
Greg,
Thanks. I do need reminding about that page as it is a nice summary of
all the various things to look through. In this case it doesn't give me
any more insight, it just confirms what I'm seeing looking at dmesg and
such via ssh.
I'm just baffled as to why the line
Code:
--------------------
SDL_VIDEODRIVER=fbcon SDL_FBDEV=/dev/fb1 /opt/jivelite/bin/jivelite &
--------------------
doesn't get executed if LMS is running. It doesn't matter if that line
is called from a separate script, if it is called before slimserver is
started or after. If slimserver is called in do_rebootstuff, the
framebuffer doesn't get created and jivelite doesn't start unless
slimserver is subsequently stopped. I've tried all the different
combinations I can think of. I've tried to start squeezelite and
jivelite before starting lms, but the common denominator is if the line
Code:
--------------------
sudo /usr/local/etc/init.d/slimserver start
--------------------
is allowed to execute inside do_rebootstuff, the line to create the
framebuffer and start jivelite will never finish executing until
slimserver is stopped. It just sits there waiting until slimserver is
stopped and then it loads jivelite immediately.

FWIW, if I remove the parts of the line calling jivelite that create the
framebufffer, then jivelite is started and output to the hdmi monitor,
so jivelite isn't the culprit. There is some conflict between
slimserver being called and the creation of the framebuffer. No doubt
I'm missing something obvious. Unfortunately it isn't obvious to me...


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-29 22:03:12 UTC
Permalink
FWIW, I do want to confirm that I have a workaround and that is to stop
and restart LMS in the scripts. It makes everything take longer to get
started. Plus the stop and restart of LMS defeats the power-on options
in pCP so you have to add another line to the scripts to start the
player once everything is finally running.

Basically, it makes the normally quick and graceful pCP a little clunky
when trying to make an LMS/TFT combo.


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-01-30 07:16:58 UTC
Permalink
rmac321 wrote:
>
> FWIW, if I remove the parts of the line calling jivelite that create the
> framebufffer, then jivelite is started and output to the hdmi monitor,
> so jivelite isn't the culprit. There is some conflict between
> slimserver being called and the creation of the framebuffer. No doubt
> I'm missing something obvious. Unfortunately it isn't obvious to me...
If the HDMI output works, then the framebuffer copy from fb0 to fb1 may
be the solution for you. Before I found out the solution with the
SDL_Videodriver, I had 'this tool'
(https://github.com/AndrewFromMelbourne/raspi2fb) to copy the contents
of the HDMI output (/dev/fb0) into the Waveshare display (/dev/fb1). But
if /dev/fb1 is not created, it probably will not work either.


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-30 15:12:55 UTC
Permalink
piplayer,
Thanks. I'll take a look, but as you said, if fb1 doesn't get created,
then there won't be a framebuffer to copy to. It looks like I'll need
to make an extension out of the raspi2fb files to test it, so when I
have a chance I'll play with it.


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-30 15:52:03 UTC
Permalink
I have a couple questions about some sections/items in do_rebootstuff.sh
and some observations from playing with various settings in pCP. I'm
hoping if I get a better understanding of what is happening, I can
better diagnose my setup. If anybody has any insight on the following,
I'd be grateful.

Starting from a working pCP with LMS set to autostart:
1a) Reset LMS autostart to "No" and reboot. When I subsequently attempt
to start LMS from the LMS page on the pCP interface, LMS never starts.
The output window never goes beyond:
Code:
--------------------
[ INFO ] Starting LMS...
[ INFO ]
--------------------

1b) Same scenario but I issue the startup command from a ssh/terminal.
Code:
--------------------
sudo /usr/local/etc/init.d/slimserver start
--------------------
I get the response:
Code:
--------------------
sudo: /usr/local/etc/init.d/slimserver: command not found
--------------------

Why is slimserver not in init.d if autostart is set to No?
When/how during initialization is slimserver placed in init.d when
autostart is set to Yes?

2) What is the purpose of the section in do_rebootstuff.sh
Code:
--------------------
if [ "$A_S_LMS" = "Enabled" ]; then
echo -n "${BLUE}Starting auto start LMS... ${NORMAL}"
pcp_auto_start_lms
echo "${GREEN}Done.${NORMAL}"
fi
--------------------

That section is after the section that actually starts LMS, so I don't
understand its purpose. When LMS autostart is set to Yes, this section
of the script is not run, or at least it's echo statements are never
output to the screen.

Thanks in advance!


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-30 16:42:45 UTC
Permalink
Answer to question 2
I think I can answer question 2. It looks like $A_S_LMS refers to the
"Auto start LMS" setting in the tweaks page rather than the similarly
named setting to Auto Start LMS itself on the LMS page. IOW, it is the
setting to tell LMS what to play on power-up.


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-30 16:59:22 UTC
Permalink
Eureka! Now that I found it, it's kind of a duh!
The solution to getting the framebuffer to be created promptly is in the
bootlocal.sh script. When jivelite was enabled, the modprobe settings
were placed at the end of bootlocal.sh after the call to
do_rebootstuff.sh, so since they aren't called yet the framebuffer isn't
created until after do_rebootstuff is finished in its entirety. Moving
the modprobe commands to execute before do_rebootstuff.sh causes the
framebuffer to be created and the screen to switch over and the rest of
the boot/setup messages are then displayed on the TFT.

I still don't know why slimserver needed to be stopped under the prior
circumstances, but moving the modprobe commands to precede
do_rebootstuff.sh negates the problem.

Hope this helps others


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
Greg Erskine
2018-01-30 22:10:20 UTC
Permalink
Great to see you found the solution! :D

100 points for persistence.

I have a feeling not many people use a screen/jivelite on their LMS,
it's not a combination I use or test.

Look at [Tweaks] > [Auto start tweaks] > Auto start LMS > help

Auto start LMS and Auto start favorites tweaks were added to pCP a long
time ago and have nothing to do with the pCP LMS installation. In
retrospect, I can see how the terminology is now confusing, but at the
time having LMS on pCP was not envisaged.

regards
Greg


------------------------------------------------------------------------
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
rmac321
2018-01-30 22:49:13 UTC
Permalink
Greg,
re: the 2nd autostart. Yea, when I realized it followed FAV, I recalled
that they were in that order on the tweaks page and realized that was
probably what it was.

re: TFT without LMS onboard. PiZeroW, TFT and picoreplayer make a great
combo for a little desktop now-playing screen. Bonus is add a DAC and
it can play as well, if you don't mind the occasional glitches of
wireless.

As to the addition of LMS, I don't know if I really need LMS and TFT on
same device, but it became a bit of a mission and learning experience to
figure it out. Was thinking of making a little desktop player for my
wife for her office. Could be nice for travel. I'd also like to use a
picoreplayer/LMS solution for the car, but the lack of an internet
connection will make LMS less friendly there. Mostly just exploring
what is possible while I mull over what to do with it...

Thanks again for the nudges in the right direction.


------------------------------------------------------------------------
rmac321's Profile: http://forums.slimdevices.com/member.php?userid=58482
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-01-31 06:49:40 UTC
Permalink
Hello rmac,

Congratulations, your endurance to find the problem has paid off.
I had the combination of LMS and TFT working before nowhinjing did his
tutorial. My workflow was a little different than the tutorial. In my
case, I manually wrote the entries in bootlocal.sh. That's why my boot
order is right.


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
streampunk
2018-01-31 15:05:27 UTC
Permalink
Congratulations! I've just setup up PCP + LMS from the scratch on a Zero
W with a cheap China 3.5 touchscreen. Using nowhinjing's tutorial (not
his files, they didn't work for me), everything works out of the box -
great!



PCP (always latest version) on RasPi 3 with PhatDac (player & server)
PCP on several RasPis 2 +3
2 Airplay speakers (Sony SA-NS510) integrated via Airplay Bridge Plugin
------------------------------------------------------------------------
streampunk's Profile: http://forums.slimdevices.com/member.php?userid=66210
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
streampunk
2018-02-09 11:43:04 UTC
Permalink
rmac321 wrote:
> Eureka! Now that I found it, it's kind of a duh!
> The solution to getting the framebuffer to be created promptly is in the
> bootlocal.sh script. When jivelite was enabled, the modprobe settings
> were placed at the end of bootlocal.sh after the call to
> do_rebootstuff.sh, so since they aren't called yet the framebuffer isn't
> created until after do_rebootstuff is finished in its entirety. Moving
> the modprobe commands to execute before do_rebootstuff.sh causes the
> framebuffer to be created and the screen to switch over and the rest of
> the boot/setup messages are then displayed on the TFT.
>
> I still don't know why slimserver needed to be stopped under the prior
> circumstances, but moving the modprobe commands to precede
> do_rebootstuff.sh negates the problem.
>
> Hope this helps others

Thanks a lot - it really helped me, I'd run into the same problem.



PCP (always latest version) on RasPi 3 with PhatDac (player & server)
PCP on several RasPis 2 +3
2 Airplay speakers (Sony SA-NS510) integrated via Airplay Bridge Plugin
------------------------------------------------------------------------
streampunk's Profile: http://forums.slimdevices.com/member.php?userid=66210
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
noise11
2018-03-17 06:46:51 UTC
Permalink
hi there! I'm trying to use this guide with a 4inch waveshare instead of
the 3.5inch, and I'm not sure if is that the problem or what the problem
is, but all I get is a white screen in tft, and in the hdmi output
"starting jivelite... done" and in yellow letters "trying to mount
/dev/sda1. done." "newconfig.cfg not found on mmcblk0p1. done, I also
tried to copy the waveshare overlay.dtb to mmcblk0p1 via "winscp" but i
don't have permission to paste files over there. what i'm missing? so
frustrated


------------------------------------------------------------------------
noise11's Profile: http://forums.slimdevices.com/member.php?userid=66033
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
Greg Erskine
2018-03-17 08:28:17 UTC
Permalink
hi noise11,

noise11 wrote:
> hi there! I'm trying to use this guide with a 4inch waveshare instead of
> the 3.5inch, and I'm not sure if is that the problem or what the problem
> is, but all I get is a white screen in tft,

I have read that revision one of the one of the screen boards had this
problem. Don't know if it applies to yours or not.

> and in the hdmi output "starting jivelite... done" and in yellow
> letters "trying to mount /dev/sda1. done." "newconfig.cfg not found on
> mmcblk0p1. done,

Standard boot messages. No problem here.

> I also tried to copy the waveshare overlay.dtb to mmcblk0p1 via "winscp"
> but i don't have permission to paste files over there. what i'm missing?
> so frustrated

mmcblk0p1 is a fat partition so no permission problem possible but
mmcblk0p1 is unmounted after pCP has booted. (hint: m1)

List of pCP shortcuts:
http://picoreplayer.sourceforge.net/pcp_aliases.shtml

regards
Greg


------------------------------------------------------------------------
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
noise11
2018-03-17 12:29:37 UTC
Permalink
Hi, just checked and the screen is rev.2 and makes sense since i bought
it last week, I'll try starting over again today maybe I failed
following the guide as it is, I'll appreciate any suggestion.


------------------------------------------------------------------------
noise11's Profile: http://forums.slimdevices.com/member.php?userid=66033
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
noise11
2018-03-18 02:04:40 UTC
Permalink
thank you guys, but i just returned this crap lcd to amazon and bought
an official 7 inch lcd and a nice bamboo made stand.


------------------------------------------------------------------------
noise11's Profile: http://forums.slimdevices.com/member.php?userid=66033
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-03-20 10:52:31 UTC
Permalink
noise11 wrote:
> thank you guys, but i just returned this crap lcd ...
The 4" Waveshare display works very well if you follow the instructions
of nowhinjing step by step.
You do not need a waveshare overlay, but you have to load the required
fbtft driver so that the display starts up when booting.
The display is not "crap", you just have to know what to do.


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
noise11
2018-03-21 05:08:28 UTC
Permalink
piPlayer wrote:
> The 4" Waveshare display works very well if you follow the instructions
> of nowhinjing step by step.
> You do not need a waveshare overlay, but you have to load the required
> fbtft driver so that the display starts up when booting.
> The display is not "crap", you just have to know what to do. actually that's what i did in repeat for a whole day, following the
guide step by step, and trying again and again, in my book a good
product doesnt have to be that hard to make it work, and theres lots of
guides and threads over the internet with more frustration than success,
in the other hand the raspberry pi 7 inch works out of the box.


------------------------------------------------------------------------
noise11's Profile: http://forums.slimdevices.com/member.php?userid=66033
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-03-21 09:36:45 UTC
Permalink
noise11 wrote:
> ... in the other hand the raspberry pi 7 inch works out of the box.
Yes and only this display is officially supported by picoreplayer. To
get all other displays working is much more difficult and requires some
linux knowledge. But I have both the original Waveshare 4 inch display
and a china clone called "4 inch rpi display" working well with
picoreplayer.
Therefore, I can only imagine that either your display was broken or you
did something wrong.


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
noise11
2018-03-21 05:13:11 UTC
Permalink
piPlayer wrote:
> The 4" Waveshare display works very well if you follow the instructions
> of nowhinjing step by step.
> You do not need a waveshare overlay, but you have to load the required
> fbtft driver so that the display starts up when booting.
> The display is not "crap", you just have to know what to do. and just out of curiosity i tried the raspbian image provided in the
mini cd included with the lcd... didn't work lol.


------------------------------------------------------------------------
noise11's Profile: http://forums.slimdevices.com/member.php?userid=66033
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
streampunk
2018-02-01 16:33:13 UTC
Permalink
piPlayer wrote:
> In the past i spended some time to that problem and i cant find a
> solution. I think there is no way to control the backlight of that
> cheap displays. The controler chip is direct wired to 5V and has no
> backlight pin. The hdmi versions of the waveshare displays have a
> mechanical backlightswitch. For that ones you can found tutorials for
> switching off the backlight via gpio.
I've asked the vendor, and he answered:
> Unfortunately, the backlight can't be switchd off, but you can put the
> display into standby mode in order to reduce power consumption when
> running on battery power.
> Please have a look at:
> https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling
I'm far from being an expert, but I suppose that this only applies when
the display is used wit an x server?
Perhaps somebody has more knowledge than me to evaluate this?
Best regards
Martin



PCP (always latest version) on RasPi 3 with PhatDac (player & server)
PCP on several RasPis 2 +3
2 Airplay speakers (Sony SA-NS510) integrated via Airplay Bridge Plugin
------------------------------------------------------------------------
streampunk's Profile: http://forums.slimdevices.com/member.php?userid=66210
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
bvlet
2018-02-06 01:30:33 UTC
Permalink
I just wanted to confirm that this solution is also working with
piCorePlayer 3.22 on my pi Zero W, connected to a cheap (8 euro) Chinese
version of the waveshare TFT!

https://nl.aliexpress.com/item/3-5-Inch-TFT-LCD-Moudle-For-Raspberry-Pi-2-Model-B-RPI-B-raspberry-pi/32707058182.html

I had to modify some things, but now it's working perfectly with a USB
DAC!
If there's any interest I can share my modified files.

Thanks for helping me to set this up!

Regards, Bart


------------------------------------------------------------------------
bvlet's Profile: http://forums.slimdevices.com/member.php?userid=67766
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-02-06 12:04:23 UTC
Permalink
patrick31698 wrote:
> Any experiences on this TFTs with the first generation Pis?
The pinout of the linked Chinese touch screen is identical to the
Waveshare 3.5 "and 4" displays.
I believe in China they are cloning their own products. :rolleyes:
So it should work with the tutorial from nowhinjing.
I have a 4 inch China display identical to the 4 inch from Waveshare in
operation on a Raspberry Pi 1 B.
The performance is more than enough.


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
patrick31698
2018-02-06 14:11:47 UTC
Permalink
piPlayer wrote:
>
> I have a 4 inch China display identical to the 4 inch from Waveshare in
> operation on a Raspberry Pi 1 Model B.
> The performance is more than enough.

Great! I have two Pi 1 B lying around here. i always thought of building
a fancy WifiAlarm clock. So i think i will give it a try


------------------------------------------------------------------------
patrick31698's Profile: http://forums.slimdevices.com/member.php?userid=67060
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
wl1
2018-02-06 19:37:24 UTC
Permalink
How do!

I followed the instructions for the getting my Official RPi Display
working with the RPi and piCorePlayer. It is working of a fashion, just
the precision of the screen, particularly at the edges, is not working.

I looked at the instructions for calibrating (the albeit different)
display from here :- http://www.pughx2.com/picore320.html

24492

and got this error:- ""Open fbdevice: no such file or error""

Response to the Cat command
***@Boom2:~/www$ cat /proc/bus/input/devices
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="FT5406 memory based driver"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0
B: PROP=2
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=2608000 3

I have tried searching for what I assume is a ts_calibrate file that is
being invoked - and I can't find it. (Learning linux commands as i go -
and Locate did not work for this).

I have no experience here - so I am likely missing something
simple.....everything else went really well :-)

Any pointers would be appreciated. Thanks,


+-------------------------------------------------------------------+
|Filename: TouchScreen Calibrate.PNG |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=24492|
+-------------------------------------------------------------------+

------------------------------------------------------------------------
wl1's Profile: http://forums.slimdevices.com/member.php?userid=9842
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
piPlayer
2018-02-06 20:44:01 UTC
Permalink
For the official 7" RPI Display You have to follow this instruction:
'link'
(https://github.com/ralph-irving/tcz-jivelite/blob/master/README.md)


------------------------------------------------------------------------
piPlayer's Profile: http://forums.slimdevices.com/member.php?userid=65280
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
sbp
2018-02-06 21:46:11 UTC
Permalink
wl1 wrote:
> How do!
>
> I followed the instructions for the getting my Official RPi Display
> working with the RPi and piCorePlayer. It is working of a fashion, just
> the precision of the screen, particularly at the edges, is not working.
> ........
>
> I have no experience here - so I am likely missing something
> simple.....everything else went really well :-)
>
> Any pointers would be appreciated. Thanks,

Hi. I notice that you mention the Official RPi Display. When you are
using this display you simply need to attach it and then enable
Jivelite. This screen is working fine directly "out of the box" with
pCP. The touch function is already calibrated.
So there is really no need for you to mess with these commands and
scripts etc.

This is the official screen:
https://www.modmypi.com/pis-and-peripherals-1139/raspberry-pi-7-touchscreen-display-official
- and it is the only screen that is officially supported by pCP. Our
problem is that it is impossible for us to manage and support all
available "third party" screens.



piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://sites.google.com/site/picoreplayer/home

*Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=U7JHY5WYHCNRU&lc=GB&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted)
if you like the piCorePlayer*
------------------------------------------------------------------------
sbp's Profile: http://forums.slimdevices.com/member.php?userid=37237
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
wl1
2018-02-06 22:35:24 UTC
Permalink
sbp wrote:
>
>
> This is the official screen:
> https://www.modmypi.com/pis-and-peripherals-1139/raspberry-pi-7-touchscreen-display-official
> - and it is the only screen that is officially supported by pCP. Our
> problem is that it is impossible for us to manage and support all
> available "third party" screens.
Yes, that’s the Display I purchased.

The previous poster linked to a complicated process, but I guess you
have it integrated now. Any extensions I need st all? Is joggler the
correct selection?

I’m not sure why my touchscreen feels so difficult to use. If there is
nothing I can do to calibrate - are other Official Displays showing
similar behaviours.?

I’m having to tip toe around it, softly pressing it. And volume button
(bottom right) is particularly irksome.

Thanks for your responses.




------------------------------------------------------------------------
wl1's Profile: http://forums.slimdevices.com/member.php?userid=9842
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
Greg Erskine
2018-02-06 23:12:28 UTC
Permalink
hi wl1,

All the pCP developers use the "official" Raspberry Pi screen, so you
should expect perfect results.

I recommend you restart from scratch.

1. Burn new pCP image on SD card.
2. Go to [ Tweaks ] > [ Jivelite Setup ] > [ Install ]
3a. If prompted, expand SD card. (100 MB will be enough, wait till it
reboots a couple of times)
3b. Go to [ Tweaks ] > [ Jivelite Setup ] > [ Install ] (yes again, it
didn't install before)

On Jivelite screen:
4. Select Language
5. Select Grid Skin (800 x 480) ( or Joggler)

Note: If you select some weird resolution you may end up with unusual
results.

People sometimes forget to come back and do Step 3b. I can see the
slightly illogical installation process.

regards
Greg


------------------------------------------------------------------------
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forums.slimdevices.com/showthread.php?t=107366
Loading...