How to configure VFD

General Guides & How-tos
1108

What I am observing is the following.

systemctl status openvfd.service

× openvfd.service - OpenVFD Service
Loaded: loaded (/usr/lib/systemd/system/openvfd.service; disabled; preset:
Active: failed (Result: exit-code) since Thu 2023-02-16 23:40:59 IST; 1min
Duration: 366ms
Process: 3330 ExecStart=/usr/lib/coreelec/openvfd-start (code=exited, status
Process: 3388 ExecStopPost=/usr/sbin/rmmod openvfd (code=exited, status=0/SU
Main PID: 3330 (code=exited, status=1/FAILURE)

 cat /sys/kernel/debug/gpio

CoreELEC:~ # cat /sys/kernel/debug/gpio
gpiochip1: GPIOs 410-495, parent: platform/pinctrl@ff634480, periphs-banks:
 gpio-448 (                    |amlsd               ) out hi
 gpio-458 (                    |amlsd               ) in  lo
 gpio-482 (                    |sdio_wifi           ) out hi
 gpio-483 (                    |sdio_wifi           ) in  hi
 gpio-493 (                    |bt_rfkill           ) out hi
 gpio-495 (                    |bt_rfkill           ) out hi

gpiochip0: GPIOs 496-511, parent: platform/pinctrl@ff800014, aobus-banks:
 gpio-498 (                    |avout_mute          ) out hi
 gpio-499 (                    |key                 ) in  hi
 gpio-507 (                    |?                   ) out lo

The vfd.conf file updated with vfd_gpio_dat=‘1,10,0x10’ and any value other than vfd_gpio_clk=‘1,11,0x10’ keep the openvfd service in running status. If these values are interchanged or modified then openvfd service fails.

Example: Below given keep the openvfd service in running status however the values are showing as in hi and in lo instead of out hi which is expected behaviour to keep the VFD on. I am unable to update the vfd.conf with the value 11. If I do that then the service is failing.

vfd_gpio_clk='1,12,0x10'
vfd_gpio_dat='1,10,0x10'
vfd_gpio_stb='0,0,0xFF'


 openvfd.service - OpenVFD Service
     Loaded: loaded (/usr/lib/systemd/system/openvfd.service; disabled; preset:
     Active: active (running) since Thu 2023-02-16 23:44:57 IST; 3min 40s ago
   Main PID: 4122 (openvfd-start)
      Tasks: 4 (limit: 3724)
     Memory: 1.0M
     CGroup: /system.slice/openvfd.service
             ├─4122 /bin/sh /usr/lib/coreelec/openvfd-start
             └─4137 /usr/sbin/OpenVFDService -s CE20

Feb 16 23:44:57 CoreELEC systemd[1]: Started openvfd.service.


CoreELEC:~ # cat /sys/kernel/debug/gpio
gpiochip1: GPIOs 410-495, parent: platform/pinctrl@ff634480, periphs-banks:
 gpio-448 (                    |amlsd               ) out hi
 gpio-458 (                    |amlsd               ) in  lo
 gpio-482 (                    |sdio_wifi           ) out hi
 gpio-483 (                    |sdio_wifi           ) in  hi
 gpio-493 (                    |bt_rfkill           ) out hi
 gpio-495 (                    |bt_rfkill           ) out hi

gpiochip0: GPIOs 496-511, parent: platform/pinctrl@ff800014, aobus-banks:
 gpio-498 (                    |avout_mute          ) out hi
 gpio-499 (                    |key                 ) in  hi
 gpio-506 (                    |openvfd             ) in  hi
 gpio-507 (                    |?                   ) out lo
 gpio-508 (                    |openvfd             ) in  lo
1109

I looked at the dmesg you posted again and when you created it you were not using the trident vfd.conf.

Set the vfd.conf to the values to the original trident config. Then reboot, and then generate the dmesg file.

1110

Original vfd.conf (trident):

This file must be renamed to vfd.conf and placed in the /storage/.config/ folder.

Trident T527 (S905X3) configuration

#--------------------
#gpio_xxx:

[0] 0 = &gpio, 1 = &gpio_ao.

[1] pin number - https://github.com/openSUSE/kernel/blob/master/include/dt-bindings/gpio/meson-g12a-gp>

[0] Reserved - must be 0.

vfd_gpio_clk=‘1,11,0’
vfd_gpio_dat=‘1,10,0’
vfd_gpio_stb=‘0,0,0xFF’

#chars:

< DHHMM > Order of display chars (D=dots, represented by a single char)

vfd_chars=‘4,3,2,1,0’

#dot_bits:

Order of dot bits. Typical configurations:

Display Type 0, 1 usually has Alarm, USB, Play, Pause, Col, Ethernet, Wifi dots

Alarm = 0, USB = 1, Play = 2, Pause = 3, Col = 4, Eth = 5, Wifi = 6

Display Type 2 usually has APPS, USB, SETUP, CARD, Col, HDMI, CVBS dots

APPS = 0, USB = 1, SETUP = 2, CARD = 3, Col = 4, HDMI = 5, CVBS = 6

Display Type 3 Power, LAN, Col, Low Wifi, High Wifi

N/A = 0, N/A = 1, Power = 2, LAN = 3, Col = 4, Low Wifi = 5, High Wifi = 6

vfd_dot_bits=‘5,6,2,3,4,0,1’

#display_type:

[0] - Display type.

[1] - Reserved - must be 0..

[2] - Flags. (bit 0 = ‘1’ - Common Anode display)

[3] - Controller.

vfd_display_type=‘0x01,0x00,0x00,0x06’

systemctl status openvfd.service

× openvfd.service - OpenVFD Service
Loaded: loaded (/usr/lib/systemd/system/openvfd.service; disabled; preset:
Active: failed (Result: exit-code) since Tue 2024-02-27 22:56:08 IST; 3min
Duration: 646ms
Process: 3478 ExecStart=/usr/lib/coreelec/openvfd-start (code=exited, status
Process: 3585 ExecStopPost=/usr/sbin/rmmod openvfd (code=exited, status=0/SU
Main PID: 3478 (code=exited, status=1/FAILURE)

Feb 27 22:56:07 s905x3anbx systemd[1]: Started openvfd.service.
Feb 27 22:56:07 s905x3anbx openvfd-start[3559]: Open device failed.
Feb 27 22:56:07 s905x3anbx openvfd-start[3559]: : No such file or directory
Feb 27 22:56:07 s905x3anbx systemd[1]: openvfd.service: Main process exited, cod
Feb 27 22:56:08 s905x3anbx systemd[1]: openvfd.service: Failed with result 'exit

dmesg:

dmesg.log (72.1 KB)

1111

Use systemctl status openvfd.service --no-pager

After service is started check for any errors with journalctl -l --no-pager

1112

I could find below given wrt to openvfd. I am attaching the complete log as well here.

journal.log (126.5 KB)

s905x3anbx:~ # systemctl status openvfd.service --no-pager
× openvfd.service - OpenVFD Service
Loaded: loaded (/usr/lib/systemd/system/openvfd.service; disabled; preset: disabled)
Active: failed (Result: exit-code) since Tue 2024-02-27 22:56:07 IST; 48s ago
Duration: 650ms
Process: 3466 ExecStart=/usr/lib/coreelec/openvfd-start (code=exited, status=1/FAILURE)
Process: 3571 ExecStopPost=/usr/sbin/rmmod openvfd (code=exited, status=0/SUCCESS)
Main PID: 3466 (code=exited, status=1/FAILURE)

Feb 27 22:56:07 s905x3anbx systemd[1]: Started openvfd.service.
Feb 27 22:56:07 s905x3anbx openvfd-start[3557]: Open device failed.
Feb 27 22:56:07 s905x3anbx openvfd-start[3557]: : No such file or directory
Feb 27 22:56:07 s905x3anbx systemd[1]: openvfd.service: Main process exited, code=exited, status=1/FAILURE
Feb 27 22:56:07 s905x3anbx systemd[1]: openvfd.service: Failed with result ‘exit-code’.

journalctl -l --no-pager

Feb 27 22:56:07 s905x3anbx (udev-worker)[3429]: event1: Process ‘/usr/bin/evrepeat -d 500 /dev/input/event1’ failed with exit code 1.
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: Version: V1.4.4
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_gpio_clk: #0 = 0x01; #1 = 0x0B; #2 = 0x00;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_gpio_dat: #0 = 0x01; #1 = 0x0A; #2 = 0x00;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_gpio_stb: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_chars: #0 = 0x04; #1 = 0x03; #2 = 0x02; #3 = 0x01; #4 = 0x00;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_dot_bits: #0 = 0x05; #1 = 0x06; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x00; #6 = 0x01;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: vfd_display_type: #0 = 0x01; #1 = 0x00; #2 = 0x00; #3 = 0x06;
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: Detected gpio chips: periphs-banks, aobus-banks.
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: “aobus-banks” chip found. base = 496, pin count = 16, pin = 11, offset = 507
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: “aobus-banks” chip found. base = 496, pin count = 16, pin = 10, offset = 506
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio_stb evaluation (0xFF)
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio0 evaluation (0xFF)
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio1 evaluation (0xFF)
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio2 evaluation (0xFF)
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio3 evaluation (0xFF)
Feb 27 22:56:07 s905x3anbx kernel: OpenVFD: can’t request gpio of gpio_clk
Feb 27 22:56:07 s905x3anbx kernel: openvfd: probe of openvfd failed with error -22
Feb 27 22:56:07 s905x3anbx (udev-worker)[3486]: event3: Process ‘/usr/bin/evrepeat -d 500 /dev/input/event3’ failed with exit code 1.
Feb 27 22:56:07 s905x3anbx dbus-daemon[3451]: [system] Activating via systemd: service name=‘org.bluez’ unit=‘dbus-org.bluez.service’ requested by ‘:1.2’ (uid=0 pid=3469 comm=“/usr/bin/pulseaudio --system --disallow-exit --exi” label=“kernel”)
Feb 27 22:56:07 s905x3anbx dovi-loader[3532]: run dovi ‘start’ for ng
Feb 27 22:56:07 s905x3anbx (udev-worker)[3441]: event6: Process ‘/usr/bin/evrepeat -d 500 /dev/input/event6’ failed with exit code 1.
Feb 27 22:56:07 s905x3anbx kernel: EXT4-fs (mmcblk0p16): mounted filesystem without journal. Opts: (null)
Feb 27 22:56:07 s905x3anbx openvfd-start[3557]: Open device failed.
Feb 27 22:56:07 s905x3anbx openvfd-start[3557]: : No such file or directory
Feb 27 22:56:07 s905x3anbx (udev-worker)[3486]: controlC0: /usr/lib/udev/rules.d/90-alsa-restore.rules:5 Only network interfaces can be renamed, ignoring NAME=“snd/%k”.
Feb 27 22:56:07 s905x3anbx systemd[1]: openvfd.service: Main process exited, code=exited, status=1/FAILURE

1113

This doesn’t seem right.

1114

For testing purpose I have changed the value as below.

vfd_gpio_clk=‘1,4,0’
vfd_gpio_dat=‘1,10,0’
vfd_gpio_stb=‘0,0,0xFF’

systemctl status openvfd

● openvfd.service - OpenVFD Service
Loaded: loaded (/usr/lib/systemd/system/openvfd.service; disabled; preset: disabled)
Active: active (running) since Tue 2024-02-27 23:08:04 IST; 1min 35s ago
Main PID: 4446 (openvfd-start)
Tasks: 4 (limit: 3724)
Memory: 1.1M ()
CGroup: /system.slice/openvfd.service
├─4446 /bin/sh /usr/lib/coreelec/openvfd-start
└─4463 /usr/sbin/OpenVFDService -s CE21

Feb 27 23:08:04 s905x3anbx systemd[1]: Started openvfd.service.

systemctl status openvfd.service --no-pager

s905x3anbx:~/.config # systemctl status openvfd.service --no-pager
● openvfd.service - OpenVFD Service
Loaded: loaded (/usr/lib/systemd/system/openvfd.service; disabled; preset: disabled)
Active: active (running) since Tue 2024-02-27 23:08:04 IST; 1min 58s ago
Main PID: 4446 (openvfd-start)
Tasks: 4 (limit: 3724)
Memory: 1.1M ()
CGroup: /system.slice/openvfd.service
├─4446 /bin/sh /usr/lib/coreelec/openvfd-start
└─4463 /usr/sbin/OpenVFDService -s CE21

Feb 27 23:08:04 s905x3anbx systemd[1]: Started openvfd.service.

journalctl -l --no-pager Full log at

journal_1.log (153.1 KB)

Feb 27 23:07:46 s905x3anbx connmand[3759]: Skipping server 162.159.200.1 KoD code RATE
Feb 27 23:07:57 s905x3anbx connmand[3759]: Skipping server 192.168.66.1 KoD code RATE
Feb 27 23:08:04 s905x3anbx systemd[1]: Started openvfd.service.
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: Version: V1.4.4
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_gpio_clk: #0 = 0x01; #1 = 0x04; #2 = 0x00;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_gpio_dat: #0 = 0x01; #1 = 0x0A; #2 = 0x00;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_gpio_stb: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_gpio0: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_gpio1: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_gpio2: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_gpio3: #0 = 0x00; #1 = 0x00; #2 = 0xFF;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_gpio_protocol: #0 = 0x00; #1 = 0x00;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_chars: #0 = 0x04; #1 = 0x03; #2 = 0x02; #3 = 0x01; #4 = 0x00;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_dot_bits: #0 = 0x05; #1 = 0x06; #2 = 0x02; #3 = 0x03; #4 = 0x04; #5 = 0x00; #6 = 0x01;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: vfd_display_type: #0 = 0x00; #1 = 0x00; #2 = 0x00; #3 = 0x06;
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: Detected gpio chips: periphs-banks, aobus-banks.
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: “aobus-banks” chip found. base = 496, pin count = 16, pin = 4, offset = 500
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: “aobus-banks” chip found. base = 496, pin count = 16, pin = 10, offset = 506
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio_stb evaluation (0xFF)
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio0 evaluation (0xFF)
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio1 evaluation (0xFF)
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio2 evaluation (0xFF)
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: Skipping vfd_gpio3 evaluation (0xFF)
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: Select FD6551 controller
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: SW I2C interface intialized (address = 0x0000 (N/A), MSB mode, pull-ups off)
Feb 27 23:08:04 s905x3anbx kernel: OpenVFD: Select FD6551 controller

1115

Also vfd_display_type=‘0x00,0x00,0x00,0x06’. Post which the service got started and provided the logs above. I am not sure this is is the correct value or not.

1116

I have just changed as given below.

vfd_gpio_clk=‘1,12,0’
vfd_gpio_dat=‘1,10,0’
vfd_gpio_stb=‘0,0,0xFF’
vfd_display_type=‘0x01,0x00,0x00,0x06’

● openvfd.service - OpenVFD Service
Loaded: loaded (/usr/lib/systemd/system/openvfd.service; disabled; preset: disabled)
Active: active (running) since Tue 2024-02-27 22:56:07 IST; 2 years 2 months ago
Main PID: 3472 (openvfd-start)
Tasks: 4 (limit: 3724)
Memory: 1.8M ()
CGroup: /system.slice/openvfd.service
├─3472 /bin/sh /usr/lib/coreelec/openvfd-start
└─3557 /usr/sbin/OpenVFDService -s CE21

Feb 27 22:56:07 s905x3anbx systemd[1]: Started openvfd.service.

s905x3anbx:~ # cat /sys/kernel/debug/gpio
gpiochip1: GPIOs 410-495, parent: platform/pinctrl@ff634480, periphs-banks:
gpio-448 (                    |amlsd               ) out hi
gpio-458 (                    |amlsd               ) in  lo
gpio-482 (                    |sdio_wifi           ) out hi
gpio-483 (                    |sdio_wifi           ) in  hi
gpio-493 (                    |bt_rfkill           ) out hi
gpio-495 (                    |bt_rfkill           ) out hi

gpiochip0: GPIOs 496-511, parent: platform/pinctrl@ff800014, aobus-banks:
gpio-498 (                    |avout_mute          ) out hi
gpio-499 (                    |key                 ) in  hi
gpio-506 (                    |openvfd             ) in  hi
gpio-507 (                    |?                   ) out lo
gpio-508 (                    |openvfd             ) in  lo

s905x3anbx:~/.config # systemctl status openvfd.service --no-pager
● openvfd.service - OpenVFD Service
Loaded: loaded (/usr/lib/systemd/system/openvfd.service; disabled; preset: disabled)
Active: active (running) since Tue 2024-02-27 22:56:07 IST; 2 years 2 months ago
Main PID: 3472 (openvfd-start)
Tasks: 4 (limit: 3724)
Memory: 1.8M ()
CGroup: /system.slice/openvfd.service
├─3472 /bin/sh /usr/lib/coreelec/openvfd-start
└─3557 /usr/sbin/OpenVFDService -s CE21

I am finding the openvfd value is showing as “in hi” for gpio-506 where this was appearing as “out hi” in android. If we set ‘1,11,0’ for gpio-507 then openvfd service is not starting.

Editing this post since I can’t post more than 3 in a row

vfd_gpio_clk=‘1,11,0’
vfd_gpio_dat=‘1,10,0’
vfd_gpio_stb=‘0,0,0xFF’

I have referred to this post and updated the flash value with above in vfd.conf.

Now the gpio showing correct entries but the values are “in hi”.

s905x3anbx:~ # cat /sys/kernel/debug/gpio
gpiochip1: GPIOs 410-495, parent: platform/pinctrl@ff634480, periphs-banks:
gpio-448 ( |amlsd ) out hi
gpio-458 ( |amlsd ) in lo
gpio-482 ( |sdio_wifi ) out hi
gpio-483 ( |sdio_wifi ) in hi
gpio-493 ( |bt_rfkill ) out hi
gpio-495 ( |bt_rfkill ) out hi

gpiochip0: GPIOs 496-511, parent: platform/pinctrl@ff800014, aobus-banks:
gpio-498 ( |avout_mute ) out hi
gpio-499 ( |key ) in hi
gpio-506 ( |openvfd ) in hi
gpio-507 ( |openvfd ) in hi

1117

@vpeter

[ 10.874965@1]- OpenVFD: can’t request gpio of gpio_clk
[ 10.874977@1]- openvfd: probe of openvfd failed with error -22

Something in the DTB is taking up pin 11. That’s why it’s not working.
I will look later tonight.

1118

Try the instructions in this post and let me know what it does.

1119

Thanks for looking into this. I am pasting the commands ran and the outcome

s905x3anbx:~ # mount -o remount,rw /flash/
s905x3anbx:~ # fdtput -r /flash/dtb.img /gpioleds/sys_led
Error at '/gpioleds/sys_led': FDT_ERR_NOTFOUND
s905x3anbx:~ # sunc
-sh: sunc: command not found
s905x3anbx:~ # sync
s905x3anbx:~ # mount -o remount,ro /flash
s905x3anbx:~ # reboot

Post reboot status. VFD is still not working.

s905x3anbx:~ # cat /sys/kernel/debug/gpio
gpiochip1: GPIOs 410-495, parent: platform/pinctrl@ff634480, periphs-banks:
gpio-448 (                    |amlsd               ) out hi
gpio-458 (                    |amlsd               ) in  lo
gpio-482 (                    |sdio_wifi           ) out hi
gpio-483 (                    |sdio_wifi           ) in  hi
gpio-493 (                    |bt_rfkill           ) out hi
gpio-495 (                    |bt_rfkill           ) out hi

gpiochip0: GPIOs 496-511, parent: platform/pinctrl@ff800014, aobus-banks:
gpio-498 (                    |avout_mute          ) out hi
gpio-499 (                    |key                 ) in  hi
gpio-506 (                    |openvfd             ) in  hi
gpio-507 (                    |openvfd             ) in  hi
s905x3anbx:~ #
1120

Please post the dtb.img file you are using.

1121

Please find the image I am using.

sm1_s905x3_4g.dtb (71.6 KB)

1122

I meant the dtb.img file itself, on your box. Because the command to remove sys_led works fine on the file you attached.

1123

I am sorry I have copied the wrong one. Please find the dtb.img from the Android for this box.

dtb.img.gz (255.4 KB)

1124

Again, I mean the dtb.img you have in your /flash folder in CoreELEC.

1125

Please find the dtb image from CE /flash.

dtb.img (71.5 KB)

.

1126

OK, the dtb section that was causing the conflict seems to be gone.
Try with the trident vfd.conf again, reboot and post dmesg if the display still doesn’t turn on at all.

1127

Tried with trident vfd.conf again, rebooted and tested. Still there is no display. Are the “in hi” values ok for gpio-506 and gpio-507? Do I have to modify any bits to make it high?

vfd_gpio_clk=‘1,11,0’
vfd_gpio_dat=‘1,10,0’
vfd_gpio_stb=‘0,0,0xFF’
vfd_chars=‘4,3,2,1,0’
vfd_dot_bits=‘5,6,2,3,4,0,1’
vfd_display_type=‘0x01,0x00,0x00,0x06’

s905x3anbx:~ # cat /sys/kernel/debug/gpio
gpiochip1: GPIOs 410-495, parent: platform/pinctrl@ff634480, periphs-banks:
gpio-448 (                    |amlsd               ) out hi
gpio-458 (                    |amlsd               ) in  lo
gpio-482 (                    |sdio_wifi           ) out hi
gpio-483 (                    |sdio_wifi           ) in  hi
gpio-493 (                    |bt_rfkill           ) out hi
gpio-495 (                    |bt_rfkill           ) out hi

gpiochip0: GPIOs 496-511, parent: platform/pinctrl@ff800014, aobus-banks:
gpio-498 (                    |avout_mute          ) out hi
gpio-499 (                    |key                 ) in  hi
gpio-506 (                    |openvfd             ) in  hi
gpio-507 (                    |openvfd             ) in  hi

I am attaching the updated dmesg here.

dmesg_v1.log (73.8 KB)