dr_toggleswitch Posted April 13 Posted April 13 Was anybody able to install to emmc on this unit? I can't do it with nand-sata-install. It only shows my SD card. 0 Quote
jimg Posted April 16 Posted April 16 (edited) On 4/13/2025 at 10:41 AM, dr_toggleswitch said: Was anybody able to install to emmc on this unit? I can't do it with nand-sata-install. It only shows my SD card. I don't think the Orange Pi Zero 3 has emmc.. Edited April 16 by jimg 0 Quote
dr_toggleswitch Posted April 16 Posted April 16 ......... You are correct. Well, that explains that. The Kickpi I have has 8GB EMMC and I was wondering why I didn't see any reports of people installing to it. 0 Quote
ag123 Posted April 17 Author Posted April 17 I've not used a board which use EMMC (yet). They are more convenient, sometimes faster. While I'm not always against EMMC, some of the EMMC support is occasionally not very well documented / implemented, in particular by the vendors (e.g. how their boot rom selects booting from EMMC or SD). And that occasionally led to gotchas such as a boot fail in EMMC but it seem there isn't a way to recover from that etc. EMMC add a bit more complexity to the boot process, in particular by the boot rom (on PCs used to be called BIOS) and it is necessary to see that all the different boot permutations are well supported, boot from SD, boot from EMMC, override from SD (e.g. if EMMC install fails) etc, reflash EMMC from SD etc. 0 Quote
robertoj Posted April 17 Posted April 17 (edited) On 12/13/2024 at 9:06 PM, mantouboji said: edge 6.11.9 kernel added symbolic link for overlay Hello Have you tried using the SPI pins under Linux 6.12? Update: Opiz3 SPI pins work with Linux 6.12 and 6.13... but I needed 2 extra lines in the DTS. See: https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/#findComment-216779 Edited April 20 by robertoj 0 Quote
dr_toggleswitch Posted April 19 Posted April 19 I swapped OpenSSH server for Dropbear. Soooo much faster on this unit. Very noticeable. Easy to do on a headless install, just setup Dropbear on a different port than the default, reboot, sign in with that different port, disable & uninstall OpenSSH. 0 Quote
TRay Posted April 20 Posted April 20 I updated my ArmBian and the kernel 6.12.23 appeared but u-boot is still v24.01 and there is still a problem with incorrect detection of the memory size instead of 1 Gb it shows 2 Gb only after a few reboots it shows correctly 1 Gb RAM. I don't know if u-boot v25.x versions solve this problem Linux localhost 6.12.23-current-sunxi64 #1 SMP Thu Apr 10 12:39:41 UTC 2025 aarch64 GNU/Linux 0 Quote
Werner Posted April 21 Posted April 21 There are actually just a few situations where updating the boot loader makes sense. So when a new u-boot package is shipped it just provides the binaries but does not write them to the boot sector. I think you can use armbian-install to rewrite the boot loader with the latest binaries. 0 Quote
TRay Posted April 21 Posted April 21 1 hour ago, Werner said: I think you can use armbian-install to rewrite the boot loader with the latest binaries. Thank you for info. I did "armbian-install" and saved u-boot on microSD but in the directory /usr/lib/linux-u-boot-current-orangepizero3 declare -i UBOOT_NUM_TARGETS=1 declare UBOOT_BIN_DIR="/usr/lib/linux-u-boot-current-orangepizero3" declare UBOOT_VERSION="2024.01" declare UBOOT_ARTIFACT_VERSION="2024.01-S866c-P4a40-H8869-V380a-Bb703-R448a" declare UBOOT_GIT_REVISION="866ca972d6c3cabeaf6dbac431e8e08bb30b3c8e" declare UBOOT_GIT_SOURCE="https://github.com/u-boot/u-boot" declare UBOOT_GIT_BRANCH="tag:v2024.01" indicates that nothing has changed and there is information that u-boot is 2024.01 during apt upgrade is: Preparing to unpack .../base-files_25.5.0-trunk.426-12.4+deb12u10-bookworm_arm64.deb ... Unpacking base-files (25.5.0-trunk.426-12.4+deb12u10-bookworm) over (25.5.0-trunk.422-12.4+deb12u10-bookworm) ... Setting up base-files (25.5.0-trunk.426-12.4+deb12u10-bookworm) ... (Reading database ... 46891 files and directories currently installed.) Preparing to unpack .../armbian-bsp-cli-orangepizero3-current_25.5.0-trunk.426_arm64.deb ... Armbian 'armbian-bsp-cli-orangepizero3-current' for '1-PC8904-V801b-Hc65c-B1e5d-Rf36a': 'preinst' starting. Armbian 'armbian-bsp-cli-orangepizero3-current' for '1-PC8904-V801b-Hc65c-B1e5d-Rf36a': 'preinst' finishing. Unpacking armbian-bsp-cli-orangepizero3-current (25.5.0-trunk.426) over (25.5.0-trunk.422) ... Armbian 'armbian-bsp-cli-orangepizero3-current' for '1-PC8904-V801b-Hc65c-B1e5d-Rf36a': 'postrm' starting. Armbian 'armbian-bsp-cli-orangepizero3-current' for '1-PC8904-V801b-Hc65c-B1e5d-Rf36a': 'postrm' finishing. Preparing to unpack .../armbian-firmware_25.5.0-trunk.426_all.deb ... Unpacking armbian-firmware (25.5.0-trunk.426) over (25.5.0-trunk.422) ... Preparing to unpack .../linux-dtb-current-sunxi64_25.5.0-trunk.426_arm64.deb ... Armbian 'linux-dtb-current-sunxi64' for '6.12.23-current-sunxi64': 'preinst' starting. Armbian 'linux-dtb-current-sunxi64' for '6.12.23-current-sunxi64': 'preinst' finishing. Unpacking linux-dtb-current-sunxi64 (25.5.0-trunk.426) over (25.5.0-trunk.422) ... Preparing to unpack .../linux-image-current-sunxi64_25.5.0-trunk.426_arm64.deb ... Armbian 'linux-image-current-sunxi64' for '6.12.23-current-sunxi64': 'prerm' starting. Armbian 'linux-image-current-sunxi64' for '6.12.23-current-sunxi64': 'prerm' finishing. Armbian 'linux-image-current-sunxi64' for '6.12.23-current-sunxi64': 'preinst' starting. Armbian 'linux-image-current-sunxi64' for '6.12.23-current-sunxi64': 'preinst' finishing. Unpacking linux-image-current-sunxi64 (25.5.0-trunk.426) over (25.5.0-trunk.422) ... Armbian 'linux-image-current-sunxi64' for '6.12.23-current-sunxi64': 'postrm' starting. Armbian 'linux-image-current-sunxi64' for '6.12.23-current-sunxi64': 'postrm' finishing. Preparing to unpack .../linux-u-boot-orangepizero3-current_25.5.0-trunk.426_arm64.deb ... Unpacking linux-u-boot-orangepizero3-current (25.5.0-trunk.426) over (25.5.0-trunk.422) ... Setting up linux-u-boot-orangepizero3-current (25.5.0-trunk.426) ... Armbian 'uboot-orangepizero3-current' for '2024.01-S866c-P4a40-H8869-V380a-Bb703-R448a': 'postinst' starting. Armbian 'uboot-orangepizero3-current' for '2024.01-S866c-P4a40-H8869-V380a-Bb703-R448a': 'postinst' finishing. Setting up linux-image-current-sunxi64 (25.5.0-trunk.426) ... Armbian 'linux-image-current-sunxi64' for '6.12.23-current-sunxi64': 'postinst' starting. update-initramfs: Generating /boot/initrd.img-6.12.23-current-sunxi64 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.12.23-current-sunxi64 Image Name: uInitrd Created: Mon Apr 21 09:18:24 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 12492766 Bytes = 12199.97 KiB = 11.91 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.12.23-current-sunxi64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.12.23-current-sunxi64' update-initramfs: Armbian: done. Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.12.23-current-sunxi64' Armbian: Debian compat: linux-update-symlinks install 6.12.23-current-sunxi64 boot/vmlinuz-6.12.23-current-sunxi64 Armbian 'linux-image-current-sunxi64' for '6.12.23-current-sunxi64': 'postinst' finishing. Setting up armbian-bsp-cli-orangepizero3-current (25.5.0-trunk.426) ... Armbian 'armbian-bsp-cli-orangepizero3-current' for '1-PC8904-V801b-Hc65c-B1e5d-Rf36a': 'postinst' starting. '/boot/boot.cmd' -> '/usr/share/armbian/boot.cmd-1745219906' NOTE: You can find previous bootscript versions in /usr/share/armbian ! Recreating boot script '/usr/share/armbian/boot.cmd' -> '/boot/boot.cmd' Armbian 'armbian-bsp-cli-orangepizero3-current' for '1-PC8904-V801b-Hc65c-B1e5d-Rf36a': 'postinst' finishing. Setting up linux-dtb-current-sunxi64 (25.5.0-trunk.426) ... Armbian 'linux-dtb-current-sunxi64' for '6.12.23-current-sunxi64': 'postinst' starting. Armbian: DTB: symlinking /boot/dtb to /boot/dtb-6.12.23-current-sunxi64... 'dtb' -> 'dtb-6.12.23-current-sunxi64' Armbian 'linux-dtb-current-sunxi64' for '6.12.23-current-sunxi64': 'postinst' finishing. Setting up armbian-firmware (25.5.0-trunk.426) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for initramfs-tools (0.142+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.12.23-current-sunxi64 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.12.23-current-sunxi64 Image Name: uInitrd Created: Mon Apr 21 09:18:56 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 12493052 Bytes = 12200.25 KiB = 11.91 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.12.23-current-sunxi64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.12.23-current-sunxi64' update-initramfs: Armbian: done. 0 Quote
Werner Posted April 21 Posted April 21 Seems like the default for sunxi64 family is v2024.01. You can try manually bumping it by overwriting at board level and see what happens. Example: https://github.com/armbian/build/blob/main/config/boards/nanopi-r3s.csc 0 Quote
TRay Posted April 21 Posted April 21 I noticed that after updating the kernel to version 6.12.23 there is a problem with armbin-config I can't set overllay tree devices choosing from armbian-config --cmd SY210 The current Armbian 25.5.0-trunk.426 nightly (bookworm) is supported. Check distro Loaded Dialog... Loaded Docs... Loaded System helpers... Loaded Network helpers... Loaded Software helpers... Loaded Runtime conditions... Invalid overlay_prefix sun50i-h616 I changed it to sun50i-h618 but Invalid overlay_prefix sun50i-h618 I made an empty overlay_prefix= but still Invalid overlay_prefix What should be now in overlay_prefix= in ArmBianEnv.txt for Organa Pi Zero 3 for kernel 6.12.23??? 0 Quote
TRay Posted April 21 Posted April 21 (edited) I updated armbian-config to latest version and now show devicetree Edited April 21 by TRay 0 Quote
TRay Posted April 21 Posted April 21 (edited) I notice that with now new kernel 6.12.23 and armbian-config where I set in device tree overlay uart5 for Orange Pi Zero 3 (OZPI v3 UART5 described in the original documentation) now change number from /dev/ttyS1 (it was up to 6.6.67 kernel version) now is /dev/ttyS0 [ 0.000621] printk: legacy console [tty1] enabled [ 1.550621] printk: legacy console [ttyS0] disabled [ 1.551031] 5000000.serial: ttyS0 at MMIO 0x5000000 (irq = 300, base_baud = 1500000) is a 16550A [ 1.551091] printk: legacy console [ttyS0] enabled but I am not sure why is now change name in device tree from uart5-ph to uart5 Edited April 21 by TRay update info about UART5 0 Quote
TRay Posted April 21 Posted April 21 (edited) I check on my old microSD card image with kernel 6.6.75 Linux armbian 6.6.75-current-sunxi64 #1 SMP Sat Feb 1 17:37:57 UTC 2025 aarch64 GNU/Linux [ 0.000505] printk: console [tty1] enabled [ 1.371166] printk: console [ttyS0] disabled [ 1.371473] 5000000.serial: ttyS0 at MMIO 0x5000000 (irq = 297, base_baud = 1500000) is a 16550A [ 1.371524] printk: console [ttyS0] enabled [ 1.372761] 5001400.serial: ttyS1 at MMIO 0x5001400 (irq = 298, base_baud = 1500000) is a 16550A and now I see that /dev/ttyS0 is for console connect but /dev/ttyS1 was UART5 on 26 PIN header so at current with new kernel 6.12.23 and we set in armbianEnv.txt sun50i-h616-uart5 via armbian-config we are not have access to UART5 /dev/ttyS1 Edited April 21 by TRay 0 Quote
TRay Posted April 21 Posted April 21 I see that current image Orange Pi Zero 3 for download base on kernel 6.12 so the question is, does anyone have a problem with access to UART5 which is on the 26-pin connector? 0 Quote
robertoj Posted April 21 Posted April 21 (edited) With these instructions, you may get UART5 in ttyS1 https://forum.armbian.com/topic/43718-orange-pi-zero-3-issues-with-gps-on-uart/ https://forum.armbian.com/topic/44034-using-gpio-ports-on-orangepi-zero3/#comment-201030 Edited April 21 by robertoj 0 Quote
TRay Posted April 22 Posted April 22 (edited) Hi I know that I can use UART5 as /dev/ttyS1 but it worked on kernel 6.6.67 when in overlays was used uart5-ph but after update to kernel 6.12.23 and new armbian-config now when you use armbian-config to setup device tree the UART5 has changed name to sun50i-h616-uart5 and this name is put in overlays in armbianEnv.txt. overlays=sun50i-h616-uart5 After reboot we lose UART5 as /dev/ttyS1 But I found old problem that armbian-config add overlay_prefix to device name (https://github.com/armbian/configng/issues/344#issuecomment-2613947809 ) and this make problem. When I removed sun50i-616 from name sun50i-616-uart5 and overlays line looks: overlays=uart5 (don't use uart5-ph) now I see again UART5 /dev/ttyS1 in my system [ 0.000624] printk: legacy console [tty1] enabled [ 1.552801] printk: legacy console [ttyS0] disabled [ 1.553231] 5000000.serial: ttyS0 at MMIO 0x5000000 (irq = 301, base_baud = 1500000) is a 16550A [ 1.553288] printk: legacy console [ttyS0] enabled [ 1.554781] 5001400.serial: ttyS1 at MMIO 0x5001400 (irq = 303, base_baud = 1500000) is a 16550A Edited April 22 by TRay 0 Quote
TRay Posted April 22 Posted April 22 The question is why (what was the reason) the name for h616 uart5-ph which was used so far to the name uart5 was changed (without -ph)? This will now cause many people to look for a solution to the problem with access to UART5. In the new kernel 6.12.23 I see that UART2 which is also available is still in the device tree called uart2-ph-... 0 Quote
robertoj Posted April 22 Posted April 22 (edited) Nice find I don't know why those changes happen... but we as bleeding edge linux users, must be aware of those things (by searching in the armbian forum... or sometimes in the raspberry forum) Edited April 22 by robertoj 0 Quote
TRay Posted April 24 Posted April 24 On 4/21/2025 at 9:29 AM, Werner said: Seems like the default for sunxi64 family is v2024.01. You can try manually bumping it by overwriting at board level and see what happens. I see that u-boot 2025.04 has applied some fixes to DRAM detection a month ago https://github.com/u-boot/u-boot/commits/master/arch/arm/mach-sunxi/dram_sun50i_h616.c so if the new u-boot 2025.04 via apt upgrade will be available in armbian for Orange Pi Zero 3, there is hope that the problem of incorrect detection of RAM size will be solved 0 Quote
TRay Posted Wednesday at 04:59 AM Posted Wednesday at 04:59 AM From the information of DietPi users, it appears that they have used UBoot v2025.04 for Orange Pi Zero 3 and it seems that the problem of incorrect detection of RAM size has been solved, especially in the version with 1 MB. It would be valuable if ArmBian was also transferred for Orange Pi Zero 3 to Uboot v2025.04, we could avoid complications during system updates and other processes that need a lot of RAM causing the system to hang up because they try to use memory addresses that are not physically there when the RAM size was incorrectly identified during booting. More info about UBoot v2025.04 with Orange Pi Zero 3: https://github.com/MichaIng/DietPi/issues/7242#issuecomment-2912290816 0 Quote
going Posted Wednesday at 05:06 PM Posted Wednesday at 05:06 PM 12 часов назад, TRay сказал: Orange Pi Zero 3 to Uboot v2025.04, Ok! Are you ready to test it? 0 Quote
Igor Posted Wednesday at 06:00 PM Posted Wednesday at 06:00 PM Also need someone to test this: https://fi.mirror.armbian.de/incoming/igorpecovnik/orangepizero3/archive/ 0 Quote
Michael Robinson Posted Wednesday at 07:05 PM Posted Wednesday at 07:05 PM /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.5.1 for Orange Pi Zero3 running Armbian Linux 6.12.23-current-sunxi64 Packages: Ubuntu stable (noble) Support: DIY (community maintained) IPv4: (LAN) 192.168.***.*** (WAN) ***.***.***.*** IPv6: *** Performance: Load: 4% Up time: 16 min Local users: 3 Memory usage: 45% of 971M Zram usage: 47% of 485M CPU temp: 46°C Usage of /: 11% of 58G RX today: 98 MiB Commands: Configuration : armbian-config Monitoring : htop *** System restart required *** Some packages require a reboot (gnome-shell) orangepi@orangepizero3:~$ 1 Quote
boyd86 Posted 22 hours ago Posted 22 hours ago I am also available for testing new images on Orange Pi Zero 3, while I am new to this SBC I am happy to learn. Today I have installed "Armbian_community_25.8.0-trunk.38_Orangepizero3_bookworm_current_6.12.23_minimal.img" to use for NTP server purposes. I have successfully enabled uart5 by using "overlays=uart5" and seeing GPS data with "gpsmon /dev/ttyS1". However, I also want to use PPS signal coming from my Waveshare L76K module, and the pps device does not seem to be created. I have used the following dts, from this forum: /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target = <&pio>; __overlay__ { pps_pins: pps_pins { pins = "PC7"; function = "gpio_in"; }; }; }; fragment@1 { target-path = "/"; __overlay__ { pps@0 { compatible = "pps-gpio"; pinctrl-names = "default"; /* pinctrl-0 = <&pps_pins>; */ gpios = <&pio 2 7 0>; /* PC7 */ status = "okay"; }; }; }; }; Then I did "armbian-add-overlay sun50i-h616-pps-gpio.dts" followed by a reboot. Then I do not see any PPS device. Am I missing something else? 0 Quote
TRay Posted 19 hours ago Posted 19 hours ago I use the ArmBian version which is updated very often (see below) so if U-Boot v2025.04 for OZPI v3 appears in the current updates it will be possible to check and other users who have OZPI v3 with 1,1.5, 2, or 4 Gb RAM check it 0 Quote
ag123 Posted 16 hours ago Author Posted 16 hours ago @Igor Armbian_25.5.1_Orangepizero3_bookworm_current_6.12.23_mi nimal.img.xz below is transcript from the 'debug uart (serial)' console, via a usb-uart dongle, it is the only way to boot up with a console , if network etc is not available. U-Boot 2024.01-armbian-2024.01-S866c-P4a40-H8869-V3d5b-Bb703-R448a (May 28 2025 - 02:53:19 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: OrangePi Zero3 DRAM: 1.5 GiB Core: 57 devices, 25 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to use mmc 0:1... .... _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.5.1 for Orange Pi Zero3 running Armbian Linux 6.12.23-current-sunxi64 Packages: Debian stable (bookworm) Updates: Kernel upgrade enabled and 23 packages available for upgrade Support: DIY (community maintained) IPv4: (LAN) 192.168.xxx.xxx (WAN) xxx.xxx.xxx.xxx IPv6: fd00:xxxx:xxxxx, xxxxx (WAN) xxxx Performance: Load: 18% Up time: 2 min Memory usage: 9% of 1.44G CPU temp: 50°C Usage of /: 9% of 15G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop root@orangepizero3:~# ping google.com PING google.com (142.250.4.138) 56(84) bytes of data. 64 bytes from sm-in-f138.1e100.net (142.250.4.138): icmp_seq=1 ttl=100 time=2.77 ms 64 bytes from sm-in-f138.1e100.net (142.250.4.138): icmp_seq=2 ttl=100 time=2.79 ms ^ ethernet works root@orangepizero3:~# ip link set wlan0 up root@orangepizero3:~# iw dev wlan0 scan BSS xxxxx freq: 24xx signal: -77 dBm ^ wifi works, at least for scanning for stations, connect and AP not yet tested ^ the above is booted up on a 'rare' 1.5GB board. repeat using the same uSD card on a 4 GB board, initially the debug usb-uart console is garbled, it seemed to be a baud rate mismatch, I'm not sure why, but after a few retry it works. Perhaps it is due to bad wires. U-Boot 2024.01-armbian-2024.01-S866c-P4a40-H8869-V3d5b-Bb703-R448a (May 28 2025 - 02:53:19 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: OrangePi Zero3 DRAM: 4 GiB Core: 57 devices, 25 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to use mmc 0:1... ... _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.5.1 for Orange Pi Zero3 running Armbian Linux 6.12.23-current-sunxi64 Packages: Debian stable (bookworm) Updates: Kernel upgrade enabled and 23 packages available for upgrade Support: DIY (community maintained) IPv4: (LAN) 192.168.xxx.xxx (WAN) xxx.xxx.xxx.xxx IPv6: fd00:xxxx:xxxxx, xxxxxxxx (WAN) xxxxxxxx Performance: Load: 12% Up time: 1 min Memory usage: 3% of 3.83G CPU temp: 46°C Usage of /: 9% of 15G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop root@orangepizero3:~# ping google.com PING google.com (142.251.12.139) 56(84) bytes of data. 64 bytes from se-in-f139.1e100.net (142.251.12.139): icmp_seq=1 ttl=103 time=2.69 ms 64 bytes from se-in-f139.1e100.net (142.251.12.139): icmp_seq=2 ttl=103 time=2.99 ms ^ ethernet works root@orangepizero3:~# ip link set wlan0 up root@orangepizero3:~# iw dev wlan0 scan BSS xxxxxx(on wlan0) freq: 24xx signal: -78.00 dBm ^ wifi works for scan, connect and AP not tested I'm not too sure what is the difference between v25.5.1 vs that on the boards page? https://www.armbian.com/orange-pi-zero-3/ from those links 'current' seemed to be linked to: as of current 28 May 2025 Armbian_community_25.8.0-trunk.8_Orangepizero3_bookworm_current_6.12.23_minimal.img.xz btw thanks much (to all contributors) for updating Armbian to 25.x for OrangePi Zero 3 (and likely means works for Zero 2W) as well. oh frequency scaling works as well, this is on the 4GB board root@orangepizero3:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq Tcpu C.St. 01:43:36 1416 MHz 0.00 1% 0% 0% 0% 0% 0% 47.2 °C 0/7 01:43:41 480 MHz 0.00 0% 0% 0% 0% 0% 0% 47.2 °C 0/7 01:43:46 480 MHz 0.00 0% 0% 0% 0% 0% 0% 47.4 °C 0/7 01:43:51 480 MHz 0.00 0% 0% 0% 0% 0% 0% 47.0 °C 0/7 'everyone' should just get the 4GB board, make it a 'standard' lol @TRay It is a good idea to try U-Boot v2025.04 I've got a python script which can patch u-boot binary into an Armbian .img or practically any other image file (though i've only tested this in *unofficial* armbian builds) https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3/tree/main/tools https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3 i created it back then while researching solutions for the '1.5GB' problem back then. Do you have the 'bin' file for u-boot that you could share say in a zip file attached here? you can extract that 'bin' file using the 'backup' procedure documented here: https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3?tab=readme-ov-file#how-to-use sudo dd if=/dev/sdX of=u-boot-backup.bin bs=1024 skip=8 count=1024 But that the appropriate way would be to build the full armbian image from source including u-boot etc. Nevertheless, having the 'patched' u-boot binary would enable most here to test that by patching a distributed image file e.g. from the boards page, or from the 'test images' link as Igor has provided. 0 Quote
mantouboji Posted 15 hours ago Posted 15 hours ago (edited) sun50i-h616-spidev1_1.dtso /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h616"; fragment@0 { target-path = "/aliases"; __overlay__ { spi1 = "/soc/spi@5011000"; }; }; fragment@1 { target = <&spi1>; __overlay__ { status = "okay"; #address-cells = <1>; #size-cells = <0>; pinctrl-names = "default"; pinctrl-0 = <&spi1_pins>,<&spi1_cs1_pin>; spidev1_1: spidev@1 { compatible = "armbian,spi-dev"; status = "okay"; reg = <1>; spi-max-frequency = <1000000>; }; }; }; }; Edited 15 hours ago by mantouboji fix code 0 Quote
Igor Posted 14 hours ago Posted 14 hours ago 2 hours ago, ag123 said: I'm not too sure what is the difference between v25.5.1 vs that on the boards page? https://www.armbian.com/orange-pi-zero-3/ from those links 'current' seemed to be linked to: as of current 28 May 2025 Armbian_community_25.8.0-trunk.8_Orangepizero3_bookworm_current_6.12.23_minimal.img.xz btw thanks much (to all contributors) for updating Armbian to 25.x for OrangePi Zero 3 (and likely means works for Zero 2W) as wel I moved them to production already as I got another report they are working - so they are the same, but also community build images are mixed with those links ... this needs to be fixed eventually. Thank you for comprehensive testings. Here is image for 2w if anyone have it laying around: https://fi.mirror.armbian.de/incoming/igorpecovnik/orangepizero2w/archive/ 0 Quote
Michael Robinson Posted 12 hours ago Posted 12 hours ago /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.5.1 for Orange Pi Zero2W running Armbian Linux 6.12.23-current-sunxi64 Packages: Ubuntu stable (noble) Updates: Kernel upgrade enabled and 17 packages available for upgrade Support: DIY (community maintained) IPv4: (LAN) 192.168.***.***, 192.168.***.*** (WAN) ***.***.***.*** IPv6: *** Performance: Load: 11% Up time: 4 min Local users: 3 Memory usage: 24% of 1.93G CPU temp: 45°C Usage of /: 10% of 58G Commands: Configuration : armbian-config Upgrade : armbian-upgrade Monitoring : htop orangepi@orangepizero2w:~$ It boots into xfce wifi works, eth works and hdmi work. 2gb board with keyboard plugged into expansion board. 1 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.