Search the Community

My Armbian paste is at https://paste.armbian.com/yamakinoce This is an OrangePi Zero Plus, with an H3, not an H5 or an H2. I see all kinds of problems here but don't know how to fix them. It seems the DTB is just wrong for this board. For one, there are interrupts showing up in /proc/interrupts for HDMI and LCD, but this physical board has *neither* of those. It has an Ethernet PHY but neither the kernel nor uboot see it. It also has a Wifi but the kernel does not see that either. Does a correct DTB exist for this board? What is its name? I vaguely remember a couple ways to force the kernel and uboot to use a different DTB than what it calculates, but I would need to know if such a DTB exists in the first place. Thanks!

Just installed armbain for a orangepi zero plus 2 H3 setup the root and usernames credentials. I am able to login under root in putty, but sudo armbain-config is not found.

I just installed the image located here and am unable to get a bluetooth keyboard and mouse to connect. https://www.armbian.com/orange-pi-zero-plus-2-h3/ And used armbian-config -> Network -> Enable bluetooth. Here's the output of some common debugging commands I found in the forums. root@orangepizeroplus2-h3:~# lsusb Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@orangepizeroplus2-h3:~# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no root@orangepizeroplus2-h3:~# root@orangepizeroplus2-h3:~# sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2023-07-11 21:43:39 EDT; 21min ago Docs: man:bluetoothd(8) Main PID: 2945 (bluetoothd) Status: "Running" Tasks: 1 (limit: 828) Memory: 424.0K CPU: 283ms CGroup: /system.slice/bluetooth.service └─2945 /usr/lib/bluetooth/bluetoothd Jul 11 21:43:39 orangepizeroplus2-h3 systemd[1]: Starting Bluetooth service... Jul 11 21:43:39 orangepizeroplus2-h3 bluetoothd[2945]: Bluetooth daemon 5.64 Jul 11 21:43:39 orangepizeroplus2-h3 systemd[1]: Started Bluetooth service. Jul 11 21:43:39 orangepizeroplus2-h3 bluetoothd[2945]: Starting SDP server Jul 11 21:43:39 orangepizeroplus2-h3 bluetoothd[2945]: Bluetooth management interface 1.22 initialized root@orangepizeroplus2-h3:~# hcitool scan Device is not available: No such device root@orangepizeroplus2-h3:~# I also ran armbianmonitor -U > monitor.txt The results of which are attached to this message. It seems like the bluetooth service comes up, but it doesn't see any bluetooth devices. Can anyone point me in the right direction? monitor.txt

Hi! I am trying to use Armbian 23.5 Jammy XFCE for new Orange Pi Zero Plus 2. I have TTL-USB connection through Serial port. In pyutty window i see log U-Boot SPL 2022.07-armbian (May 27 2023 - 19:28:04 +0000) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (May 27 2023 - 19:28:04 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero Plus 2 DRAM: 512 MiB Core: 65 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: No ethernet found. ** Reading file would overwrite reserved memory ** Failed to load '/boot/boot.bmp' There is no valid bmp file at the given address starting USB... Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1d000: USB EHCI 1.00 scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 4121 bytes read in 4 ms (1005.9 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 180 bytes read in 3 ms (58.6 KiB/s) 16682525 bytes read in 693 ms (23 MiB/s) 8477464 bytes read in 355 ms (22.8 MiB/s) Found mainline kernel configuration 33498 bytes read in 10 ms (3.2 MiB/s) 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo 4185 bytes read in 6 ms (680.7 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 45000000 Kernel image @ 0x42000000 [ 0x000000 - 0x815b18 ] ## Loading init Ramdisk from Legacy Image at 43400000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 16682461 Bytes = 15.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49017000, end 49fffddd ... OK Loading Device Tree to 48fa6000, end 49016fff ... OK Starting kernel ... and this is all. My orange can not boot propertly. Is it possible to do something? Other image... Please help!