Support for: 7″ Touchscreen Monitor for Raspberry Pi

Suggestions/requests/ideas for RuneAudio core features and functions

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby indy49 » 21 Jan 2017, 09:51

Hi hondagx35,

Thank you for your interest.
Except that the screen is white (with backlight I mean), there is nothing on it (no boot message).
So I guess this is bad news...

I bought a bundle :
- The rPI was in a box with a raspberry on it. It is written "Made in UK" and "Allied Electronics" too
- The screen was in a neutral box. Here is what I see on the board : "3.5inch RPi Display 480x320 Pixel XPT2046 Touch Controller"

Does this help?

Thank you again,

Tony
indy49
 
Posts: 7
Joined: 20 Jan 2017, 16:44

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby hondagx35 » 21 Jan 2017, 11:36

Hi Tony,

Does this help?

No, not really.

And you got no documentation with the kit?

All small displays with direct connection (GPIO header) to the Pi have one in common.
They are driven by a so-called SPI interface and they need a special driver.
On a RP2/3 with latest Rune Audio image these drivers have to be enabled in /boot/config.txt.

Here is an example for the Adafruit PiTFT 3.5" display
Code: Select all
Name:   pitft35-resistive
Info:   Adafruit PiTFT 3.5" resistive touch screen
Load:   dtoverlay=pitft35-resistive,<param>=<val>
Params: speed                   Display SPI bus speed

        rotate                  Display rotation {0,90,180,270}

        fps                     Delay between frame updates

        debug                   Debug output level {0-7}


This should look like this:
Code: Select all
.....
.....

# LCD settings
# 180 degrees
#lcd_rotate=2
# Normal
#lcd_rotate=0
#dtoverlay=rpi-backlight
#dtoverlay=rpi-ft5406
#disable_splash=1
dtoverlay=pitft35-resistive,rotate=90,speed=42000000,fps=20


I also would update the kernel:
post19169.html#p19169

Frank
User avatar
hondagx35
 
Posts: 3041
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby indy49 » 21 Jan 2017, 18:30

Thanks Franck.

I believe I have done everything: extend the partition, update kernel, and modify the config.txt.
My screen stays the same (backlit, but no information displayed).

Still, I have a question: during the kernel update, I have seen a message looking like :
Code: Select all
config.txt has been replaced by config.txt.pacnew

Does that meant I should have modified config.txt.pacnew in order to put the dtoverlay line ?

config.txt.pacnew only contains the following :
Code: Select all
gpu_mem=64

So I assumed it was not it I was supposed to modify, and did modify the one you said (/boot/config.txt)
Was I wrong?

(I also did reboot the pi between each main step and at the end).

Thank you again for your patience...
indy49
 
Posts: 7
Joined: 20 Jan 2017, 16:44

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby hondagx35 » 22 Jan 2017, 01:04

Hi indy49,

Was I wrong?

No, you have modified the correct one.

The pitft35-resistive entry was only an example, we need to know the exact brand and model.

Frank
User avatar
hondagx35
 
Posts: 3041
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby indy49 » 22 Jan 2017, 09:24

Hi Franck,
OK, I've asked the vendor to give me missing information.
Thanks again and have a nice day
indy49
 
Posts: 7
Joined: 20 Jan 2017, 16:44

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby indy49 » 22 Jan 2017, 18:28

The vendor could not tell me the model but provided me with some files... :?

Two are named waveshare35a-overlay.dtb and waveshare32b-overlay.dtb
As my screen is 3.5", I would expect the right LCD model to be waveshare35a.
I then tried to add the following lines to config.txt
Code: Select all
dtoverlay=waveshare35a
dtoverlay=w1-gpio-pullup,gpiopin=4,extpullup=1

But the screen is still blank

What do you think?
Do you know this screen and, if so, what should be the config.txt lines?

Tony
indy49
 
Posts: 7
Joined: 20 Jan 2017, 16:44

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby hondagx35 » 22 Jan 2017, 22:45

Hi Tony,

please read this
waveshare-spotspear-3-5-touch-screen-working-with-rune-t3859.html
maybe it will help.

Frank
User avatar
hondagx35
 
Posts: 3041
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby indy49 » 23 Jan 2017, 18:50

Hi Frank,
I did everything of what is written in the link, but I still have nothing...
It's weird because the component layout on the back of my screen looks exactly the same as the one in the post.

Still, I noted one weird thing :
In the post, it is said
Code: Select all
Add the following to /etc/modules-load.d/raspberrypi.conf:

Whereas this file did not exist on my rPI.
I thus created it on my own, but do you think this could be a hint to the trouble?
Regards,
Tony
indy49
 
Posts: 7
Joined: 20 Jan 2017, 16:44

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby hondagx35 » 23 Jan 2017, 23:23

Hi Tony,

What do you think?

Please check the log files.
Code: Select all
journalctl

or
Code: Select all
dmesg

for errors.

Frank
User avatar
hondagx35
 
Posts: 3041
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: Support for: 7″ Touchscreen Monitor for Raspberry Pi

Postby indy49 » 24 Jan 2017, 13:34

Hi Franck,

First are the logs without the 3 "optional" lines of raspberrypi.conf

Here are the errors I've seen with dmesg:
[ 5.717274] w1_add_master_device: set_pullup requires write_byte or touch_bit, disabling
[...]
[ 6.207058] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c
[...]
[ 7.312092] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[ 7.312121] brcmfmac: brcmf_add_if: ignore IF event
[...]
[ 7.454072] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[ 7.454088] brcmfmac: brcmf_add_if: ignore IF event


And now with journalctl :
Jan 24 13:09:03 runeaudio systemd[1]: Time has been changed
Jan 24 13:09:03 runeaudio systemd[1]: Starting Verify integrity of password and group files...
Jan 24 13:09:03 runeaudio systemd[1]: Starting Rotate log files...
Jan 24 13:09:03 runeaudio pwck[868]: user 'mpd': directory '/home/mpd' does not exist
Jan 24 13:09:03 runeaudio pwck[868]: user 'smbd': directory '/home/smbd' does not exist
Jan 24 13:09:03 runeaudio pwck[868]: user 'upmpdcli': directory '/home/upmpdcli' does not exist
Jan 24 13:09:03 runeaudio pwck[868]: user 'frank': directory '/home/frank' does not exist
Jan 24 13:09:03 runeaudio pwck[868]: pwck: no changes
Jan 24 13:09:03 runeaudio logrotate[871]: error: skipping "/var/log/runeaudio/ui_error.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
Jan 24 13:09:03 runeaudio systemd[1]: shadow.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jan 24 13:09:03 runeaudio systemd[1]: Failed to start Verify integrity of password and group files.
Jan 24 13:09:03 runeaudio systemd[1]: shadow.service: Unit entered failed state.
Jan 24 13:09:03 runeaudio systemd[1]: shadow.service: Failed with result 'exit-code'.
Jan 24 13:09:03 runeaudio systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
Jan 24 13:09:03 runeaudio systemd[1]: Failed to start Rotate log files.
Jan 24 13:09:03 runeaudio systemd[1]: logrotate.service: Unit entered failed state.
Jan 24 13:09:03 runeaudio systemd[1]: logrotate.service: Failed with result 'exit-code'.
Jan 24 13:09:14 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.800000000000.8c is not registered.
Jan 24 13:09:25 runeaudio kernel: cfg80211: Verifying active interfaces after reg change
Jan 24 13:09:51 runeaudio sshd[918]: Accepted password for root from 192.168.1.11 port 49324 ssh2
Jan 24 13:09:51 runeaudio sshd[918]: pam_unix(sshd:session): session opened for user root by (uid=0)
Jan 24 13:09:51 runeaudio dbus[295]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Jan 24 13:09:51 runeaudio dbus[295]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.login1.service': Unit systemd-logind.service is masked.
Jan 24 13:09:51 runeaudio sshd[918]: pam_systemd(sshd:session): Failed to create session: Unit systemd-logind.service is masked.
Jan 24 13:10:13 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.400000000000.46 is not registered.
Jan 24 13:11:01 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.c00000000000.ca is not registered.
Jan 24 13:12:12 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.200000000000.23 is not registered.
Jan 24 13:13:11 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.a00000000000.af is not registered.
Jan 24 13:13:46 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.600000000000.65 is not registered.
Jan 24 13:14:24 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.e00000000000.e9 is not registered.
Jan 24 13:15:23 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.100000000000.9d is not registered.
Jan 24 13:15:59 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.900000000000.11 is not registered.
Jan 24 13:17:09 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.500000000000.db is not registered.
Jan 24 13:17:58 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.d00000000000.57 is not registered.
Jan 24 13:18:22 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.300000000000.be is not registered.
Jan 24 13:19:08 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.b00000000000.32 is not registered.
Jan 24 13:19:45 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.700000000000.f8 is not registered.
Jan 24 13:20:33 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.f00000000000.74 is not registered.


Now the logs with the said lines

Here are the errors I've seen with dmesg:
[ 5.051524] systemd[1]: Failed to start Load Kernel Modules.
[...]
[ 5.736902] w1_add_master_device: set_pullup requires write_byte or touch_bit, disabling
[ 5.742399] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[ 5.983753] ads7846 spi0.1: touchscreen, irq 183
[ 5.984258] input: ADS7846 Touchscreen as /devices/platform/soc/3f204000.spi/spi_master/spi0/spi0.1/input/input0 <<----- Here we see a touchscreen, but no error, if I'm correct
[...]
[ 6.218272] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c
[...]
[ 7.340594] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[ 7.340611] brcmfmac: brcmf_add_if: ignore IF event
[ 7.344845] brcmfmac: power management disabled
[ 7.483947] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[ 7.483962] brcmfmac: brcmf_add_if: ignore IF event


And now with journalctl :
Jan 24 13:24:07 runeaudio systemd[1]: Time has been changed
Jan 24 13:24:07 runeaudio ntpd[345]: receive: Unexpected origin timestamp 0xda759c60.90f9efdd from 163.172.10.212 xmt 0xdc31c5e7.dfd6e92e
Jan 24 13:24:14 runeaudio sudo[559]: pam_unix(sudo:session): session closed for user root
Jan 24 13:24:40 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.800000000000.8c is not registered.
Jan 24 13:24:51 runeaudio kernel: cfg80211: Verifying active interfaces after reg change
Jan 24 13:25:39 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.400000000000.46 is not registered.
Jan 24 13:25:42 runeaudio sshd[891]: Accepted password for root from 192.168.1.11 port 49394 ssh2
Jan 24 13:25:42 runeaudio sshd[891]: pam_unix(sshd:session): session opened for user root by (uid=0)
Jan 24 13:25:42 runeaudio dbus[288]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
Jan 24 13:25:42 runeaudio dbus[288]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.login1.service': Unit systemd-logind.service is masked.
Jan 24 13:25:42 runeaudio sshd[891]: pam_systemd(sshd:session): Failed to create session: Unit systemd-logind.service is masked.
Jan 24 13:26:26 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.c00000000000.ca is not registered.
Jan 24 13:27:38 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.200000000000.23 is not registered.
Jan 24 13:28:37 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.a00000000000.af is not registered.
Jan 24 13:29:12 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.600000000000.65 is not registered.
Jan 24 13:29:50 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.e00000000000.e9 is not registered.
Jan 24 13:30:48 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.100000000000.9d is not registered.
Jan 24 13:31:25 runeaudio kernel: w1_master_driver w1_bus_master1: Family 0 for 00.900000000000.11 is not registered.
indy49
 
Posts: 7
Joined: 20 Jan 2017, 16:44

support RuneAudio Donate with PayPal

PreviousNext

Return to Feature request

Who is online

Users browsing this forum: No registered users and 0 guests