Jump to content

viteo

Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. i'd made a new driver for PCD8544 display, because it is not compatible with mipi. A lot of time has passed since then, but i found my dts for st7789. hope it help you. st7789v-drm-spi.dts panel-mipi-dbi.dts
  2. i've managed to create DRM driver for that display. https://lore.kernel.org/linux-devicetree/20230807121022.1871-2-viteosen@gmail.com/ that was impressive jouney pcd8544.c pcd8544-drm-spi.dts
  3. I'm missing something essential. I have NanoPi Neo v1.4 with Armbian 23.5 Jammy CLI (Linux nanopineo 6.1.30-sunxi). My display is Nokia5110 LCD or PCD8544 With spi-spidev DT I can successfully via `spidev0.0` with `spi-tools`. I.e. I confirm that spi is working. Now, I studied about DTO and fbtft driver, found that it supports pcd8544. I wrote this kind of DTO and added it to `armbianEnv.txt` /* * Device: LCD5110 (nokia5110) 1.6"(84x48px) SPI display Module PCD8544 * Module Connector * SDI(MOSI) <- PC0 * SCK <- PC2 * CS <- PC3 * RESET <- PA1 * DC/RS <- PA3 * LED <- PA2 */ /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { display_pins: display_pins { pins = "PA1", "PA3"; /*RESET, DC_RS*/ function = "gpio_out"; }; }; }; fragment@1 { target = <&spi0>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; status = "okay"; cs-gpios = <&pio 2 3 0>; /* ChipSelect PC3 */ pcd8544: pcd8544@0 { compatible = "philips,pcd8544"; reg = <0>; pinctrl-names = "default"; pinctrl-0 = <&display_pins>; spi-max-frequency = <4000000>; buswidth = <8>; fps = <5>; // led-gpios = <&pio 0 2 1>; /*LED=PA2*/ reset-gpios = <&pio 0 1 1>; /*RESET=PA1*/ dc-gpios = <&pio 0 3 0>; /*DC_RS=PA3*/ }; }; }; }; I'm seeing in serial output `Applying user provided DT overlay sun8i-h3-spi-pdc8544.dtbo` But... Thats all. `dmesg | grep spi` or `dmesg | grep fbtft` is empty. `lsmod | grep fb` - also nothing. `ls /dev/fb*` - nope. If I manually call for `sudo modprobe spi:fb_pcd8544` this prints into dmesg: I've tried a lot of different tweaks in DTO, I've tried different releases from download page for my board. I don't know what am I missing. Is it somehow related to CLI nature of images? Why does no fb device apeears? Any help would be appreciated. Thank you.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines