VFD on X96 Max

I found this in a Hungarian forum, you can try this too:
https://www.mediafire.com/file/yubqefgy2kl0q6s/x96max_vfd.zip/file

I will try it, but I do not hold out much hope because without any VFD I expect to see “boot” in the display, but it is completely dead … no segment lit at any time during CE use.
The display functions normally when Android is in use.

I also have the 2g/16g X96max and on trying to follow the instructions at post 27 I get:

X96:~ # mount -o remount,rw /flash
X96:~ # fdtput -r /flash/dtb.img /gpioleds/net_red
Error at ‘/gpioleds/net_red’: FDT_ERR_NOTFOUND
X96:~ # fdtput -r /flash/dtb.img /gpioleds/net_red
Error at ‘/gpioleds/net_red’: FDT_ERR_NOTFOUND
X96:~ # fdtput -r /flash/dtb.img /gpioleds/net_green
Error at ‘/gpioleds/net_green’: FDT_ERR_NOTFOUND
X96:~ # fdtput -r /flash/dtb.img /gpioleds/remote_led
Error at ‘/gpioleds/remote_led’: FDT_ERR_NOTFOUND

No lights at all on front after reboot.

Give us an output from Android for
cat /sys/kernel/debug/gpio

X96:~ # cat /sys/kernel/debug/gpio | paste
http://ix.io/1Q8T
X96:~ #

Are you sure that it’s from Android?

That’s CE, I don’t think Android has paste and you can’t SSH into Android easily.
Also, Android doesn’t use openvfd :slight_smile:

1 Like

X96 MAX V311R_P no BT of 9.2。
Android 9: x96Max_311R_P_ Q5X2_LP3 19215 wifi: Fn-Link 6222B-SRB RAM: DDR3 :
img :https://mega.nz/#!PpR3wAYT!cwZTe0bfa7QNJlQJFyiDG1vJDmt9g7YFBLpVA9wYBtw

Yes the log was from CE.
Did it not show anything useful?
Is it possible that the dtb file for 905x2/2g doesnt contain the needed info to flash?

Has there been any resolution for this blank display issue on the X96Max box? I have the most recent development build on the box and front display is blank whether booting or in operation.

Not for the 2GB RAM version.

The box I have is the 4GB ram version running Android 9. I found nothing via search on how to fix this.

1 Like

Thanks for this. Display is working. I wasn’t aware of the term “VFD”, so wasn’t able to search it properly.

@TheCoolest Did you already fix for the 2GB RAM version?

No. You can try running the cat /sys/kernel/debug/gpio command in Android and post a screenshot of the output here. But from previous attempts, there was no info about VFD in that output.

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

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

Unfortunately it’s the same as before, no data about the 2nd VFD pin, basically making it impossible for us to add support for it.

@TheCoolest Could you please tell me the pins you discover up to now from the results of cat /sys/kernel/debug/gpio ?

gpio-424 ( |vdftest ) out lo

That’s pin 14 (424 - 410 base)
And you need 2 or 3 pins, depending on the type of controller.
It also doesn’t say which it is (stb, clk, dat)