Raspberry 3 , RuneAudio and TFT 2.2" HAT install ?

[tinhdhmo]

I buy a TFT Display 2.2" Hat from https://item.taobao.com/item.htm?spm=a2 ... t=6#detail
Some pictures :


It use GPIO interface , when i plug in to Raspberry3 run RuneAudio , nothing display I found way to install at here : https://learn.adafruit.com/adafruit-2-2 ... sy-install
But i can not do it

Can anyone help me ?

Sorry I dont know more English
Thank you so much

[SimonDechain]

Hello,
Yes, I can try to help you, but I must warn you in advance, I do not own such a TFT-Modul, so you'll have to do most of the heavy lifting. So please, if a step fails, tell me and supply as much usable information as you can ("It did not work" will not help me much). Also since I do not know, how experienced you are with linux, I'll try to keep things as simple as possible.

It is not a surprise, that the instruction do not work. They have been written for the official Raspbian image based on debian. RuneAudio itself runs on Arch Linux.

1. Step: Hardware test
First of all, your display differs slightly from the one linked in the adafruit blog post. So as a first step, you'll have to try if it works as expected with the drivers from the website. Have you tried the premade image on the adafruit website to verify, that your hardware works and is compatible? If not, please download the "Ready to Go" jessie image (https://learn.adafruit.com/adafruit-2-2 ... o-go-image) and boot the pi to see it working.
It only makes sense to proceed, if we can be sure, that the instructions will work for your display.

2. Step: Install the Runeaudio image
Please use the image created by hondagx35 for the raspberry pi 3 from here: the-raspberry-pi-3-t3256-80.html#p12370
It should be the same as the one from the main download page, but I can not swear.

2. Step: Use the helper script
When you boot up rune, you should not see anything on the display. That's okay, since we have to install the drivers.
So SSH into your raspberry pi (f.e. with putty). The default credential are user "root" and password "rune".
The helper script from adafruit should work with the runeaudio image. To use it, execute the following commands:

Get the device tree overlay:

Code: Select all

curl -L --output /boot/overlay/pitft22.dtb https://github.com/AndrewFromMelbourne/raspi-device-tree/raw/master/pitft22-overlay.dtb

Get the script and make it executable:

Code: Select all

curl -L --output /root/adafruit-pitft-helper https://raw.githubusercontent.com/adafruit/Adafruit-PiTFT-Helper/master/adafruit-pitft-helper && chmod +x /root/adafruit-pitft-helper

Execute it:

Code: Select all

export SYSTEMD=1 && /root/adafruit-pitft-helper -t 22 -u /root

Then follow the description on the adafruit website after the Text "This will install the 2.2" type of PiTFT into the current install.". If you get any "Exiting due to error" text printed anywhere in the progress, copy and paste the whole output of the last command in a code-tag.

3. Step: Enable the local browser
On your PC navigate your web browser to http://runeaudio (or http://<ip-of-the-raspberry-pi>). In the Settings, enable the local browser.

After that restart your raspberry pi. If all went well, you should see a local browser after the startup.
Greetings and good luck,
Simon

[tinhdhmo]

Thank you for your support, when i try step 1 , have an error as below:

[root@runeaudio ~]# curl -L --output /boot/overlay/pitft22.dtb https://github.com/AndrewFromMelbourne/ ... verlay.dtb
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 164 100 164 0 0 140 0 0:00:01 0:00:01 --:--:-- 140
Warning: Failed to create the file /boot/overlay/pitft22.dtb: No such file or
Warning: directory
100 1550 100 1550 0 0 876 0 0:00:01 0:00:01 --:--:-- 876
curl: (23) Failed writing body (0 != 1550)
[root@runeaudio ~]#

[hondagx35]

Hi,

Thank you for your support, when i try step 1 , have an error as below:

This is because the folder is "/boot/overlays" and not "/boot/overlay".

Code: Select all

curl -L --output /boot/overlays/pitft22.dtb https://github.com/AndrewFromMelbourne/raspi-device-tree/raw/master/pitft22-overlay.dtb

Frank

[jss2]

Hello folks,

Rather than creating a new thread, I figured I'd sort of hijack this one.

I have a Raspberry Pi 3, and I recently puchased a 3.5" TFT screen.
Specifically, this is the TFT screen that I have: https://www.adafruit.com/products/2441

I've trying to take the instructions here, and adapt them to work with my 3.5" resistive touchscreen, rather than the 2.2" TFT screen discussed above.

First off, I tested the modifed Raspbian image provided by Adafruit, and everything booted up just fine and the screen works as expected. So I know that there's no hardware issue.

For the first step, get the device tree overlay, the file I need is the "pitft35r-overlay.dtb" (rather than "pitft22-overlay.dtb" discussed above). Because I wasn't sure of the github.com link to download the device tree overlay, I just grabbed the "pitft35r-overlay.dtb" from the Rasbian image provided by Adafruit, and then copied it manually to my Rune /boot/overlays/ folder. Hopefully that isn't going to cause problems.

Next I used the second command listed above to get the adafruit script and make it executable.

Code: Select all

curl -L --output /root/adafruit-pitft-helper https://raw.githubusercontent.com/adafruit/Adafruit-PiTFT-Helper/master/adafruit-pitft-helper && chmod +x /root/adafruit-pitft-helper

then I executed the script with this:

Code: Select all

export SYSTEMD=1 && /root/adafruit-pitft-helper -t 35r -u /root

(same as above, but modified "-t 22" to "-t 35r" to match my screen).

All seems to go well, until the very end, this is the error that I get:

Code: Select all

[root@runeaudio ~]# curl -L --output /root/adafruit-pitft-helper https://raw.githubusercontent.com/adafruit/Adafruit-PiTFT-Helper/master/adafruit-pitft-helper && chmod +x /root/adafruit-pitft-helper
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 11034  100 11034    0     0  30683      0 --:--:-- --:--:-- --:--:-- 31081
[root@runeaudio ~]# export SYSTEMD=1 && /root/adafruit-pitft-helper -t 35r -u /root
Type = 35r
Homedir = /root
[PITFT] Checking init system...
Found systemd
/boot is mounted
[PITFT] Updating X11 default calibration...
[PITFT] Updating X11 setup tweaks...
grep: /root/.profile: No such file or directory
Adding 'export FRAMEBUFFER=/dev/fb1'
[PITFT] Updating TSLib default calibration...
[PITFT] Updating SysFS rules for Touchscreen...
Would you like the console to appear on the PiTFT display? [y/n] y
[PITFT] Updating console to PiTFT...
Updating /boot/cmdline.txt
sed: can't read /etc/kbd/config: No such file or directory
[PITFT] Exiting due to error: Unable to configure console
[root@runeaudio ~]#


the last question that comes up during the script, "Would you like the console to appear on the PiTFT display? [y/n]", I've tried both yes and no. With "no", I don't get any error, but the screen doesn't work with Rune upon reboot. With "yes", I get the error that you see above. And the screen doesn't work with Rune.

Yes, I've logged on via web browser from my laptop and made sure that the local browser option is turned on.

Any help or guidance to get my new 3.5" TFT working is greatly appreciated.

Thanks.

- Jason

[rlsten]

Can anyone confirm that they got the Adafruit 2.2" or 3.5" capacitive touch screen to work properly with Rune Audio? If so, how did you manage to get it to work?

Thanks,
Rod

[SimonDechain]

Hello Jason,
Okay, I'll try to guide you through the fault finding (since, as stated above, I don't own a screen)

1. Framebuffer devices
What is the output of the following command:

Code: Select all

ls -l /dev/fb*

You should see both fb0 (the HDMI) and fb1 (the SPI-Screen).

If fb1 is present, goto 2.
If not, then the screen was not initialized correctly by the kernel/device tree, goto 5.

2. Do you have a HDMI-Screen to verify, the local browser is showing
If you can't test trough the HDMI, goto 3.

If yes, please attach it to the PI and reboot. If the local browser is shown of fb0, goto 4.
If no, goto 5.

3. Force X onto fb1
Execute the following commands:

Code: Select all

killall xinit
killall -9 xinit
FRAMEBUFFER=/dev/fb1 startx

Do you have an output on the screen? If yes, goto 4.

4. Change the framebuffer device
Execute the following command:

Code: Select all

pacman -S xf86-video-fbdev

Create file: /usr/share/X11/xorg.conf.d/99-fbdev.conf
Content:

Code: Select all

Section "Device" 
  Identifier "myfb"
  Driver "fbdev"
  Option "fbdev" "/dev/fb1"
EndSection


Restart, if the local browser doesn't show up, goto 5.

5. Log files
Please supply the debug information from Rune (see here) and additionally the output of the following commands:

a) installed packages

Code: Select all

pacman -Qe

b) X11 log
post your /var/log/Xorg.0.log

c) dev tree

Code: Select all

ls -l /dev

d) Device Tree debug
Add the following line to your /boot/config.txt:

Code: Select all

dtdebug=1

reboot and post the output of

Code: Select all

/opt/vc/bin/vcdbg log msg

[jss2]

Hello Simon,

I appreciate you taking the time to help me figure this out, especially as you don't have any TFT hardware to test stuff on. I do have an HDMI screen (though my samsung TV is not touchscreen) to test the local browser stuff on.

Upon first boot with a clean install of RuneAudio, I see on my TV that the local browser is active via HDMI. I then ran the adafruit script as listed in my previous post, and I can no longer see the local browser via the HDMI out (verified that it's still active in the settings).

Step 1. Framebuffer devices

Code: Select all

[root@runeaudio ~]# ls -l /dev/fb*
crw-rw---- 1 root video 29, 0 Feb 22 15:40 /dev/fb0

fb1 is not present, so I take it that the screen was not initialized correctly by the kernel/device tree.

Here is the debug info from the RuneAudio UI
http://pastebin.com/SQvL1dW7

a) installed packages:
http://pastebin.com/sLfNVv9Q

b) X11 log, post your /var/log/Xorg.0.log
http://pastebin.com/M8jeD9U6

c) dev tree
http://pastebin.com/M3Hu7Sv3

d) Device Tree debug
http://pastebin.com/bTRuYEiZ

As I said at the start, I really appreciate you taking the time to look through these logs and spending your time helping me to figure this out.

Thanks,
Jason

[hondagx35]

Hi Simon, hi Jason,

this will not work.
The description and overlay are for a patched 3.xx kernel.
The kernel used for the latest Rune images is 4.xx and has the fbtft drivers included.

You can try to load the driver (fb_hx8357d.ko.gz) manually and check what happens.

Code: Select all

modprobe fb_hx8357d.ko

Frank

[jss2]

Frank, I appreciate you chiming in and offering some advice.

This is what I get:

Code: Select all

[root@runeaudio ~]# modprobe fb_hx8357d.ko
modprobe: FATAL: Module fb_hx8357d.ko not found in directory /lib/modules/4.1.20-1-ARCH

This is with a fresh, clean RuneAudio install. I'll do some digging on my own to see what I can figure out, but any other tips/help you can provide would be great.

Thanks,
Jason