Active threads

I guess this should do:

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.

While having this sent to mainline would be overall best, the faster approach in the mean time would be to send a patch via PR to this location to have it included into Armbian kernel packages: https://github.com/armbian/build/tree/main/patch/kernel/archive/rockchip64-6.18

At this time we do not have plans to support it. However anyone is free to step up and provide support with a pull request. We'll happily review. Perhaps chainxs will do this since they're an active volunteer contributor already

Probably more experienced users will not have similar issues, but I'll provide my solution just for for the record: Power off devide. Insert SD card into the slot. Hold 'boot' button on the mainboard. Plug in device. Release 'boot' after 5 seconds. Power off and power on. in my case it took up to 60 seconds before my device boot from SD card. I checked the same with USB and it also work (*it ust be plugged into one of USB2.0 ports). Thank you for your suggestion. I'll close the thread.

Some updates... After rebooting (power off and power on) the device.... this appears and Armbian won't boot anymore...

@Gavin Munday Did you compile a desktop or server image? Did you write the image onto a reliable sdcard? Remember there’s no framebuffer support. Server images need a usb to serial device attached to the UART. Having a usb serial device attached to the UART helps with these types of problems. https://docs.radxa.com/en/cubie/a7a/system-config/uart_debug Also, first boot might take awhile to boot. For desktop images wait at least 5 minutes for a display manager login screen.

You don’t actually need a static route on PC1. Since PC1 already has a default gateway (192.168.100.254), anything outside 192.168.100.0/24 is automatically sent there. So PC1 isn’t the source of the routing problem. The real issue is on the 10.10.10.x side: Device1 has no gateway. Without a gateway, it can receive packets coming from the Linux box, but it has no way to send replies back to a different subnet. That’s why the communication fails. The fix is simply to give Device1 a valid gateway pointing to the Linux box. Device1: IP: 10.10.10.2 Mask: 255.255.255.0 Gateway: 10.10.10.1 On the Linux box: sudo sysctl -w net.ipv4.ip_forward=1 This is enough to route between NIC1 and NIC2. If Device1 cannot be configured manually, the Linux box can offer a small DHCP service on NIC2. A minimal dnsmasq example: interface=enp4s0 dhcp-range=10.10.10.50,10.10.10.150,255.255.255.0,12h dhcp-option=3,10.10.10.1 This simply ensures Device1 learns “send everything through 10.10.10.1”. Once Device1 has a gateway, the Linux box will forward traffic correctly and PC1 will reach it without needing any static route at all. Useful resources: https://wiki.archlinux.org/title/Router https://askubuntu.com/questions/205017/how-to-define-the-range-of-ips-using-dhcp https://pingmynetwork.com/network/ccna-200-301/dhcp-dynamic-host-configuration-protocol

Something wrong with xorg or x11 session on cinnamon desktop for my boxes, i can get into desktop when i choose experimental wayland session but that is not a good way to start. So, i switch to Mate and i like it

can this SoC boot from a USB drive? i've tried it multiple times and it didnt work.

moved to staging

Good day, @jock the link of the Multitool is not valid anymore. Please help where I can download from? Thank you for your efford.

I also tried the latest image (https://github.com/armbian/community/releases/download/26.2.0-trunk.22/Armbian_community_26.2.0-trunk.22_Rock-3c_trixie_current_6.12.59_minimal.img.xz) and it works fine (with mainline u-boot). I think I may have experienced problems using radxa's software to erase the spi flash memory, but writing an image fine would always work. So you may be better off writing Radxa's u-boot image to the spi flash memory, as per their instructions (and to get rid of the Android image). You can subsequently manage the spi flash memory either directly from u-boot (by interrupting start-up) or from the linux terminal. See comments by @amazingfate in this post for instruction on how to write Armbian u-boot image to mtdblock0 from a linux terminal.

I went out and bought a waveshare clone 3.5 inch display, to try and confirm I haven't spent the last few weeks trying to do the impossible with broken GPIO pins or something - and got a partial success eventually, using fbtft, displaying basic console and plymouth boot logs. It has poor fps like you said - which I expected, its the reason I tried to use the tiny DRM driver from the beginning, but now I know the rockpi and DTS is functional. The same DTS also shows a broken, purple / blue output of bars on my red ili9488 display only if I adjust the bus width to 16 instead of 8 (0x10, instead of 0x08), otherwise it remains a blank white screen. A bus width of 18 and 24 also only gave me a white screen, so 16 might be correct. I've been unable to confirm touch works, since I only have a basic console and I can't figure out how to start LXDE on a framebuffer device, but I do see messages insinuating it initializes under dmesg | grep spi. I could probably just query the GPIO interrupt to find out if touch is working. Not that important right now. I did realize that the big "fixups" section at the bottom is clearly used to replace the empty 0xfffffff targets throughout. I'm unsure why the DTS was written this way, but it works so I am not going to touch it (changing the targets and switching from hex to decimal values broke the DTS for some reason.) Unfortunately, a simple drop in replacement of fb_ili9486 with panel_mipi_dbi did not make either display work, even with the added arguments you use in your latest DTS. Clearly I have much more work to do. BUT I've finally confirmed the DTS works, and all GPIO is claimed and SPI is initialized for both displays (even if the red LCD is showing gibberish), so now I need to nail down the subtle differences with the displays like the bus and reg width and find the right combo of spi clock speed, reg bus widths, and buffer length to get it all to work with fbtft (if only aliexpress sellers put up datasheets or example code!). Then I can follow the second half of your journey to hopefully translate a working fbtft setup to a panel_mipi_dbi setup. Maybe get backlight PWM working. All this still on edge kernel 6.18, on a rockpi 4b plus.

I have the NanoPi-R6C and that came out of the box with an OpenWRT variant on eMMC. Indeed many partitions, but I think I managed to get it running somehow with Debian/Armbian rootfs on some higher partition number, I don't remember exactly. As long it can load boot.scr. Indeed eMMC is number 2, I guess they avoid potential confusion that is sometimes there with SBCs and various OSses swapping numbers for SD-card and eMMC. I had that once, no data loss but costed a lot of time. It is a bit similar to that on 6-SATA PC's, Debian might name the OS dev (SSD) /dev/sdb and a large HDD /dev/sda while Opensuse names OS always /dev/sda. So what do we do with 2-MMC SBC's ? I see my HP x86-64 dualrole computer/tablet uses /dev/mmcblk1 (its eMMC) for OS (Linuxes at least, Windows10 I don't remenber). The SD-card slot I have normally empty but uses /dev/mmcblk0 if card is inserted. It has UEFI and SecureBoot and TPM, so no choice actually like there is with opensource U-Boot. For NanoPi-R6C I have written Tianocore EDK2-UEFI to eMMC and appears as /dev/mmcblk1. I do not use the rest of the 32GB storage, but the UEFI binary comes with 1 partition, so easy to use the rest of the 32GB, but currently I need the much larger and faster NVME. And for emergency, if I insert an SD-card with newly generated rolling/edge image or so, it boots from that and is then /dev/mmcblk0. So this is IMO the preferred numbering, but I already had created some shell script code that can identify the boot partition and the root partition, but it is not too generic, only works if certain mounts are there which is what I have as I focus on EFI bootable and Btrfs with subvolumes ('nested' and default). So I would at least use 0 for SD. 1 for eMMC is fine. For the LEDs, on my NanoPi-R6C, I actually don't know, I never look at them. I think it is not correct with my installation (in-place upgraded and also other Linuxes), but I guess correct with current downloadable images. At least they were correct with the FriendlyElec OpenWRT that was pre-installed. I still can't get maskROM mode to work, so I am a bit paranoid on messing too much with data in the Rockchip loader area. I am not sure what happens if I put rubbish data or broken U-Boot there, can I still start from SD-card is the question. I might need to apply a fixed voltage between 9-20V as powersupply, but need to look in PCB schematics again first. For the Zero2, I see removable eMMC, so no risk or fear for 'hard-bricking'. Although I would check if maskROM works. For network, I assume it is the on-SoC port, so fixed off-the-shelf, so end0 is fine. For optional WLAN, I am not sure, likely some PCIe/HWtree named string, I have seen multiple altnames for 'wlo1', at least 'wlp1s0' or 'wlx<MACaddress>'. systemd-networkd should be able to handle those, NM can do all anyway.

Hi everyone, how's it going? I'm new to the forum and I'm having trouble getting my Chinese T95 mini TV box to run Linux. I want to switch it to a basic server, but I'm having problems booting it from the SD card. I'm using the sunxi-fel mode method in Linux. I tested Armbian_23.8.1_Orangepipc_jammy_current_6.1.47_minimal.img and others like Armbian_23.8.1_Orangepipc_jammy_current_6.1.47.img. I used the .bin file generated on this forum. Boot it using the method `sudo sunxi-fel -v -p uboot u-boot-sunxi-with-spl.bin` in the terminal. TV BOX Model: T95mini | R69 - EMCP V2.0 - H3 Allwinner. The screenshots below show the screen freezing. I'm a total noob, guys, if you could please explain the procedures, indicate what needs to be done to make it work. Thanks in advance libretech_all_h3_cc_h3_mem_336 - u-boot-sunxi-with-spl.bin

Glad I fell on this post Igor, Thank you for the share.. (download was indeed really fast!) I managed to install without any issues. (been using buster for way too long) Cheers, Again thanks in advance!

Seems you are using redhat kernel. it means something wrong changed in armbian meson64 kernel config after 6.16.??

Thanks for confirming. That makes 6.18 look very compelling. I have some ideas for how I'd like to present this and I'm finding myself wanting to flesh out my overview... If anyone has preferences for a better place than my PR comment to publish please let me know.

@ARx8 @rafaeldavid I was having this problem, and I just figured out that this is a cheat from the chip. I don't know the details but basically they mark the memory as 2GB but it actually just have 512MB. The Armbian sees 2GB but when you do a task that requires more that the actual 512MB it crashes. To solve that I manually set the memory on the Armbian to be 512MB. Edit the file: /boot/armbianEnv.txt Add the line (or change if already exists): extraargs=mem=512M On my case the device claimed 2GB of Ram. I reach the 512M testing. To get to this number I ran: free -h This gave me the amount of memory the system was already using (230M). After that I apt installed memtester and start testing the memory: memtester 200M I started at 200M and cancel the test (CTRL-C) on the firsts interaction after: Stuck Address : ok Random Value : ok Compare XOR : ok Compare SUB : ok Compare MUL : ok Compare DIV : ok Compare OR : ok Compare AND : ok The other tests took too long and if the problem is the memory that didnt exist just the firsts test would be enough. I ran memtester increading by 50M, so 200,250,300... And on 300 the system crashed, so I assumed the real memory of the chip was 512 (the 230 from the system + the 250 from the memtester before it crashed).

No. This fork uses the name Armbian without permission and they do not contribute to the core development process. Instead they trick you into thinking that you'd get any sort of support here at our place whatsoever.

Hello fedes_gl, thx for testing. Regarding wifi I got the same error with connectet LAN cable because the default Gateway is pointed to LAN address. Remove the LAN cable and you should be able to connect over wifi. x88pro:~:# routel Dst Gateway Prefsrc Protocol Scope Dev Table default 192.168.178.1 192.168.178.71 dhcp wlan0 192.168.178.0/24 192.168.178.71 kernel link wlan0 127.0.0.0/8 127.0.0.1 kernel host lo local 127.0.0.1 127.0.0.1 kernel host lo local 127.255.255.255 127.0.0.1 kernel link lo local 192.168.178.71 192.168.178.71 kernel host wlan0 local 192.168.178.255 192.168.178.71 kernel link wlan0 local