VFD configuration

[tex1988]

Hi, devmfc and the community,
I appreciate your amazing work
I have one question. I am using Vontar X4 gigabit with your image and noticed that the VFD screen works but displays something incomprehensible. Can we configure it like on Armbian with openvfd or is there any way to use openvfd instead of the builtin vfd service?
For now on my Vontar X4 I am getting such messages in dmesg

tvbox:~#dmesg | grep fd6551
[    0.203533] tm16xx fd6551: DEVMFC: tm16xx driver v1.96 probe
[    0.203637] tm16xx fd6551: Get stb GPIO failed: -2, assuming two wire protocol

Added: this error doesn't affect anything but segment-mapping is wrong in meson-sc2-vontarx4-gbit.dtb and I can't figure out how to define the correct.
If it will be helpful here is the original android dts file
single.dts.zip

Thank you in advance

[devmfc]

Only the mapping is wrong.
You could try to figure the right mapping, see /usr/lib/tm16xx-display/tm16xx-map.sh for some examples.

Original DTB will not be very helpful.

If you find the right mapping, please let me know, then I will fix the DTB for the next release.

Of course you can also disable my driver by removing the fd6551 node from the DTB.

[tex1988]

Unfortunately, I can't manage to find the right mapping so I removed fd6551 from dtb and moved to openvfd driver

[Machete2048]

Hello there,

First things first: many thanks for the nice work on providing such images for these boxes.

i came up here while looking for some informations for this tm16xx display (i own a Vontar-X4 Gigabit too),
and after playing around, here is the setting that worked for me :

• change the following line in file /usr/lib/tm16xx-display/tm16xx-map.sh :

echo ${map6[@]} > $dev_path/mapping

with:

echo ${map2[@]} > $dev_path/mapping

• OPTIONAL: you can uncomment the tests and the end of the file.
• chmod +x /usr/lib/tm16xx-display/tm16xx-map.sh
• execute /usr/lib/tm16xx-display/tm16xx-map.sh (to initiliaze mapping)

Cheers,