bsrobot

Hello everyone, I followed the configuration steps for the st7735s LCD driver, and here are the details of my setup and observations so far: Configuration Files and Commands /boot/overlay-user/st7735s-fb5.dts Command used: armbian-add-overlay /boot/overlay-user/st7735s-fb5.dts dmesg Output Filtered dmesg output related to framebuffer or SPI: Observations Based on dmesg, the driver and display appear to be detected. Relevant messages are logged during updates. The command fbi works correctly, and running cat /dev/fb0 reveals some data. However, the display remains bright white, and nothing is visible on the screen. I attempted to test various initialization sequences (the commented-out sections in the overlay file) but without success. Next Steps Before writing this post, I wanted to conduct more testing, particularly with the LCD initialization parameters, but I'm unsure how to proceed further in debugging this issue. I'd appreciate any advice or suggestions to resolve the display issue! Thanks in advance for your help.

Hello, and thank you for the suggestions. Just to clarify, I am not using an ILI9341 or ST7789 display. My display is a ST7735S (1.8", 128x160), a generic model purchased from AliExpress. The main issue is that while this setup worked perfectly on older Armbian kernels, it's no longer working with the current Kernel 6.12.x. It seems like the necessary module might have been removed or changed in the newer versions. I am not using a desktop environment; my goal is to use the display directly from the console/framebuffer (no X11). I’ve made some progress, but now I’m stuck. Here’s what I'm observing: The system does create a framebuffer device at /dev/fb0. When I use a tool like fbi to show an image, it runs without any errors. If I try to dump the framebuffer device (e.g., cat /dev/fb0), it outputs data, which suggests something is being written to the buffer. The problem is on the physical display itself: the screen's backlight turns on, but it remains completely blank (white). No image is ever displayed. I'm unfortunately not sure how to proceed from here. It feels like the display is being initialized enough to turn on the backlight, but the actual image data isn't being displayed correctly. I suspect the driver is not sending the right commands. Does anyone have an idea what I could try next? Thank you!

Hello everyone, I'm trying to get an ST7735S LCD display working with my Orange Pi Zero 2 (H616). This setup was working correctly with older Armbian kernels, but after a recent update, I can no longer get the SPI device to appear. I have already tried a couple of different configuration methods without success. System Information: Board: Orange Pi Zero 2 (H616) Display: ST7735S (SPI) Kernel Version: Linux orangepizero2 6.12.43-current-sunxi64 #2 SMP Wed Aug 20 16:30:58 UTC 2025 aarch64 GNU/Linux I have recently updated armbian-config by running the update from the script itself. Attempt 1: Using armbianEnv.txt My first attempt was to edit /boot/armbianEnv.txt and add the required overlays. Here is my configuration: verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 rootdev=UUID=aef396b8-ac79-477c-b797-466fc4d881a6 rootfstype=ext4 overlays=sun50ih616spidev1_0 sun50ih616spidev1_1 sun50ih616spispidev sun50ih616tft35_spi usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u After rebooting with this configuration, the device nodes are not created. The output of ls /dev/spidev* is empty. Attempt 2: Using a custom user overlay Next, I tried creating a custom Device Tree Overlay. I created the file /boot/overlay-user/sp1-spidev.dts with the following content: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&spi1>; __overlay__ { status = "okay"; pinctrl-names = "default"; #address-cells = <1>; #size-cells = <0>; spidev@0 { compatible = "spidev"; reg = <0>; spi-max-frequency = <50000000>; }; }; }; }; I then added sp1-spidev to the overlays line in armbianEnv.txt. This method seems to be partially working. After a reboot, I can see the SPI master controller: $ ls /sys/class/spi_master/ spi0 spi1 However, the spidev device is still missing. ls /dev/spidev* is still empty. Diagnostic Information Here is the output of dmesg filtered for "spi". It seems to refer to spi0, not spi1 which I am trying to configure, but I'm including it for completeness. $ dmesg | grep -i spi [ 2.821043] spi-nor spi0.0: supply vdd not found, using dummy regulator My Question I don't understand why the /dev/spidev* device is not being created, even when the spi1 master appears to be correctly enabled via the overlay. It seems like the spidev driver is not binding to the device. Since this worked on older kernels, has the method for enabling SPI devices changed? What is the correct procedure now? Is there something I'm missing in my overlay file or configuration? Thank you for your help

Thanks for the reply. In these days I will start some tests. One question, I don't have the led pin. Could the LED pin be my BLK? Another curiosity, why use fb_ili9341 and not fb_st7735r? on PCB i have only SDA i don't have MISO and MOSI pins. How can I do? Thank you

Hi, I would like to use st7735 in an orangePI zero 2 (H616). The st7735 module was purchased at the following link: https://it.aliexpress.com/item/33031122936.html?spm=a2g0o.order_list.order_list_main.32.c5eb36966Y6eGs&gatewayAdapt=glo2ita Armbian usage. I connected st7735 in the following way: OPI --------> st7735 23 --------> SCK 19 --------> SDA 24 --------> CS 13 --------> AD 11 --------> RTD 4 --------> VCC 25 --------> GND I then ran the following command: sudo modprobe fbtft_device custom name=fb_st7735r gpios=dc:3,reset:0 speed=16000000 rotate=90 The screen stays white with a red stripe at the bottom. I can't find any errors in dmesg. /dev/fb1 is created how can i use the command con2fbmap 1 1 which I found by following this guide: https://www.instructables.com/Orange-Pi-Zero-Connect-TFT-SPI-ST7735/ Thank you