Help wanted to test a new OpenVFD alternative

[Jean-Francois Lessard]

That should make it. You can always try to see if it works and search online if not.

[dale]

Quote

sudo ./display -c
[WARN] Display device directory missing at /sys/class/leds/display; attempting module load
[INFO] Successfully loaded module: tm16xx
[ERROR] Display device not present after modprobe

Hi, @Jean-Francois Lessard I'm using a x98h box with self-built image. I have issue with the tm16xx kernel module using a patch https://github.com/paolosabatino/armbian-build/blob/main/patch/kernel/archive/rockchip64-6.16/general-driver-tm16xx-led-driver.patch

The vfd controller is AIP1688 which is similar to fd628. Do you have any idea why it fails?

 

Edited 3 hours ago by dale

[Jean-Francois Lessard]

Hi @dale

 

What is your DTS node for your display? My first guess is that your DT node is not being picked up/inexistent since the module loads but the display device is not present.

You can use dtc /proc/device-tree to see your loaded DT and find your display node, if any.

 

Then, have you checked dmesg for any tm16xx kernel message?

 

Then, you can ls /sys/class/leds to see if any device were created. The display-service/display-utils scripts expect /sys/class/leds/display.

 

That should not be your issue here, but I'm not sure that aip1688 is the same as tm1628 variants. Googling aip1688 list it besides aip1618, so that would be the tm1618 variant. Whatsoever, I think you should have partial working display if using tm1628. To be 100% of which compatible string to use, we would need the aip1688 datasheet but I couldn't find it online.

 

Good luck with your experimentation! Let me know how you results.