LED (VFD) Displays in LibreELEC

Sholander · April 2, 2018 at 4:23 PM

Quote from The Coolest

Download it from this post, then it should work. (just tested it to confirm)

Btw, did you test it with this version "LibreELEC-S912.arm-8.2.4-S912-Subtitles-fix.tar" on which I am trying to get the display working?

**The Coolest** · April 2, 2018 at 4:33 PM

Sholander

Everything is explained in the post I linked, it works with the older kernel. (pre-8.90.4)

Sholander · April 2, 2018 at 6:34 PM

It does just not work for me...

Fresh installs of "LibreELEC-S912.arm-8.2.4-Oclock-GPU.img" (even done once with your dtb.img file)

Running install.sh from your "FD628 Display.zip" results with:

Code

Using username "root".
[email protected]'s password:
##############################################
#                  LibreELEC                 #
#            https://libreelec.tv            #
##############################################

LibreELEC (kszaq-wrx): 8.2.4-Oclock-GPU (S912.arm)
LibreELEC:~ # cd radni
LibreELEC:~/radni # sh install.sh
LibreELEC:~/radni # Open device failed.
: No such file or directory

LibreELEC:~/radni #

Display More

Nothing on display. Rebbot

Installing your service.fd628.zip (from FD628 Display.zip) -> nothing on display. Reboot

Placed vfd.conf in .config -> nothing on display. Reboot

Trying all posible driver configurations -> nothing on display

Tried several dtb.img files for old kernel and the only time I get something on display is when I use your "gxm_q200_3g_x92.dtb". But then the display looks like this: Image

In this case no settings can change anything on the display...

I'm giving up

**The Coolest** · April 2, 2018 at 8:03 PM

Sholander

Edit:

You can give up, I can't really help with that. There's nothing complicated about getting the new driver to work on LE 8.x.

You need 3 things:

1) The gxm_q200_3g.dtb from the zip I attached, as all the DTBs in that zip contain an entry the driver requires to load and work.

2) The up to date driver\service from the same post I linked (on page #8).

3) The vfd.conf file for the x92 placed in /storage/.config/ folder (It's 'Configfiles' from the SMB share).

After a clean boot, with the most up to date driver\service from the post I linked, do:

Code

sh test_led.sh
dmesg | grep FD628

And paste the output.

I also want to add that this driver I posted is not an 'official' or 'supported' feature. I decided to post it just to help those who are using old builds get their display working.

Whoever creating these new builds based on 8.x should update their sources with the latest PRs to bake the latest driver into the images they post.

Sholander · April 3, 2018 at 12:38 AM

I did it now with files for "normal v.8.2.4" (not OC version) with correct files.

After boot I get almost a correct display and this is the output:

Code

Using username "root".
[email protected]'s password:
##############################################
#                  LibreELEC                 #
#            https://libreelec.tv            #
##############################################

LibreELEC (community): 8.2-8.2.4 (S912.arm)
LibreELEC:~ # cd radni
LibreELEC:~/radni # chmod 0755 FD628Service
LibreELEC:~/radni # sh test_led.sh
No command line options were found, showing usage instructions.

Usage: FD628Service [-t] [-dt TYPE] [-h]

        -t              Run FD628Service in display test mode.
        -dt N           Specifies which display type to use.
        -co N...        < D HH:MM > Order of display chars.
                        Valid values are 0 - 6.
                        (D=dots, represented by a single char)
        -h              This text.

LibreELEC:~/radni # dmesg | grep FD628
[   14.520222@4] FD628: vfd_gpio_clk:           #0 = 0x00; #1 = 0x41; #2 = 0x00;
[   14.520242@4] FD628: vfd_gpio_dat:           #0 = 0x00; #1 = 0x40; #2 = 0x00;
[   14.520249@4] FD628: vfd_gpio_stb:           #0 = 0x00; #1 = 0x42; #2 = 0x00;
[   14.520259@4] FD628: vfd_chars:              #0 = 0x04; #1 = 0x00; #2 = 0x01; #3 = 0x02; #4 = 0x03;
[   14.520270@4] FD628: vfd_dot_bits:           #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
[   14.520278@4] FD628: vfd_display_type:       #0 = 0x02; #1 = 0x00; #2 = 0x01; #3 = 0x00;
[   14.520288@4] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 65, offset = 220
[   14.520294@4] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 64, offset = 219
[   14.520301@4] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 66, offset = 221
[  251.455227@0] FD628: vfd_gpio_clk:           #0 = 0x00; #1 = 0x41; #2 = 0x00;
[  251.455241@0] FD628: vfd_gpio_dat:           #0 = 0x00; #1 = 0x40; #2 = 0x00;
[  251.455249@0] FD628: vfd_gpio_stb:           #0 = 0x00; #1 = 0x42; #2 = 0x00;
[  251.455258@0] FD628: vfd_chars:              #0 = 0x04; #1 = 0x00; #2 = 0x01; #3 = 0x02; #4 = 0x03;
[  251.455269@0] FD628: vfd_dot_bits:           #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
[  251.455277@0] FD628: vfd_display_type:       #0 = 0x02; #1 = 0x00; #2 = 0x01; #3 = 0x00;
[  251.455285@0] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 65, offset = 220
[  251.455291@0] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 64, offset = 219
[  251.455297@0] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 66, offset = 221
[  282.954994@1] FD628: vfd_gpio_clk:           #0 = 0x00; #1 = 0x41; #2 = 0x00;
[  282.955009@1] FD628: vfd_gpio_dat:           #0 = 0x00; #1 = 0x40; #2 = 0x00;
[  282.955017@1] FD628: vfd_gpio_stb:           #0 = 0x00; #1 = 0x42; #2 = 0x00;
[  282.955026@1] FD628: vfd_chars:              #0 = 0x04; #1 = 0x00; #2 = 0x01; #3 = 0x02; #4 = 0x03;
[  282.955037@1] FD628: vfd_dot_bits:           #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
[  282.955045@1] FD628: vfd_display_type:       #0 = 0x02; #1 = 0x00; #2 = 0x01; #3 = 0x00;
[  282.955053@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 65, offset = 220
[  282.955059@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 64, offset = 219
[  282.955065@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 66, offset = 221
[  347.826214@1] FD628: vfd_gpio_clk:           #0 = 0x00; #1 = 0x41; #2 = 0x00;
[  347.826229@1] FD628: vfd_gpio_dat:           #0 = 0x00; #1 = 0x40; #2 = 0x00;
[  347.826237@1] FD628: vfd_gpio_stb:           #0 = 0x00; #1 = 0x42; #2 = 0x00;
[  347.826246@1] FD628: vfd_chars:              #0 = 0x04; #1 = 0x00; #2 = 0x01; #3 = 0x02; #4 = 0x03;
[  347.826257@1] FD628: vfd_dot_bits:           #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
[  347.826265@1] FD628: vfd_display_type:       #0 = 0x02; #1 = 0x00; #2 = 0x01; #3 = 0x00;
[  347.826273@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 65, offset = 220
[  347.826279@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 64, offset = 219
[  347.826286@1] FD628: "banks" chip found.     base = 155, pin count = 101, pin = 66, offset = 221
LibreELEC:~/radni #

Display More

After running "sh test_led.sh" command the display correctly displayed time with no additional icons.

After reboot it first displayes only correct time (no icons), and when Kodi comes up it messes up the display time and lights up almost all icons.

Will try to fix this, but if not, the correct time is what I seek, icons are not needed...

edit: Choosing "Defaults" in Settings for FD628 Display FIXED everything. And all works correct after reboot.

Will try tomorow again with v.8.2.4_OC images.

**The Coolest** · April 3, 2018 at 12:41 AM

Sholander

8.2.4, if you mean the one by adamg, it should already have the driver built in, but anyway, good to see progress.

The icons depend on the kodi add-on. Make sure you disable the advanced settings in the add-on configuration and the display should go back to normal. (if it doesn't, then reboot).

Sholander · April 3, 2018 at 12:45 AM

Already did that, tnx

Used this version "https://libreelec.adamg.co.uk/releases/archi….2-8.2.4.img.gz"

**The Coolest** · April 3, 2018 at 12:52 AM

Yep, I believe that with this version by adamg, you can run sh uninstall.sh followed by systemctl restart fd628 and stick to the built in driver, as it is identical.

Not all devs are in sync on the version of the baked in driver, adamg made sure that his build has the latest one.

**The Coolest** · April 3, 2018 at 11:30 AM

Quote from KeNt606

I have the MXV + S905. Installed Libreelec 8.90.5 clock on the console did not work.

1. MXV+ S905

2. Amlogic_s905/dtb_file/S905/MXV+ at master · 150balbes/Amlogic_s905 · GitHub

3. gxbb_p200_1G_1Gbit_RealtekWiFi

4. FD650B-S 005CYL0002

~~I'm working on adding support for I2C controllers, and need the original DTB from Android to determine which pins the FD650 controller is~~

~~connected to. That way I'll be able to send you test versions when I have something ready.~~

I grabbed the firmware for this box, pulled the DTB from it and got the data I needed from there.

I'll ping you when I have a version to test, though.

JohnBoyz · April 3, 2018 at 11:42 AM

Quote from The Coolest

Sholander

8.2.4, if you mean the one by adamg, it should already have the driver built in, but anyway, good to see progress.

The icons depend on the kodi add-on. Make sure you disable the advanced settings in the add-on configuration and the display should go back to normal. (if it doesn't, then reboot).

I had a completely corrupted display on a Tanix Tx3 and finally found that if I configured FD628 service by changing

"- Select which icon is to be used as the access indicator"

to the power option in my case I got a properly functioning display.

I have forgotten what the default entry was.

Dunno if this might be relevant or not.

Sholander · April 3, 2018 at 12:16 PM

Quote from Sholander

Will try tomorow again with v.8.2.4_OC images.

Tried again with my instalation (not new install) of "LibreELEC-S912.arm-8.2.4-Oclock-GPU.img" updated with

"LibreELEC-S912.arm-8.2.4-S912-Subtitles-fix.tar", same as yesterday's trials.

First uninstalled "service.fd628", deleted driver from .local/share and "vfd.conf" from .config -> rebboted.

Then copied and renamed x92-vfd.conf to .config and run your "install.sh" from unpacked "FD628 Display.zip"

It finished with "something" = 1 and BUM -> corect time was displayed! Finaly SUCCESS.

Did not install service.fd628, because clock display is all I realy need.

Just don't know what was going wrog yesterday. I know how silly and frustrating it feels when you know for sure that something works, but it does not work for a person you are trying to help.

So THANK YOU VERY MUCH for staying with me at times of lost faith, CHEERS

Sholander · April 3, 2018 at 12:20 PM

Quote from The Coolest

Yep, I believe that with this version by adamg, you can run sh uninstall.sh followed by systemctl restart fd628 and stick to the built in driver, as it is identical.

It did not work until I run through your installing procedures.

Anyhow, that was just a test version that I don't intend to use.

Tim_Taylor · April 3, 2018 at 12:32 PM

Quote from Sholander

Just don't know what was going wrog yesterday.

Maybe wrong sequence and misunderstanding.

Without the vfd.conf corresponding to Your hardware the installation will fail.

Sholander · April 3, 2018 at 1:41 PM

Thinking back through the steps I did yesterday, yes "vfd.conf" is probably the reason. Not the file itself, but my stupidity; I think that yesterdy I copied the file to wrong folder, not like today to correct -> /storage/.config/

**The Coolest** · April 3, 2018 at 4:55 PM

Quote from JohnBoyz

I had a completely corrupted display on a Tanix Tx3 and finally found that if I configured FD628 service by changing

"- Select which icon is to be used as the access indicator"

to the power option in my case I got a properly functioning display.

I have forgotten what the default entry was.

Dunno if this might be relevant or not.

I just tried to reproduce this, but failed. It's much more likely that one of the advanced display options was the one that caused the problem.

The access indicator lets you chose an icon to be used as a rudimentary "HDD" led, to show you when the box reads from/writes to its storage.

**The Coolest** · April 4, 2018 at 11:42 PM

I'm looking for someone with the following boxes: "MXV+ S905" / "M9 Pro" / "CSA93" to test whether the driver will work with i2c based display drivers. Please reply or PM me if you have one of these and can help with testing.

Support was added for the FD650 (actually for TM1650) and for the HBS658 chips.

darioml · April 9, 2018 at 9:16 PM

Hi!

I am just using the vorke-z6-vfd.conf (renamed as vfd.conf) with 8.90.6 and CoreELEC, but just only the clock works. No other symbol (ethernet, play, pause appears... LibreELEC 8.90.5 and before worked perfectly.

What could be the reason?

Thanks!

**The Coolest** · April 9, 2018 at 9:17 PM

darioml

Make sure that you install the FD628 Service addon in Kodi.

LED (VFD) Displays in LibreELEC

Similar Threads

S802/S812-Libreelec images for 7/8/9

Tanix TX3 Mini with Amlogic S905W CPU - Libreelec

[8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices