dale

I gave this a try but no success. The structure of original source code doesn't match the one for armbian. It would be great if you could make a patch as in this link

Can you make a patch for armbian? It will be easy for us to try.

Hi, I finally got my display to work with below DT overlay source. My device is x98h. Thank you! /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = <&pio 2 7 GPIO_ACTIVE_HIGH>; mosi-gpios = <&pio 2 2 GPIO_ACTIVE_HIGH>; cs-gpios = <&pio 2 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0x0>; spi-3wire; spi-lsb-first; spi-rx-delay-us = <1>; spi-max-frequency = <500000>; tm16xx,transposed; tm16xx,digits = [00 01 02 03]; tm16xx,segment-mapping = [00 01 02 03 04 05 06]; #address-cells = <2>; #size-cells = <0>; led@4,0 { reg = <4 0>; function = LED_FUNCTION_USB; }; led@4,1 { reg = <4 1>; function = LED_FUNCTION_SD; }; led@4,2 { reg = <4 2>; function = "hi-wifi"; }; led@4,3 { reg = <4 3>; function = "low-wifi"; }; led@4,4 { reg = <4 4>; function = "colon"; }; led@4,5 { reg = <4 5>; function = "apps"; }; led@4,6 { reg = <4 6>; function = LED_FUNCTION_LAN; }; }; }; };

Hi, thanks for checking. I check dmesg -T | grep spi_gpio and see the error spi_gpio spi: probe with driver spi_gpio failed with error -22. Also the /sys/class/leds is empty. Do you think the gpio pins are not correct? Below are current gpio pins I try this time mosi-gpios = <&pio 2 11 GPIO_ACTIVE_HIGH>; /* PC11 = data */ sck-gpios = <&pio 2 12 GPIO_ACTIVE_HIGH>; /* PC12 = clock */ cs-gpios = <&pio 7 5 GPIO_ACTIVE_LOW>; /* PH5 = strobe/latch */

@Jean-Francois Lessard sorry for making you confused. Device tree source for tm16xx driver that I convert from a working openvfd.conf is below /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = < 7 GPIO_ACTIVE_HIGH>; mosi-gpios = < 2 GPIO_ACTIVE_HIGH>; cs-gpios = < 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0>; spi-3wire; spi-lsb-first; spi-max-frequency = <500000>; digits { #address-cells = <1>; #size-cells = <0>; 01 02 03 04 }; leds { #address-cells = <2>; #size-cells = <0>; led@{GRID0},0 { reg = <{GRID0} 0>; function = "apps"; }; led@{GRID1},1 { reg = <{GRID1} 1>; function = "setup"; }; led@{GRID2},2 { reg = <{GRID2} 2>; function = LED_FUNCTION_USB; }; led@{GRID3},3 { reg = <{GRID3} 3>; function = LED_FUNCTION_SD; }; led@{GRID4},4 { reg = <{GRID4} 4>; function = "colon"; }; led@{GRID5},5 { reg = <{GRID5} 5>; function = "hdmi"; }; led@{GRID6},6 { reg = <{GRID6} 6>; function = "video"; }; }; }; }; }; The convert script I downloaded from this commit https://github.com/jefflessard/tm16xx-display/blob/a93b257ed4c73780fcdefbb1f1dd189599cf6ecc/vfdconf-convert Can you please help get it to work? Thanks!

@Jean-Francois Lessard I'm sorry for the typo. Yes the controller is tm1628. ls /sys/class/leds --> shows empty. Dmesg doesn't show any message for tm16xx. I've attached the working overlay source for openvfd which I have the clock digits working at least with. (The full icons would be card, usb, Low wifi, hi wifi, apps and eth) openvfd_x98h.dts

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?

@Nick A it has same issue. I thik it is related to the device tree declaration. Should it be something like this? https://github.com/LYU4662/aic8800-sdio-linux-1.0

@robertoj thank you for the answer. I will look at it. @Nick A Hi Nick, for your x98h box, is the wifi working after a reboot command?

Hi I got error when applying the patch you shared. Can I know how to fix it?

Hi every one, Do we have a fix for bluetooth?

@firepowercan you let me know what is difference between Murata and Samsung ones? I don't know what is mine and I tried both but nothing is working for me.

@MMoralesthank you! I'm thinking of a way to integrate it into openvfd driver module. But it is a bit complicated.

@MMorales I read those posts. do you make a python script for it?

Hi, can you share with me how you could do that? Thanks!