This is *ELEC basics, LE creates a few shared folders, one of them is `downloads` and it's normally stored in /storage, together with a lot of other folders.
Linux is case sensitive, so make sure you don't use caps when you type in commands.
Try to run these commands and post the URL you get in return.
To extract the DTB, you have to run the command when you are in LE.
A T95m works great, it should also have a better processor, S905X.
Because it's probably a better idea to try it for yourself and see if it works well for your needs, than to wait for someone to "kindly" give you an answer whether it works or not.
It's also very likely to take a lot less time than to wait for someone to reply.
And in addition, LibreELEC 8.0.2 is ancient, and you should install something newer.
We should probably take this to PM, as there's no point in cluttering the forum with our dialogue
I suggest you disable the Kodi openvfd service for testing purposes.
SSH into the box, kill the OpenVFDService process.
Then start it again like so:
This will run the service in demo mode, and should look something like this:
If you could take a video of what happens on screen, it would be great.
OK, now there's some progress.
Looks like there is now a conflict with pins allocation. I'll look into it later today if I have time or tomorrow.
This will probably require a dedicated DTB for this box.
vvd214 What does
produce? It's highly unlikely that it's trying to read the vfd.conf from somewhere else.
The Kodi service can't affect the dmesg output from openvfd module, what you see there is what is read from vfd.conf. And currently what I'm seeing is that you're using the vfd.conf file narcotic posted.
- [ [email protected]] OpenVFD: vfd_gpio_clk: #0 = 0x00; #1 = 0x44; #2 = 0x00;
- [ [email protected]] OpenVFD: vfd_gpio_dat: #0 = 0x00; #1 = 0x43; #2 = 0x00;
- [ [email protected]] OpenVFD: vfd_gpio_stb: #0 = 0x00; #1 = 0x45; #2 = 0x00;
- [ [email protected]] OpenVFD: vfd_chars: #0 = 0x04; #1 = 0x03; #2 = 0x02; #3 = 0x01; #4 = 0x00;
- [ [email protected]] OpenVFD: vfd_dot_bits: #0 = 0x00; #1 = 0x01; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x05; #6 = 0x06;
- [ [email protected]] OpenVFD: vfd_display_type: #0 = 0x01; #1 = 0x00; #2 = 0x00; #3 = 0x00;
- [ [email protected]] OpenVFD: "banks" chip found. base = 155, pin count = 101, pin = 68, offset = 223
- [ [email protected]] OpenVFD: "banks" chip found. base = 155, pin count = 101, pin = 67, offset = 222
- [ [email protected]] OpenVFD: "banks" chip found. base = 155, pin count = 101, pin = 69, offset = 224
- [ [email protected]] OpenVFD: Select FD628* controller
- [ [email protected]] OpenVFD: SPI 3-wire interface intialized
You're not using the vfd I attached in this post...
Make sure that you put it into Configfiles folder, and rename it to 'vfd.conf'
I re-install Coreelec 8.95 (with dtb: gxl_p212_2g.dtb) and OpenVFD services, but sill black display
Here is my Android _DTB
dmesg - http://ix.io/1jmg
systemctl status openvfd - http://ix.io/1jmj
Please, have a look. Thanks
Thanks. Try the attached vfd.conf.
I don't know what version of the vfd driver wrxtasy uses in 18.104.22.168, but in 22.214.171.124 he wasn't using the driver I adapted, so it won't work at all without a per-box DTB configuration.
Also, the dtb file you posted is empty, you may have to extract it from Android directly.
Try running the following commands and post the URLs.
Have a look at the LE openVFD Addon configurations. There is all sorts of stuff to adjust.
I think he's saying that the display is stuck at "boot", which normally means the vfd driver has not been started or the wrong vfd.conf was used.