All Activity

He works as ili9341 and as ili9486. I use it now as ili9486. I`ll go further to make it work as native device. DRM frambuffer its something what needs to be kernel recompiled... as i know? And if i want to use it natively, i must edit or recompile u-boot.... DRM support for ILI9486 display panels modulename: ili9486.ko configname: CONFIG_TINYDRM_ILI9486 Linux Kernel Configuration └─>Device Drivers └─>Graphics support └─>Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) └─>SPI support └─>DRM support for ILI9486 display panels In linux kernel since version 4.14.326 (release Date: 2023-09-23) DRM driver for the following Ilitek ILI9486 panels: * PISCREEN 3.5" 320x480 TFT (Ozzmaker 3.5") * RPILCD 3.5" 320x480 TFT (Waveshare 3.5") If M is selected the module will be called ili9486. I will use it for KlipperScreen 😆 But as i se how hard is working that orangePi PC,i`ll doubt if i need this... Any way i`ll try )) Yes. But HDMI not connected. On OrangePiOne image its switching. If HDMI is connected its use it with no output to SPI. But if no HDMI present its use SPI as basic overlay On the same board. Because OPiOne had only 1 usb, OPiPC work only 1 usb ))) if will work all 3, i`ll didnt open up a topic 😑 ili9486.dts

In that case, dont try my solution: it is for the red ili9341. If you search ili9486 threads in this forum, that same blue LCD is ili9486... so you were wrong in calling it ili9341 in the first place If you have time, find another solution to get you a DRM frambuffer (instead of a classic FB). Then you can enjoy smoother animations and video. Regarding displaying boot messages to the LCD, instead of HDMI. I don't know, but it may be because your HDMI is /dev/fb0 and the LCD is /dev/fb1 Will you use X11?

I`ll think its china lcd, it`s been presented many ears ago by someone to me. Thanks to your sugestions. I read it before topic up. As U can read, it working now, with touch The last question is how to output to it when system boots... Something like auto switch from HDMI to SPI LCD. Or just SPI LCD output after U-Boot loading. rc.local with con2fbmap 1 1 in it is not an good thing. Any Advice?

I build a u-boot with it dd latest armbian.img and this u-boot, it showed: ▒[40]HELLO! BOOT0 is starting!r = 0x1d3 [43]BOOT0 commit : 4b34f2890a [46]set pll start [48]periph0 has been enabled [51]set pll end [54]unknow PMU [56]unknow PMU [59]PMU: AXP1530 [64]vaild para:15 select dram para1 [68]board init ok [69]enable_jtag [71]DRAM BOOT DRIVE INFO: V0.651 [74]the chip id is 0x2000 [77]chip id check OK [80]DRAM_VCC set to 1500 mv [86]read_calibration error [92]read_calibration error [98]read_calibration error [104]read_calibration error [110]read_calibration error [116]read_calibration error [122]read_calibration error [128]read_calibration error [135]read_calibration error [141]read_calibration error [143]retraining final error [152][AUTO DEBUG]32bit,1 ranks training success! [164]DRAM CLK =648 MHZ [166]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [174]Actual DRAM SIZE =2048 M [177]DRAM SIZE =2048 MBytes, para1 = 310a, para2 = 8000000, dram_tpr13 = 6041 [190]DRAM simple test OK. [193]rtc standby flag is 0x0, super standby flag is 0x0 [198]dram size =2048 [201]Use rtc to store dram tuning para [205]card no is 0 [207]sdcard 0 line count 4 [209][mmc]: mmc driver ver 2021-10-12 13:56 [214][mmc]: b mmc 0 bias 4 [222][mmc]: Wrong media type 0x0 [225][mmc]: ***Try SD card 0*** [240][mmc]: HSSDR52/SDR25 4 bit [243][mmc]: 50000000 Hz [245][mmc]: 119850 MB [247][mmc]: ***SD/MMC 0 init OK!!!*** [319]Loading boot-pkg Succeed(index=0). [323][mmc]: b mmc 0 bias 4 [325]Entry_name = u-boot [332]Entry_name = monitor [336]Entry_name = dtbo [339]Entry_name = optee [343]Entry_name = dtb [346]mmc not para [347]Jump to second Boot. NOTICE: BL3-1: v1.0(debug):54937d5 NOTICE: BL3-1: Built : 17:44:59, 2021-12-13 NOTICE: BL3-1 commit: 8 NOTICE: cpuidle init version V2.0 NOTICE: secure os exist MESSAGE: [0x0] TEE-CORE: OP-TEE version: 81ab7a47 #1 2020年 05月 06日 星期三 02:40:04 UTC arm NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 and I found this: [177]DRAM SIZE =2048 MBytes, para1 = 310a, para2 = 8000000, dram_tpr13 = 6041 is this para what we need?

Try this solution for the orange pi zero LTS, which is the same chip as the opiPC, but change the pin definitions to what you have. Do you have a 480x320 ili9341? Which one is it?

This one failed with "DRAM:This DRAM setup is currently not supported" I found something from kickpi's site:Linux_SDK_Compilation. including building u-boot https://github.com/tan-zhihao1/kickpi-book/blob/master/h618/en/04-SDK_Compilation_Guide/02-Linux_SDK_Compilation.md Its too huge so I deleted the folder "source" and "toolchains". hope it could help I tried to upload here but it shows errors. try this url: https://we.tl/t-t92S5rlCzD

@Jeeva Kandasamy I would freeze your kernel updates using armbian-config. I’m using a custom kernel so it might break your system. This might help fix your error. https://github.com/MichaIng/DietPi/issues/4600

Another problem here is that they don't have a schematic available for the rev2. They may have changed more than the DRAM? So the first u-boot I posted could have been fine, but the kernel DTS may need adjusting. Oh NVM. You did post the schematic EDIT: Not helpful. Its the same schematic I already have, which was incorrect as the variant I purchased is using DDR4. Not sure whats up with this company but they aren't very good at providing proper sources or essential unit information.

Try this one. I unfortunately I haven't been able to find any other timings. Hopefully this simple change makes a diff. u-boot-sunxi-with-spl.bin

There is another DDR3 option. GIve me a bit and I'll post it.

U-Boot SPL 2025.07 (Oct 24 2025 - 06:19:19 -0400) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.12.5(debug):lts-v2.12.5 NOTICE: BL31: Built : 06:13:32, Oct 24 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0cd800, model: KickPi K2B INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: Probing for PMIC on I2C: INFO: PMIC: found AXP313 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. U-Boot 2025.07 (Oct 24 2025 - 06:19:19 -0400) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: KickPi K2B DRAM: 2 GiB Core: 74 devices, 23 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4021000: 2, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Allwinner mUSB OTG (Peripheral) Net: eth0: ethernet@5020000using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in MAC de:ad:be:ef:00:01 HOST MAC de:ad:be:ef:00:00 RNDIS ready , eth1: usb_ether starting USB... USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 Bus usb@5101000: 1 USB Device(s) found Bus usb@5101400: 1 USB Device(s) found Bus usb@5200000: 1 USB Device(s) found Bus usb@5200400: 1 USB Device(s) found Bus usb@5310000: 1 USB Device(s) found Bus usb@5310400: 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 4641 bytes read in 1 ms (4.4 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 181 bytes read in 1 ms (176.8 KiB/s) Load fdt: /boot/dtb/allwinner/sun50iw9-kickpi-k2b.dtb 67673 bytes read in 5 ms (12.9 MiB/s) Working FDT set to 4fa00000 Failed to load '/boot/dtb/allwinner/overlay/h618-fixup.scr' 17096334 bytes read in 704 ms (23.2 MiB/s) 37613576 bytes read in 1549 ms (23.2 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x426d0000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17096270 Bytes = 16.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 48fb2000, end 49fffe4e ... OK Loading Device Tree to 0000000048f39000, end 0000000048fb1fff ... OK Working FDT set to 48f39000 No RNG device Starting kernel ... and stuck here. It makes differences!!

I don't know if this relates, but I recently discovered an issue with a Debian Trixie file system package xfsprogs on the 25.8.1 edge kernel for the Orange PI 5 Plus: https://forum.armbian.com/topic/55599-bug-report-armbian-edge-kernel-6164-xfsprogs-trixie-package-failure-to-start-low-memory-monitorservice/

Hi @Nick A thanks for the build details. It is working perfectly in my hardware: IK316Q-EMCP_V4.1 (IK3166-H, AXP313A, TYDOGH221664RA [1GB+8GB]) Current image: https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_server.img.xz However when I do apt upgrade I get the following error, Err:7 https://mirror.albony.in/armbian bookworm Release Redirection from https to 'http://mirror.hyd.albony.in/armbian/dists/bookworm/Release' is forbidden [IP: 82.180.145.196 443] I am using this device as headless server for IoT with internet, So I would like to keep updated kernel and packages all the time. Can you please guide me how to achieve this?

Just compiled and flashed a Cinnamon desktop image. Boots fine Video over HDMI working. Audio over HDMI working. The video experience is not that much satisfying. There seems to be no graphic acceleration, yet. WebGL aquarium runs at 5 FPS with 500 fishes, 15 FPS with 100 fishes. Youtube videos are relatively laggy and you'll experience high CPU load. All the GPIO hardware stuff has not been tested, yet. No clue how to do it... Now I'd like to have some more people on board to support me by adding graphic acceleration and how to merge the M1S support now into the Armbian repo. Greetings. EDIT 1: transferring the OS from SD card do eMMC works by using armbian-install tool EDIT 2: graphic acceleration IS kind of working, glmar2-es2 gives me a score of ~177. But the web browser seems not to be accelerated. also the desktop environment seems to have problems Cinnamon is not able to load applets, which means that the "Start" menue icon is missing...

I've got a REV 1.1. Try flashing the binary. I got the timing from the opi zero2 Make sure you flash it to the correct node, be it mmcblk1, sdb, etc. sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblkX conv=fsync bs=1024 seek=8 u-boot-sunxi-with-spl.bin

M.2 NVMe slot is also WORKING. At least the SSD gets detected with "cat /proc/partitions". It is not listed under "df -h" but I think this is because it is not mounted yet...

Okay. Thank you!

Since you have now confirmed the HDMI functionality, the time has come for me to retire further support. I am only interested in generic support; for Armbian-specific issues, you'll have to wait for others who are interested.

Okay, one step further: HDMI output is WORKING! initially I had the M1S connected to the Aux input of my AV receiver. There seems to be a problem with display detection (EDID, available modes) and so the M1S does not know which display mode to set. I then connected the M1S directly to an HDMI input of the TV and nothing changed. Rebooted and ... Surprise! Video output works, EDID information and available modes are available (wasn't when connected to AV receiver). So how can I tell Armbian to force a specific display mode even when no screen information is available?

To be honest I currently don't know. I booted my first from SD card. That worked as described above. After that, I've shut down the M1S, set the M1S to UMS mode and cloned the SD card to the internal eMMC. Booted as described. But please tell me how to perform that test and I can give your kernel build a try . Greetings

Version `25.8.2` of kernel, dtb and/or header package on Armbian Ubuntu Noble break `zfs-dkms` (I'm pretty sure kernel module `zfs` was not built with success) I had to run: ```sh sudo apt install linux-image-current-meson64=25.8.1 linux-headers-current-meson64=25.8.1 linux-dtb-current-meson64=25.8.1 && sudo dpkg-reconfigure zfs-dkms ``` I couldn't look in to the problem, because I was busy doing something else when I was just upgrading every package on the system. I had to prioritize quickly fixing it before another user arrives so I just reverted the suspicious packages (the three I mentioned in the title) I can't look into the problem now either because the computer is not being used by me alone..

From what I’ve found, the K2B has three revisions; mine is REV 2.2 (it’s printed right on the PCB). Looks like they swapped the RAM from DDR4L to DDR3—mine has DDR3 chips on board—so that might be why it’s acting up. Kickpi’s site barely loads from China; I really dislike that company, the documentation is almost non-existent. I found some here: https://github.com/tan-zhihao1/kickpi-book/tree/master/h618/en Still, I want to crack the problem. With the current sale the 2 GB + 0 GB version is only 78 CNY (about 11 USD), which is hard to pass up. Thanks for getting back to me. K2B.zip

Hello, I`ll try to hook up display to OpangePi PC, But have no output. My English is not native so i`ll try to write in simlpe way. image Armbian_23.8.1_Orangepipc_jammy_current_6.1.47_minimal.img.xz my dts: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&spi0>; __overlay__ { status = "okay"; // cs-gpios = <&pio 0 9 0>,<&pio 0 8 0>; /* PA9=CS0 for LCD, PA8=CS1 for touch */ display: display@0 { compatible = "ilitek,ili9341"; reg = <0>; pinctrl-names = "default"; spi-max-frequency = <20000000>; txbuflen = <65536>; rotate = <270>; bgr = <0>; fps = <30>; buswidth = <8>; regwidth = <16>; height = <480>; width = <320>; reset-gpios = <&pio 0 2 1>; /* PA20 */ dc-gpios = <&pio 0 71 0>; /* PA10 */ debug = <0>; init = <0x10000b0 0x00 // Interface Mode Control 0x1000011 // Sleep Out 0x20000ff // Delay (255ms) 0x10000C0 0x0D 0x0D // Power Control 1 0x10000C1 0x43 // Power Control 2 0x10000C5 0x00 0x48 0x80 // VCOM Control 1 0x10000C7 0x00 // VCOM Control 2 0x1000036 0x28 // Memory Access Control (Rotacao) 0x100003A 0x55 // Pixel Format Set (16bit) 0x10000B1 0xB0 0x11 // Frame Rate Control 0x10000F0 0x01 // Enable Extended Comand Set 0x10000F6 0x00 0x01 0x32 // SPI ilInterface Control 0x1000026 0x01 // Gamma Set 0x10000E0 0x0F 0x31 0x2B 0x0C 0x0E 0x08 0x4E 0xF1 0x37 0x07 0x10 0x03 0x0E 0x09 0x00 // Positive Gamma Correction 0x10000E1 0x00 0x0E 0x14 0x03 0x11 0x07 0x31 0xC1 0x48 0x08 0x0F 0x0C 0x31 0x36 0x0F // Negative Gamma Correction 0x10000B6 0x02 0x02 0x3B // Display Function Control 0x1000011 // Sleep Out 0x20000ff // Delay (255ms) 0x1000029>; // Display ON }; // xpt2046: xpt2046@1 { // compatible = "ti,ads7846"; // reg = <1>; // spi-max-frequency = <2000000>; // interrupts = <0 7 2>; /* high-to-low edge triggered */ // interrupt-parent = <&pio>; // pendown-gpio = <&pio 0 7 0>; // ti,keep-vref-on = <1>; // ti,x-min = /bits/ 16 <200>; // ti,x-max = /bits/ 16 <3900>; // ti,y-min = /bits/ 16 <200>; // ti,y-max = /bits/ 16 <3900>; // ti,x-plate-ohms = /bits/ 16 <60>; // ti,pressure-max = /bits/ 16 <255>; // ti,swap-xy = <1>; // }; }; }; }; when board boots, display switch from white to black. Without console output. gpio readall - looks good. all pins present. when I try Armbian_25.8.1_Orangepione_noble_current_6.12.43.img.xz board boots. add overlay to it, by armbian-add-overlays remove HDMI cable. (Really good first-config over ssh, why not to add this to other boards, like mine?) reboot Display works(Ony if HDMI is unpluged), with output of boot Armbian. I`ll think this something wrong with output on spi LCD over OrangePi PC Armbian build, or sometning like that way.... Any advise? UPD: Ok. I get it to work.(Armbian_23.8.1_Orangepipc_jammy_current_6.1.47_minimal.img.xz) ili9341 may be changed to ili9486. Didn`t matter...why? dmesg | grep graphics [ 9.406143] graphics fb1: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 64 KiB buffer memory, fps=31, spi0.0 at 16 MHz con2fbmap 1 1 and it works.... UPD 2: ili9486.dtbo With touch working, tested trought evtest

Hello, has anyone managed to get this camera to work on zero 3?

Hmmm. Never mind, maybe. I see that Armbian has it included here, but for some reason it was not installed automatically. https://github.com/armbian/build/tree/main/packages/bsp/odroid