watou

@dfahren Thanks for your reply. I believe my issue is that I cannot locate the steps to integrate your DTS snippet above into my system. The tm16xx driver does load but generates no lines in dmesg, probably because it's not referenced in the device tree? Do you have the steps to add what is needed into my device tree? Many thanks!

@dfahren Thanks for your efforts and reports on getting the tm16xx driver working on the H96 Max V56 TV box. I'm looking forward to your pull request for the Armbian build, but also wondering if you have step-by-step instructions for integrating the correct DTS, since the tm16xx-display README does not address boxes that are not in the Device Table. On my 4GB box I'm running the kernel `6.12.11-current-rockchip64` and `modprobe tm16xx` does load the driver but without knowing how to work with this specific box.

@Hqnicolas many thanks! Can't find any files at the noble-server links at the moment; will look again later. My 4GB/32GB is going to be a headless home automation server, so stability, solid USB and Ethernet and security updates are my top items. Thanks for your contributions!

I was able to do exactly that with hqnicolas's 1.1 instructions and the .img he shared yesterday on Google Drive. I then attempted the openvfd with the results above. Thanks for any LED light you can shed....

@Hqnicolas I'm very happy to have booted and now running the latest Armbian trunk on my H96 Max V56 4GB/32GB! But I'm not having success using openvfd to get the time to display on the box's face. I only get the blue backlight and red LED heartbeat. I found your post here and a link to your github repo here. I followed the instructions, referring to my current kernel 6.6.45, but the instruction I understood the least was Step 3: 3. Update dts using armbian-config openvfd { compatible = "open,vfd"; dev_name = "openvfd"; status = "okay"; }; I interpreted that to mean sudo armbian-config, choose System, Dtc, and find some place to paste the above, save and exit, choose y to apply the changes, which produces a long set of warning messages like the following. ... /tmp/tmp.zItxtnh4vV/current.dts:4892.4-29: Warning (gpios_property): /gpio-keys-control/button-r1:gpios: cell 0 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:4898.4-29: Warning (gpios_property): /gpio-keys-control/button-r2:gpios: cell 0 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:4912.4-29: Warning (gpios_property): /gpio-keys-vol/button-vol-down:gpios: cell 0 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:4918.4-29: Warning (gpios_property): /gpio-keys-vol/button-vol-up:gpios: cell 0 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:4926.3-47: Warning (gpios_property): /mux-controller:mux-gpios: cell 0 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:4926.3-47: Warning (gpios_property): /mux-controller:mux-gpios: cell 3 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:4983.3-34: Warning (gpios_property): /sdio-pwrseq:reset-gpios: cell 0 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:4989.3-27: Warning (gpios_property): /regulator-vcc3v3-lcd0:gpio: cell 0 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:5018.3-27: Warning (gpios_property): /regulator-vcc-wifi:gpio: cell 0 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:5062.3-52: Warning (gpios_property): /sound:simple-audio-card,hp-det-gpio: cell 0 is not a phandle reference /tmp/tmp.zItxtnh4vV/current.dts:5079.3-35: Warning (gpios_property): /audio-amplifier:enable-gpios: cell 0 is not a phandle reference Do you want to replace active dtb with current modification(s)? (y/n)y On reboot, there is no /proc/device-tree/openvfd so I assume I edited the device tree incorrectly? Aug 12 23:20:14 h96 systemd[1]: openvfd.service - OpenVFD Service was skipped because of an unmet condition check (ConditionPathExists=/proc/device-tree/openvfd). Any pointers on how to complete these changes so the clock appears would be very much appreciated. Cheers! watou

@Tressie, I'll post my results here when I can. I hope you can find a way out. Any chance of trying a different USB cable?

There's a link to the 8Gb mini loaded binary in this post linked below, and just use the latest official image for your TV box, like this one. Remember to uncompress the .xz image file before writing it, as I'm not sure the rk tools will do that for you. I've not done any of this yet, and I'm in a remote place trying to source a heckin' USB A to A cable!