As the wifi device is the same please see my last post in this thread : Viz : Also to fix BT : sudo crontab -e then add the line : @reboot sudo hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep It could also be your dtb though. You could decompile my dtb from this thread and use the Bluetooth related section.

Usually people switch off the HDMI monitor of the computer and and walk away. Or they put a mirror against the monitor and ask the person they see why they bought a computer that does not have Debian installed?. Why am I here? Do I need a CD-ROM drive to install from ISO myself? How do I enter the BIOS? Does it have BIOS? But there is hope. Aarch64 Debian13: root@odroidn2:/boot# apt install linux-image-arm64 root@odroidn2:/boot# ln -sf vmlinuz-6.12.57+deb13-arm64 Image reboot root@odroidn2:/boot# apt install u-boot-amlogic-binaries root@odroidn2:/boot# dpkg -L u-boot-amlogic-binaries | grep odroid-n2 /usr/lib/u-boot/odroid-n2 /usr/lib/u-boot/odroid-n2/u-boot.bin /usr/lib/u-boot/odroid-n2/uboot.elf /usr/share/doc/u-boot-amlogic-binaries/configs/config.odroid-n2.gz

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.

`idbloader.img` is device-specific code that is created from firmware build artifacts with U-Boot as payload using proprietary tools available only in binary form. SBC providers rarely offer ready-to-use code. I therefore prefer to load my firmware from microSD cards. Since it has apparently become increasingly common lately to provide only the MASKROM mode as the sole reliable recovery method, I have started building my firmware for Rockchip devices as RAM images as well. I can then simply upload them using MASKROM mode and start my work from there without having to rely on proprietary, binary-only tools.

Agree. @Igor