Werner Posted November 2 Posted November 2 36 minutes ago, Sári Zoltán said: Orange Pi Lite: Different soc and even different soc family. This most likely will not work on h618. 0 Quote
robertoj Posted November 3 Posted November 3 20 hours ago, Sári Zoltán said: Paste your custom overlay configuration for SPI, DC, and reset GPIOs Share your DTS. It is the most challenging part of this. We can customize, based on SBC model. 0 Quote
Sári Zoltán Posted November 6 Posted November 6 (edited) In my first post, I shared it in a file called "spi-display-overlay.txt". Yes, I know it’s strange that it’s in a .txt file — but it’s there nonetheless. But you know what? Here it is : /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; /* Orange Pi Lite SoC */ fragment@0 { target = <&spi0>; /* SPI0 bus */ __overlay__ { status = "okay"; }; }; fragment@1 { target = <&spi0>; __overlay__ { #address-cells = <1>; #size-cells = <0>; ili9486: ili9486@0 { compatible = "ilitek,ili9486"; reg = <0>; /* CS0 */ spi-max-frequency = <24000000>; /* Speed of SPI */ rotate = <0>; fps = <30>; buswidth = <8>; regwidth = <16>; bgr = <0>; reset-gpios = <&pio 2 8 1>; /* PC08 */ dc-gpios = <&pio 2 7 0>; /* PC07 */ init = <0x10000b0 0x00 0x1000011 0x20000ff 0x100003a 0x55 0x1000036 0x28 0x10000c2 0x44 0x10000c5 0x00 0x00 0x00 0x00 0x10000e0 0x0f 0x1f 0x1c 0x0c 0x0f 0x08 0x48 0x98 0x37 0x0a 0x13 0x04 0x11 0x0d 0x00 0x10000e1 0x0f 0x32 0x2e 0x0b 0x0d 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00 0x1000036 0x28 0x1000011 0x1000029>; }; }; }; }; Edited November 6 by Sári Zoltán 0 Quote
robertoj Posted November 10 Posted November 10 Thank you for sharing it Can you include these specifications, for quick reference for future readers? Board, Debian version, Kernel, Graphics (console, X11, wayland) 0 Quote
Bhupiister singh Posted yesterday at 10:08 AM Posted yesterday at 10:08 AM Hi @robertoj and @WDR_s I am having a similar screen ILI9486 from waveshare that i am trying to make it work with Milk-v duo S board. https://www.waveshare.com/wiki/3.5inch_RPi_LCD_(B) I was able to drive ST7789v and see content on screen with below code dts file &spi3 { status = "okay"; /delete-node/ spidev@0; st7789v: st7789v@0 { compatible = "sitronix,st7789v"; reg = <0>; spi-max-frequency = <48000000>; spi-cpol; spi-cpha; rotate = <0>; fps = <60>; rgb; buswidth = <8>; dc = <&porta 18 GPIO_ACTIVE_HIGH>; reset = <&porta 28 GPIO_ACTIVE_HIGH>; debug = <0x0>; status = "okay"; }; }; But trying to make ILi9486 work is next to impossible for me. I tried the dts file modification that worked for @WDR_s before he implemented touch. But this also does not work for me. And just for information dc-gpios and reset-gpios does not work for me and i have to name it dc and reset or else device /dev/fb0 is not created. &spi3 { status = "okay"; #address-cells = <1>; #size-cells = <0>; /delete-node/ spidev@0; ili9486: ili9486@0 { /* IMPORTANT: fb_tft binds MUCH more reliably to this */ compatible = "ilitek,ili9341"; reg = <0>; status = "okay"; /* SPI MODE 0 (correct for Waveshare ILI9486) */ spi-max-frequency = <24000000>; /* Use SAME pins that worked for ST7789V */ dc = <&porta 18 GPIO_ACTIVE_HIGH>; reset = <&porta 28 GPIO_ACTIVE_HIGH>; rotate = <0>; bgr = <0>; fps = <30>; regwidth = <16>; buswidth = <8>; txbuflen = <65536>; debug = <3>; /* Long, safe init sequence */ init = <0x10000b0 0x00 0x1000011 0x20000ff 0x10000C0 0x0D 0x0D 0x10000C1 0x43 0x10000C5 0x00 0x48 0x80 0x10000C7 0x00 0x1000036 0x28 0x100003A 0x55 0x10000B1 0xB0 0x11 0x10000F0 0x01 0x10000F6 0x00 0x01 0x32 0x1000026 0x01 0x10000E0 0x0F 0x31 0x2B 0x0C 0x0E 0x08 0x4E 0xF1 0x37 0x07 0x10 0x03 0x0E 0x09 0x00 0x10000E1 0x00 0x0E 0x14 0x03 0x11 0x07 0x31 0xC1 0x48 0x08 0x0F 0x0C 0x31 0x36 0x0F 0x10000B6 0x02 0x02 0x3B 0x1000011 0x20000ff 0x1000029>; }; }; This is very critical for me and i would really appreciate if you could make things work for me. Is the kernel 5.10 a issue here? as my SPI pins work for other display but not just for this display. 0 Quote
Orima Posted 7 hours ago Posted 7 hours ago (edited) @robertoj Can I use your DTS to connect to my Orange Pi Zero 3 and 3.95" ILI9488 display? What issues might I encounter? Can I use the pins described in the DTS file? I've read your comments on this forum thread. It's described almost everywhere: you just need to change the driver name in the file and overwrite the pins with the ones used in the wiring. Are there any potential issues with using this method? I buy this display https://aliexpress.ru/item/1005004152942022.html?spm=a2g2w.orderdetail.0.0.12a44aa6BVhy8J&sku_id=12000028212240707&_ga=2.111843779.691992273.1764584312-1605484087.1719427130 Edited 7 hours ago by Orima 0 Quote
Michael Robinson Posted 5 hours ago Posted 5 hours ago IMO the best choice is something with hdmi port. 0 Quote
Orima Posted 3 hours ago Posted 3 hours ago @Michael Robinson I want to make a cyberdeck with this display and this single board computer The ports are supposed to be used for connecting peripherals. That's why I want to know if my project is viable, or if I should look for something else. 0 Quote
robertoj Posted 1 hour ago Posted 1 hour ago 5 hours ago, Orima said: Can I use your DTS to connect to my Orange Pi Zero 3 and 3.95" ILI9488 display? What issues might I encounter? Can I use the pins described in the DTS file? I've read your comments on this forum thread. No, it wont work. I have made another thread just for the orange pi zero 3 and ili9488 https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#comment-208446 Change the GPIOs to match your wiring and connections. 1 Quote
robertoj Posted 1 hour ago Posted 1 hour ago On 11/30/2025 at 2:08 AM, Bhupiister singh said: But trying to make ILi9486 work is next to impossible for me. I don't own any waveshare LCD. I am not sure what to suggest, except that I believe it will only work with a "ili9486_DRM" (can't remember the exact name) driver ko. It is made explicitly for waveshare SPI LCDSs, and you must activate within the armbian build script process. 0 Quote
Bhupiister singh Posted 1 hour ago Posted 1 hour ago @robertoj What about your experience with ST7796? I have one with red pcb. Even this one is not working for me. Tried different dtb and .c files. Did this work for you ever? 0 Quote
robertoj Posted 1 hour ago Posted 1 hour ago (edited) 6 minutes ago, Bhupiister singh said: What about your experience with ST7796? I have one with red pcb. Even this one is not working for me. Tried different dtb and .c files. Did this work for you ever? I only have RED ili9341, ili9486 and ili9488 I don't have time to look right now, but search the Raspberry Pi forum and there's a nice thread with just the RED LCDs, st77** and iliteks working with panel-mipi-dbi driver Then, when you find a solution over there, post the link here. Your objective is MilkV Duo S with Waveshare ili9488 LCD, right? Edited 1 hour ago by robertoj 0 Quote
Orima Posted 1 hour ago Posted 1 hour ago I tried two methods with ili9341 and ili9488 with 9341, when checking SPI, it returned the log below. The second method showed that spi-dev0.0 is my FullHD HDMI display. After turning it on, SPI-dev detected the connection, but the screen was still white. True, I didn’t change the rotate line for 9488 I soldered the pins according to the DST file /* OrangePi Zero 3 -> ILI9341 LCD connections SPI CLOCK = PH6 SPI DO (LCD MISO) = PH8 (OPIZ MISO) SPI DI (LCD MOSI) = PH7 (OPIZ MOSI) LCD DATA/CONTROL = PC8 LCD RESET = PC10 CHIP SELECT = PH9 < NOT USED ANYMORE ;) VCC = 3.3V PIN GND = GND PIN */ /dts-v1/; /plugin/; /{ compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5"; fragment@0 { target = <&pio>; __overlay__{ display_pins: display_pins { pins = "PC8", "PC10"; /* DC, reset pins*/ function = "gpio_out", "gpio_out"; }; }; }; fragment@1 { target = <&spi1>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; status="okay"; pinctrl-names = "default"; pinctrl-0 = <&spi1_pins>; /* Mux the PI to make sure they are set in spi Mode */ /*cs-gpios = <&pio 0 13 0>; /* PA13 chip select NOT USED! */ num-chipselects = <0>; display: display@0 { compatible = "ilitek,ili9341"; /*compatible = "ilitek,ili9488";*/ reg = <0>; pinctrl-names = "default"; pinctrl-1 = <&display_pins>; spi-max-frequency = <40000000>; rotate = <270>; /* rotate for ili9341, rotation for yx240qv29 */ bgr=<0>; fps = <15>; buswidth = <8>; height = <320>; width = <240>; reset-gpios = <&pio 2 10 0>; /* PC10 reset pin*/ dc-gpios = <&pio 2 8 0>; /* PC8 Data control pin */ debug = <3>; init = <0x10000b0 0x00 0x1000011 0x20000ff 0x100003a 0x55 0x1000036 0x28 0x10000c2 0x44 0x10000c5 0x00 0x00 0x00 0x00 0x10000e0 0x0f 0x1f 0x1c 0x0c 0x0f 0x08 0x48 0x98 0x37 0x0a 0x13 0x04 0x11 0x0d 0x00 0x10000e1 0x0f 0x32 0x2e 0x0b 0x0d 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00 0x10000e2 0x0f 0x32 0x2e 0x0b 0x0d 0x05 0x47 0x75 0x37 0x06 0x10 0x03 0x24 0x20 0x00 0x1000036 0x28 0x1000011 0x1000029>; }; }; }; __overrides__ { rotate = <&display>,"rotate:0"; fps = <&display>,"fps:0"; debug = <&display>,"debug:0"; }; }; user@orangepizero3:~$ dmesg|grep spi [ 1.899568] sun6i-spi 5011000.spi: chipselect 0 already in use [ 1.899578] spi_master spi1: spi_device register error /soc/spi@5011000/spidev@0 [ 1.899601] spi_master spi1: Failed to create SPI device for /soc/spi@5011000/spidev@0 [ 6.735454] SPI driver fb_ili9341 has no spi_device_id for ilitek,ili9341 [ 6.735562] fb_ili9341 spi1.0: fbtft_property_value: width = 240 [ 6.735571] fb_ili9341 spi1.0: fbtft_property_value: height = 320 [ 6.735577] fb_ili9341 spi1.0: fbtft_property_value: buswidth = 8 [ 6.735583] fb_ili9341 spi1.0: fbtft_property_value: debug = 3 [ 6.735589] fb_ili9341 spi1.0: fbtft_property_value: rotate = 270 [ 6.735595] fb_ili9341 spi1.0: fbtft_property_value: fps = 15 [ 6.735669] fb_ili9341 spi1.0: fbtft_gamma_parse_str() str= [ 6.735674] fb_ili9341 spi1.0: 1F 1A 18 0A 0F 06 45 87 32 0A 07 02 07 05 00 [ 6.735764] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'reset' GPIO [ 6.735785] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'dc' GPIO [ 6.735805] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'rd' GPIO [ 6.735820] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'wr' GPIO [ 6.735834] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'cs' GPIO [ 6.735849] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'latch' GPIO [ 6.735864] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.735879] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.735894] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.735909] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.735924] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.735938] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.735953] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.735968] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.735982] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.735997] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736013] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736049] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736064] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736078] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736101] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736116] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736131] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736146] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736161] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736176] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736212] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736227] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736242] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736256] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736271] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736286] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736301] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736315] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736330] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736345] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736360] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736375] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736389] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736404] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736419] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736434] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736449] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736463] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736478] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736493] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736507] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736522] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736537] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736552] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736567] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736581] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'db' GPIO [ 6.736596] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'led' GPIO [ 6.736610] fb_ili9341 spi1.0: fbtft_request_one_gpio: 'aux' GPIO [ 6.736616] fb_ili9341 spi1.0: fbtft_verify_gpios() [ 6.736627] fb_ili9341 spi1.0: fbtft_reset() [ 6.864274] fb_ili9341 spi1.0: init: write_register: [ 6.864300] fb_ili9341 spi1.0: buf[0] = B0 [ 6.864306] fb_ili9341 spi1.0: buf[1] = 00 [ 6.864541] fb_ili9341 spi1.0: init: write_register: [ 6.864546] fb_ili9341 spi1.0: buf[0] = 11 [ 6.864568] fb_ili9341 spi1.0: init: msleep(255) [ 7.144245] fb_ili9341 spi1.0: init: write_register: [ 7.144271] fb_ili9341 spi1.0: buf[0] = 3A [ 7.144281] fb_ili9341 spi1.0: buf[1] = 55 [ 7.144365] fb_ili9341 spi1.0: init: write_register: [ 7.144370] fb_ili9341 spi1.0: buf[0] = 36 [ 7.144375] fb_ili9341 spi1.0: buf[1] = 28 [ 7.144410] fb_ili9341 spi1.0: init: write_register: [ 7.144414] fb_ili9341 spi1.0: buf[0] = C2 [ 7.144419] fb_ili9341 spi1.0: buf[1] = 44 [ 7.144447] fb_ili9341 spi1.0: init: write_register: [ 7.144452] fb_ili9341 spi1.0: buf[0] = C5 [ 7.144456] fb_ili9341 spi1.0: buf[1] = 00 [ 7.144461] fb_ili9341 spi1.0: buf[2] = 00 [ 7.144466] fb_ili9341 spi1.0: buf[3] = 00 [ 7.144470] fb_ili9341 spi1.0: buf[4] = 00 [ 7.144519] fb_ili9341 spi1.0: init: write_register: [ 7.144524] fb_ili9341 spi1.0: buf[0] = E0 [ 7.144529] fb_ili9341 spi1.0: buf[1] = 0F [ 7.144533] fb_ili9341 spi1.0: buf[2] = 1F [ 7.144537] fb_ili9341 spi1.0: buf[3] = 1C [ 7.144542] fb_ili9341 spi1.0: buf[4] = 0C [ 7.144547] fb_ili9341 spi1.0: buf[5] = 0F [ 7.144551] fb_ili9341 spi1.0: buf[6] = 08 [ 7.144555] fb_ili9341 spi1.0: buf[7] = 48 [ 7.144560] fb_ili9341 spi1.0: buf[8] = 98 [ 7.144564] fb_ili9341 spi1.0: buf[9] = 37 [ 7.144569] fb_ili9341 spi1.0: buf[10] = 0A [ 7.144574] fb_ili9341 spi1.0: buf[11] = 13 [ 7.144579] fb_ili9341 spi1.0: buf[12] = 04 [ 7.144583] fb_ili9341 spi1.0: buf[13] = 11 [ 7.144588] fb_ili9341 spi1.0: buf[14] = 0D [ 7.144592] fb_ili9341 spi1.0: buf[15] = 00 [ 7.144627] fb_ili9341 spi1.0: init: write_register: [ 7.144632] fb_ili9341 spi1.0: buf[0] = E1 [ 7.144636] fb_ili9341 spi1.0: buf[1] = 0F [ 7.144641] fb_ili9341 spi1.0: buf[2] = 32 [ 7.144646] fb_ili9341 spi1.0: buf[3] = 2E [ 7.144650] fb_ili9341 spi1.0: buf[4] = 0B [ 7.144655] fb_ili9341 spi1.0: buf[5] = 0D [ 7.144659] fb_ili9341 spi1.0: buf[6] = 05 [ 7.144663] fb_ili9341 spi1.0: buf[7] = 47 [ 7.144668] fb_ili9341 spi1.0: buf[8] = 75 [ 7.144672] fb_ili9341 spi1.0: buf[9] = 37 [ 7.144677] fb_ili9341 spi1.0: buf[10] = 06 [ 7.144681] fb_ili9341 spi1.0: buf[11] = 10 [ 7.144686] fb_ili9341 spi1.0: buf[12] = 03 [ 7.144690] fb_ili9341 spi1.0: buf[13] = 24 [ 7.144695] fb_ili9341 spi1.0: buf[14] = 20 [ 7.144699] fb_ili9341 spi1.0: buf[15] = 00 [ 7.144732] fb_ili9341 spi1.0: init: write_register: [ 7.144736] fb_ili9341 spi1.0: buf[0] = E2 [ 7.144741] fb_ili9341 spi1.0: buf[1] = 0F [ 7.144746] fb_ili9341 spi1.0: buf[2] = 32 [ 7.144750] fb_ili9341 spi1.0: buf[3] = 2E [ 7.144755] fb_ili9341 spi1.0: buf[4] = 0B [ 7.144759] fb_ili9341 spi1.0: buf[5] = 0D [ 7.144763] fb_ili9341 spi1.0: buf[6] = 05 [ 7.144768] fb_ili9341 spi1.0: buf[7] = 47 [ 7.144772] fb_ili9341 spi1.0: buf[8] = 75 [ 7.144777] fb_ili9341 spi1.0: buf[9] = 37 [ 7.144781] fb_ili9341 spi1.0: buf[10] = 06 [ 7.144786] fb_ili9341 spi1.0: buf[11] = 10 [ 7.144790] fb_ili9341 spi1.0: buf[12] = 03 [ 7.144795] fb_ili9341 spi1.0: buf[13] = 24 [ 7.144799] fb_ili9341 spi1.0: buf[14] = 20 [ 7.144804] fb_ili9341 spi1.0: buf[15] = 00 [ 7.144836] fb_ili9341 spi1.0: init: write_register: [ 7.144841] fb_ili9341 spi1.0: buf[0] = 36 [ 7.144846] fb_ili9341 spi1.0: buf[1] = 28 [ 7.144873] fb_ili9341 spi1.0: init: write_register: [ 7.144878] fb_ili9341 spi1.0: buf[0] = 11 [ 7.144895] fb_ili9341 spi1.0: init: write_register: [ 7.144899] fb_ili9341 spi1.0: buf[0] = 29 [ 7.180777] fb_ili9341 spi1.0: Display update: 4186 kB/s, fps=0 [ 7.181166] graphics fb1: fb_ili9341 frame buffer, 320x240, 150 KiB video 0 Quote
Orima Posted 1 hour ago Posted 1 hour ago @РобертсSorry, I didn't have time to read your reply. I tried Pancake's instructions, but I got stuck at the Armbian image build stage. Would his method work on the Armbian image that comes with the Orange Pi Zero3 board? I think I've figured out which pins I need to solder so I don't have to change the GPIOs in the file, as I'm not very good at deciphering pins for configuration. Thank you very much for the information and your efforts. I'll try to give it a try tomorrow and give you an answer. 0 Quote
robertoj Posted 1 hour ago Posted 1 hour ago Deactivate spi-dev in the armbian-config. That DTS is only used if you want to run a userspace program to talk to the LCD. In this case, we want the linux kernel to talk to the LCD, so we only need to use the LCD driver (ideally not a FBTFT. DRM is preferred) 0 Quote
Bhupiister singh Posted 1 hour ago Posted 1 hour ago @robertoj My objective is MilkV Duo S with Waveshare ili9486 LCD, and it will be much better if I can use ST7796, as this is a 4-inch display. I need to make at least a 4-inch display work for my project. It can be any readily available display. 0 Quote
robertoj Posted 46 minutes ago Posted 46 minutes ago (edited) There's a 4 inch RED ili9488 in aliexpress. VERY RECOMMENDED. It may be shown as ili9486, correctly or incorrectly, but it doesn't matter. I have seen both ili9486 and ili9486 work with the same panel-mipi-dbi driver, settings and init firmware. At least in orange pi zero 3, some pins worked fine for GPIO and others didn't. Also make sure to use the default chip selects in your MilkV Duo 5, and not try to change that. Also share what Armbian and Linux version you are using. Edited 43 minutes ago by robertoj 0 Quote
Bhupiister singh Posted 45 minutes ago Posted 45 minutes ago Just now, robertoj said: It may be shown as ili9486, correctly or incorrectly, but it doesn't matter. I have seen both ili9486 and ili9486 work with the same panel-mipi-dbi driver, settings and init firmware. Making it work with panel-mipi-dbi is completely new to me. I hope ill be able to make sense out of it. 0 Quote
robertoj Posted 41 minutes ago Posted 41 minutes ago (edited) 8 minutes ago, Bhupiister singh said: Making it work with panel-mipi-dbi is completely new to me. I hope ill be able to make sense out of it. At this time, panel-mipi-dbi is the most universal way of using these SPI LCDs. Even the Raspberry community gets this recommendation (except for Waveshare LCDs). Bhupiister, does the MilkV Duo S really have 512MB RAM? How do you deal with that? I have used an orange pi zero LTS with 512MB of RAM with LXDE desktop in the past, but only with lightweight GUI applications. Does it really have a useful TPU? Edited 33 minutes ago by robertoj 0 Quote
Bhupiister singh Posted 30 minutes ago Posted 30 minutes ago 9 minutes ago, robertoj said: Bhupiister, does the MilkV Duo S really have 512MB RAM? How do you deal with that? My intention is not to put the whole desktop on the display. Just a user application. I am trying to build a thermostat and might use LVGL for it. I tried a similar project on 256MB and still had plenty of RAM left. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.