Fbtft problem luckfox ultra w

  • Emms wrote: 2024-11-11 22:23 Hello i have a problem with luckfox ultra w, i want to send picture for framebuffer in a SPI st7789, I changed the device tree but de fb doesn't exist in the console when i try to test this, i wrote $fbset and cant open /dev/fb0, i bought ultra w for sound but this not work whit framebuffer, i need help
    Hello, please provide me with the device tree you modified and the system serial port startup logs, and also let me know what your goal is so that I can better solve your problem!
  • this is .dtsi

    // SPI
    &spi0 {
    pinctrl-0 = <&spi0m0_clk &spi0m0_miso &spi0m0_mosi &spi0m0_cs0>;
    #address-cells = <1>;
    #size-cells = <0>;
    spidev@0 {
    compatible = "rockchip,spidev";
    spi-max-frequency = <50000000>;
    reg = <0>;
    };

    fbtft@0 {
    compatible = "sitronix,st7789v";
    reg = <0>;
    spi-max-frequency = <20000000>;
    fps = <30>;
    buswidth = <8>;
    debug = <0x7>;
    led-gpios = <&gpio2 RK_PB0 GPIO_ACTIVE_HIGH>;//BL
    dc = <&gpio2 RK_PB1 GPIO_ACTIVE_HIGH>; //DC
    reset = <&gpio1 RK_PC3 GPIO_ACTIVE_LOW>; //RES

    width = <240>;
    height = <320>;
    // Configuración del framebuffer (asegúrate de incluir esto)
    bpp = <16>; // Bits por píxel (16 para RGB565)
    };
    };

    and .dts

    / {
    model = "Luckfox Pico Ultra W";
    compatible = "rockchip,rv1103g-38x38-ipc-v10", "rockchip,rv1106";

    restart-poweroff {
    compatible = "restart-poweroff";
    };

    sdio_pwrseq: sdio-pwrseq {
    compatible = "mmc-pwrseq-simple";
    pinctrl-names = "default";
    reset-gpios = <&gpio1 RK_PA2 GPIO_ACTIVE_LOW>;
    };

    wireless_bluetooth: wireless-bluetooth {
    compatible = "bluetooth-platdata";
    uart_rts_gpios = <&gpio0 RK_PA5 GPIO_ACTIVE_LOW>;
    pinctrl-names = "default", "rts_gpio";
    pinctrl-0 = <&uart1m0_rtsn>;
    pinctrl-1 = <&uart1_gpios>;
    BT,wake_gpio = <&gpio0 RK_PA2 GPIO_ACTIVE_HIGH>;
    BT,wake_host_irq = <&gpio1 RK_PA2 GPIO_ACTIVE_HIGH>;
    status = "okay";
    };

    gpio2pb0:gpio2pb0 {
    compatible = "regulator-fixed";
    pinctrl-names = "default";
    pinctrl-0 = <&gpio2_pb0>;
    regulator-name = "gpio2_pb0";
    regulator-always-on;
    };

    gpio2pb1:gpio2pb1 {
    compatible = "regulator-fixed";
    pinctrl-names = "default";
    pinctrl-0 = <&gpio2_pb1>;
    regulator-name = "gpio2_pb1";
    regulator-always-on;
    };

    gpio1pc3:gpio1pc3 {
    compatible = "regulator-fixed";
    pinctrl-names = "default";
    pinctrl-0 = <&gpio1_pc3>;
    regulator-name = "gpio1_pc3";
    regulator-always-on;
    };


    };

    /*************GPIO*****************/
    &pinctrl {
    gpio2-pb0{
    gpio2_pb0: gpio2-pb0 {
    rockchip,pins = <2 RK_PB0 RK_FUNC_GPIO &pcfg_pull_none>;
    };
    };

    gpio2-pb1{
    gpio2_pb1: gpio2-pb1 {
    rockchip,pins = <2 RK_PB1 RK_FUNC_GPIO &pcfg_pull_none>;
    };
    };

    gpio1-pc3{
    gpio1_pc3: gpio1-pc3 {
    rockchip,pins = <1 RK_PC3 RK_FUNC_GPIO &pcfg_pull_none>;
    };
    };
    };

    /**********SPI**********/
    &spi0 {
    status = "okay";
    fbtft@0 {
    status = "okay";
    spi-max-frequency = <50000000>;
    };
    spidev@0 {
    status = "disabled";
    spi-max-frequency = <50000000>;
    };
    };
  • You see that your settings on SPI are no problem, other need to make sure that the pin connection is correct, and then determine whether there is a pin to turn off RGB to avoid pin multiplexing conflicts. Forum support attachments, if possible, please attach complete dts and dtsi, as well as serial module access to the boot log, through the boot log print information can probably determine the problem