I am using an Orange Pi Zero 2W with a graphical user interface (GUI). I downloaded and installed the official Orange Pi Zero 2W image.

Unfortunately, I keep running into a Wi-Fi connection issue. After booting, the system repeatedly asks me to enter my Wi-Fi password. If I don’t enter it, I have no internet connection.

What’s interesting is:

If I disable and re-enable Wi-Fi in the network manager, it automatically reconnects to the known network without asking for the password again.

Alternatively, a system reboot also restores the Wi-Fi connection automatically.

I have already seen online that this seems to be a known issue, but I haven’t found a proper or permanent solution so far.

Has anyone experienced similar behavior or knows how to configure Wi-Fi so that it connects reliably and permanently without repeatedly asking for the password?

Thanks in advance!

I am looking for a specific legacy image for the Orange Pi Zero 2W: Armbian 23.02.2 Bullseye with Kernel 5.10.160.

The reason I need this specific version is to use the device as a USB UVC (Webcam) gadget via ConfigFS. On the newer 6.6/6.12 mainline kernels, I am facing a "Permission Denied" error when trying to write to hHeight, even as root. After researching, it seems this is a known kernel-level restriction in newer versions, and the legacy 5.10 kernel is the most stable for UVC gadget functionality.

I’ve checked the current archive mirrors but could only find the 6.6.x versions. Could anyone provide an official archive or a reliable mirror link for the following image? Filename: Armbian_23.02.2_Orangepizero2w_bullseye_legacy_5.10.160.img.xz

Thank you for your help.

I'm trying to get an ST7735S LCD display working with my Orange Pi Zero 2 (H616). This setup was working correctly with older Armbian kernels, but after a recent update, I can no longer get the SPI device to appear.

I have already tried a couple of different configuration methods without success.

System Information:

Board: Orange Pi Zero 2 (H616)

Display: ST7735S (SPI)

Kernel Version: Linux orangepizero2 6.12.43-current-sunxi64 #2 SMP Wed Aug 20 16:30:58 UTC 2025 aarch64 GNU/Linux

I have recently updated armbian-config by running the update from the script itself.

Attempt 1: Using armbianEnv.txt

My first attempt was to edit /boot/armbianEnv.txt and add the required overlays. Here is my configuration:

verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
rootdev=UUID=aef396b8-ac79-477c-b797-466fc4d881a6
rootfstype=ext4
overlays=sun50ih616spidev1_0 sun50ih616spidev1_1 sun50ih616spispidev sun50ih616tft35_spi
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

After rebooting with this configuration, the device nodes are not created. The output of ls /dev/spidev* is empty.

Attempt 2: Using a custom user overlay

Next, I tried creating a custom Device Tree Overlay. I created the file /boot/overlay-user/sp1-spidev.dts with the following content:

/dts-v1/;
/plugin/;

/ {
    compatible = "allwinner,sun50i-h616";
    
    fragment@0 {
        target = <&spi1>;
        __overlay__ {
            status = "okay";
            pinctrl-names = "default";
            #address-cells = <1>;
            #size-cells = <0>;
            
            spidev@0 {
                compatible = "spidev";
                reg = <0>;
                spi-max-frequency = <50000000>;
            };
        };
    };
};

I then added sp1-spidev to the overlays line in armbianEnv.txt.

This method seems to be partially working. After a reboot, I can see the SPI master controller:

$ ls /sys/class/spi_master/
spi0  spi1

However, the spidev device is still missing. ls /dev/spidev* is still empty.

Diagnostic Information

Here is the output of dmesg filtered for "spi". It seems to refer to spi0, not spi1 which I am trying to configure, but I'm including it for completeness.

$ dmesg | grep -i spi
[    2.821043] spi-nor spi0.0: supply vdd not found, using dummy regulator

My Question

I don't understand why the /dev/spidev* device is not being created, even when the spi1 master appears to be correctly enabled via the overlay. It seems like the spidev driver is not binding to the device.

Since this worked on older kernels, has the method for enabling SPI devices changed? What is the correct procedure now? Is there something I'm missing in my overlay file or configuration?

Thank you for your help

I have two Orange Pi Zero 2 for two years, I didn't know what to do with it.

Yesterday I  have installed Armbian_25.5.1_Orangepizero2_noble_current_6.12.23.

The serial was a bit buggy during installation (display + key press), I have used option -L with screen:

 

screen -L /dev/ttyUSB0 115200

Thank you for your great work !

i did not have this problem compiling the same module for Armbian lepotato (amlogic)

Where do I get the kernel source for my Orangepi Zero 2? 

Linux orangepizero2 6.12.20-current-sunxi64 #1 SMP Sat Mar 22 19:54:28 UTC 2025 aarch64 GNU/Linux

linux-headers-current-sunxi64/bookworm,now 25.2.3 arm64 [installed]
  Armbian Linux current headers 6.12.20-current-sunxi64

linux-image-current-sunxi64/bookworm,now 25.2.3 arm64 [installed]
  Armbian Linux current kernel image 6.12.20-current-sunxi64

I spent the whole day trying to boot without a microSD, and I finally got it, using the Orange Pi Zero SPI boot tutorial, with a few adjustments.

First of all, you’ll need a microSD card. I used this Armbian version Armbian_24.11.1_Orangepizero2_noble_current_6.6.62_minimal.img.xz

Once the system has booted from the microSD:

sudo apt update && sudo apt upgrade -y
reboot

After the system reboots, we need to check if the SPI flash is detected:

cat /proc/mtd
#It should return something like:
dev:    size   erasesize  name
mtd0: 00200000 00001000 "spi0.0"
#Double-check with:
ls -l /dev/mtd*
#You should get something like:
crw------- 1 root root 90, 0 Apr 10 19:34 /dev/mtd0  
crw------- 1 root root 90, 1 Apr 10 19:34 /dev/mtd0ro  
brw-rw---- 1 root disk 31, 0 Apr 10 19:34 /dev/mtdblock0

/dev/mtd/
total 0  
drwxr-xr-x 2 root root 60 Apr 10 19:34 by-name

If you see a device at /dev/mtd0 or /dev/mtd/by-name/spi0.0, you can flash U-Boot to the SPI.

# Create an empty image
sudo dd if=/dev/zero count=2048 bs=1K | tr '\000' '\377' > spi.img

# Write U-Boot to the image
sudo dd if=/usr/lib/linux-u-boot-current-orangepizero2/u-boot-sunxi-with-spl.bin of=spi.img bs=1k conv=notrunc

# Flash the image to SPI
sudo flashcp -v spi.img /dev/mtd0 
# Or /dev/mtd/by-name/spi0.0

Now it's time to plug in the USB drive (SSD or flash drive):

# Install Armbian to the USB stick, pendrive or SSD
# Follow the instructions in the menu, default values are usually fine
# DON'T REBOOT the device after this step
sudo nand-sata-install

# Mount the USB stick
sudo mount /dev/sda1 /mnt

# Copy (overwrite) the /boot directory
sudo cp -a /boot /mnt

# Now edit /mnt/boot/boot.cmd and set the correct root device:

setenv rootdev "/dev/sda1"

#Then generate the new boot.scr

sudo mkimage -C none -A arm -T script -d /mnt/boot/boot.cmd /mnt/boot/boot.scr

#Finally, edit armbianEnv.txt to update the rootdev by UUID:

blkid /dev/sda1

#Copy the UUID and update this line rootdev=UUID=your-usb-uuid

nano /mnt/boot/armbianEnv.txt

Now the moment of truth:

sudo shutdown -Fh now

Disconnect power and remove the microSD card.

Reconnect the power adapter and the system should boot from the USB drive.

If there's no sign of life, it's highly recommended to use a UART adapter to debug. Some boards require a jumper between GPIO pins 13 and 14 to boot from SPI — on my board (V1.5), this was not necessary.

I attached 2 boot logs (with good BT appears and no BT appears), I hope it will help to find out the issue.

boot_log_bt_good_02.zip

boot_log_bt_bad_02.zip

IR + controller : https://es.aliexpress.com/item/1005005651928240.html?spm=a2g0o.order_list.order_list_main.5.21a9194dT8Becw&gatewayAdapt=glo2esp

MPR121: https://es.aliexpress.com/item/1005005097989944.html?spm=a2g0o.order_list.order_list_main.11.21a9194dT8Becw&gatewayAdapt=glo2esp

Bluetooth speaker, but i would use the chip that comes with orange pi .

My answer is that i have all of these working inside a raspberrie pi 3 b 1.2, with python to detect the mpr121 pulsations and ir pulsations and manage connection Bluetooth, my problem is that I want to be sure that works, and actually the orange pi zero 2w its soo good cause comes already with antenna, so good, cause my project going to be Bluetooth intensive, its more powerful, comes with usb-c, its perfect for what i need,

but my main problem is that there's soooo difficult to find any guides about gpio config, or test with devices like the ir or mpr121, so It's possible to make this setup with the orange py zero 2, if it, there's somewhere with an extense guide on how to use it, or at least someone that know's it (I can pay for the help).

Thank you very much. 

Apologies for my English....

Unfortunately i have no connection by cable, only with Wifi and possibly it is only the Wifi connection which isn't working anymore?

I found the following entries in /var/log/kern (which are the latest entries until the device restarts):

2025-02-10T19:54:40.037397+01:00 orangepizero2 kernel: [86427.304061] unisoc_wifi unisoc_wifi wlan0: sprdwl_report_connection sm_state (5), status: (2)!
2025-02-10T19:54:40.037459+01:00 orangepizero2 kernel: [86427.304105] unisoc_wifi unisoc_wifi wlan0: sprdwl_report_connection KNAECKEBROED failed status code:1!
2025-02-10T19:54:40.365435+01:00 orangepizero2 kernel: [86427.632069] sprdwl:sprdwl_fc_add_share_credit, 536, mode:1 closed, index:0, share it
2025-02-10T19:54:55.573468+01:00 orangepizero2 kernel: [86442.837864] warning: `iwconfig' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211

is this a common issue with one of the latest updates or kernel?  

Here the link to the actual armbianmonitor -u  from this device:

https://paste.next.armbian.com/runuloneco

Best regards,

Chris

I'm struggling to get gpio_keys working.

I'm trying to use the overlay, which I have attached below, but after reboot there is no event node listed in "/dev/input/". (There is only one node named mice.)

Inspecting dmesg, I found the following error messages:

[    1.529891] sun50i-h616-pinctrl 300b000.pinctrl: pin PC8 already requested by gpio-keys-user; cannot claim for 300b000.pinctrl:72
[    1.529917] gpio-keys gpio-keys-user: failed to get gpio: -22
[    1.529926] gpio-keys: probe of gpio-keys-user failed with error -22

Inspecting the dts file of my board (orange pi zero 2), I found that PC5,PC6 and PC8 are already listed as mmc2-pins, but mmc2 is disabled, so I don't think that this is the issue. However, I have no idea what else might be wrong.

Any help?

Attachements:

custom-keys.dts Overlay:

/dts-v1/;                                                                                                                                                                                                          
/plugin/;                                                                                                                                                                                                          
                                                                                                                                                                                                                   
/ {                                                                                                                                                                                                                
  compatible = "allwinner,sun50i-h616";                                                                                                                                                                            
                                                                                                                                                                                                                   
  fragment@0 {                                                                                                                                                                                                     
    target = <&pio>;                                                                                                                                                                                               
    __overlay__ {                                                                                                                                                                                                  
      custom-buttons: custom-buttons {                                                                                                                                                                           
        pins = "PC5","PC6","PC8";                                                                                                                                                                                  
        function = "gpio_in";                                                                                                                                                                                      
        bias-pull-up;                                                                                                                                                                                              
      };                                                                                                                                                                                                           
    };                                                                                                                                                                                                             
  };                                                                                                                                                                                                               
                                                                                                                                                                                                                   
  fragment@1 {                                                                                                                                                                                                     
    target-path = "/";                                                                                                                                                                                             
    __overlay__ {                                                                                                                                                                                                  
      gpio-keys-user {                                                                                                                                                                                             
        compatible = "gpio-keys";                                                                                                                                                                                  
        pinctrl-names = "default";                                                                                                                                                                                 
        pinctrl-0 = <&custom-buttons>;                                                                                                                                                                            
                                                                                                                                                                                                                   
        play_button {                                                                                                                                                                                              
          label = "GPIO Key 1";                                                                                                                                                                                 
          linux,code = <25>;                                                                                                                                                                                       
          gpios = <&pio 0 69 1>;                                                                                                                                                                                   
        };                                                                                                                                                                                                         
        vol_up_button {                                                                                                                                                                                            
          label = "GPIO Key 2";                                                                                                                                                                               
          linux,code = <22>;                                                                                                                                                                                       
          gpios = <&pio 0 70 1>;                                                                                                                                                                                   
        };                                                                                                                                                                                                         
        vol_down_button {                                                                                                                                                                                          
          label = "GPIO Key 3";                                                                                                                                                                             
          linux,code = <32>;                                                                                                                                                                                       
          gpios = <&pio 0 72 1>;                                                                                                                                                                                   
        };                                                                                                                                                                                                         
      };                                                                                                                                                                                                           
    };                                                                                                                                                                                                             
  };                                                                                                                                                                                                               
};                                                                                                                                                                                                                 

Hey folks, I have a really weird issue where any time I try to `cat` any of the cpufreq files or use any of the cpufreq commands, it just hangs indefinitely. I've made sure that everything is up to date, reinstalled cpufreq, and because I have 2 of the same board, have confirmed that it's an issue with both of my Zero 2s.
I also ran `strace` on one of the cpufreq commands and found that it's getting hung on a write step:

openat(AT_FDCWD, "/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor", O_WRONLY) = 3
write(3, "ondemand", 8

Other than this, the device has been doing just fine. Any advice on this is welcome!

OrangePi Zero2
Armbian (24.11.1)
aarch64 6.6.62-current-sunxi64

(also attempted on the latest edge version of the kernel)

I used this post as a reference, and got quite far. But, I'm stuck on something that I believe I undestand, but don't know how to resolve. 

I don't believe this is a probleme specific to my board though.

What I've done so far with success is both install and run a pre-built Armbian Image on this board, as well as build my own image and run it.  Both work perfectly.

Now, I'm attempting to apply the RT patch and build a fresh image (or even just a Kernel) to get the FULL REALTIME kernel support working. 

However, the build system fails after the kernel is built sucesfully, as it is unable to find the resulting kernel image generated.

I belive the issue is simply that when the RT .patch is applied and configured to the kernel, it builds a kernel file with an alterered filename.  

Instead of 6.6.65-current-sunxi64 It creates 6.6.65-rt47-current-sunxi64  

As a result, the build process for the kernel stage fails as it's unable to find the file it is expecting to find.

Here is what I have done, and what outputs I am finding.

As stated, It was a success with A locally built clean Armbian

./compile.sh BOARD=orangepizero2w BRANCH=current RELEASE=bookworm BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no AUFS=no KERNELBRANCH='tag:v6.6.65'

System booted up and ran as normal.

$ uname -a 
inux orangepizero2w 6.6.65-current-sunxi64 #2 SMP Wed Dec 11 15:13:43 UTC 2024 aarch64 GNU/Linux

I then attempted to apply the PREEMPT_RT kernel patch.

download and gunzip

https://cdn.kernel.org/pub/linux/kernel/projects/rt/6.6/patch-6.6.65-rt47.patch.gz

into the directory userpatches/kernel/archive/sunxi-6.6

Then a kernel-configure step 

Worth noting that I do see this patch file applied in the output of the following command.

./compile.sh BOARD=orangepizero2w BRANCH=current RELEASE=bookworm KERNELBRANCH='tag:v6.6.65' kernel-config

Where I proceeded to enable the full REALTIME kernel (4th option).  

General setup -> Preemption Mode -> Fully Preemptible Kernel (Real-Time)

Finally followed with a compile command. 

./compile.sh BOARD=orangepizero2w BRANCH=current RELEASE=bookworm BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_CONFIGURE=no AUFS=no KERNELBRANCH='tag:v6.6.65'

The part of the build output that I beleive is relevant is this. It shows the failure, and what I believe is an indication of why it fails.  It appears that the build script it is not aware of needing to find the file name that has the rt47 portion.

🐳|🔨]     INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h616-i2c1-pi.dtbo
[🐳|🔨]     INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h616-i2c2-pi.dtbo
[🐳|🔨]     INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h616-gpu.dtbo
[🐳|🔨]     INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-a64-fixup.scr
[🐳|🔨]     INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h5-fixup.scr
[🐳|🔨]     INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h6-fixup.scr
[🐳|🔨]     INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/sun50i-h616-fixup.scr
[🐳|🔨]     INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/README.sun50i-a64-overlays
[🐳|🔨]     INSTALL /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/dtbs/allwinner/overlay/README.sun50i-h5-overlays
[🐳|🔨]   make[1]: Nothing to be done for 'install'.
[🐳|🔨]   make: Nothing to be done for 'install'.
[🐳|🌱] Kernel built in [ 95 seconds - 6.6.65-sunxi64 ]
[🐳|🌱] Packaging kernel [ sunxi64 linux-sunxi64-current ]
[🐳|🌱] Kernel .deb package version [ 6.6.65-S943e-Dfa7d-P3e46-Caa1fH5c21-HK01ba-Vc222-B59f0-R448a ]
[🐳|🌱] Packaging linux-image [ sunxi64 linux-sunxi64-current ]
[🐳|🔨]   [ 26M]  /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/image/boot
[🐳|🔨]   ├── [215K]  config-6.6.65-rt47-current-sunxi64
[🐳|🔨]   ├── [3.4M]  System.map-6.6.65-rt47-current-sunxi64
[🐳|🔨]   └── [ 22M]  vmlinuz-6.6.65-rt47-current-sunxi64
[🐳|🔨]   
[🐳|🔨]     26M used in 0 directories, 3 files
[🐳|🌱] Kernel-built image filetype [ vmlinuz-6.6.65-current-sunxi64: cannot open `/armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/image/boot/vmlinuz-6.6.65-current-sunxi64' (No such file or directory) ]
[🐳|🔨]   ls: cannot access '/armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/image/boot/vmlinuz-6.6.65-current-sunxi64': No such file or directory
[🐳|🔨]   /armbian/.tmp/work-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0/kernel_dest_install_dir-44x4J/image/boot:
[🐳|🔨]   total 26220
[🐳|🔨]   drwxrwxr-x 2 root root      100 Dec 30 17:08 .
[🐳|🔨]   drwxrwxr-x 3 root root       60 Dec 30 17:07 ..
[🐳|🔨]   -rw-rw-r-- 1 root root   220621 Dec 30 17:08 config-6.6.65-rt47-current-sunxi64
[🐳|🔨]   -rw-rw-r-- 1 root root  3564498 Dec 30 17:08 System.map-6.6.65-rt47-current-sunxi64
[🐳|🔨]   -rw-rw-r-- 1 root root 23056392 Dec 30 17:08 vmlinuz-6.6.65-rt47-current-sunxi64
[🐳|💥] Error 2 occurred in main shell [ at /armbian/lib/functions/logging/runners.sh:211
    run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211
        run_host_command_logged() --> lib/functions/logging/runners.sh:193
   kernel_package_callback_linux_image() --> lib/functions/compilation/kernel-debs.sh:221
              create_kernel_deb() --> lib/functions/compilation/kernel-debs.sh:131
   prepare_kernel_packaging_debs() --> lib/functions/compilation/kernel-debs.sh:72
                 kernel_package() --> lib/functions/compilation/kernel.sh:248
                  do_with_hooks() --> lib/functions/general/extensions.sh:567
                do_with_logging() --> lib/functions/logging/section-logging.sh:81
   kernel_prepare_build_and_package() --> lib/functions/compilation/kernel.sh:171
                 compile_kernel() --> lib/functions/compilation/kernel.sh:100
   artifact_kernel_build_from_sources() --> lib/functions/artifacts/artifact-kernel.sh:240
    artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34
       obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280
       build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:392
    main_default_build_packages() --> lib/functions/main/build-packages.sh:106
   full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:31
          do_with_default_build() --> lib/functions/main/default-build.sh:42
         cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25
        armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136
                 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176
                           main() --> compile.sh:50
 ]
[🐳|💥] Cleaning up [ please wait for cleanups to finish ]
[🐳|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0.log.ans ]
[🐳|🌿] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-3b1e65cb-74c9-47f6-aa6c-d7787497b9b0.log.ans https://paste.armbian.com/log ]
[💥] -------------Docker run failed after 152s-------------------------- [ 🐳 failed ]
[🌱] Cleaning up [ please wait for cleanups to finish ]
 ~/devel/personal/Armbian/build │ main !1                                                                                           

Thanks for any help with this. 

I hope I've provided enough information to make sense of what I'm attempting to do.

Tried to add 1wire, PPS and SPI , but can't work.

maybe help someone.

sun50i-h616-orangepi-zero2.dts

I would like to present Archian, the bastard child of Armbian & Arch.

Why … well, the project I am working on needed current versions of phosh & plasma-mobile and the versions on jammy/bookworm were quite old. The OPi supplied image was quite flaky so I had to find a way to mash these together. And this is the result.

It does need to be run as root !

The script has 3 arguments:

init - downloads the armbian image file, arch rootfs and arch packages. You need to then write the image to an SD-CARD
install - this installs arch over the armbian image on the SD-Card
finish - run this option on a booted image as root
 

It has limited/no error checking so run this at your own risk.

A wise/cautious person would run the install commands manually as it could really mess up your host system if it goes badly.

It could be easily modified to work with different boards but OPi Zero 2W is what I have.

Don't forget to edit the script before running it so that ‘things’ point to where you want them.

The root password is root.

You will need an external screen & keyboard to use it as networking wont work until it is fully installed.

Have a play and let me know any issues.
 

archian.sh

Everything come from a try to create a docker compose project. Armbian 24.8.4 bookworm on OrangePI zero 2 - Network forwarding doesn't work:
```
version: '3.6'
services:
  db:
    image: mariadb:10.3
    environment:
      MYSQL_ROOT_PASSWORD: secret
  phpmyadmin:
    image: phpmyadmin
    restart: always
    ports:
      - 8080:80
    environment:
      - PMA_HOSTS=db
```

=> FROM test-db-1 => test-db-1 3306
```
docker exec -ti test-db-1 bash -c 'timeout 0.5 echo -n 2>/dev/null < /dev/tcp/test-db-1/3306 && echo "open" || echo "closed"'
-----------
open
-----------
```

=> FROM test-phpmyadmin-1 => test-db-1 3306
```
docker exec -ti test-phpmyadmin-1 bash -c 'timeout 0.5 echo -n 2>/dev/null < /dev/tcp/test-db-1/3306 && echo "open" || echo "closed"'
-----------
closed
-----------
```

lsb_release -a
No LSB modules are available.
Distributor ID:    Debian
Description:    Armbian 24.8.4 bookworm
Release:    12
Codename:    bookworm

uname -a
Linux xxxxxx-pre 6.6.44-current-sunxi64 #1 SMP Sat Aug  3 06:54:42 UTC 2024 aarch64 GNU/Linux
```

OrangePI Zero v2

Network forwarding doesn't work

### How to reproduce?

```
ip -4 addr show scope global
2: end0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet 192.168.1.135/24 metric 100 brd 192.168.1.255 scope global dynamic end0
       valid_lft 587718sec preferred_lft 587718sec

cat /proc/sys/net/ipv4/ip_forward
1

iptables -A PREROUTING -t nat -i lo -p udp --dport 2222 -j DNAT --to 127.0.0.1:22
iptables -A PREROUTING -t nat -i lo -p tcp --dport 2222 -j DNAT --to 127.0.0.1:22
iptables -A FORWARD -p tcp -d 127.0.0.1 --dport 2222 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -m limit --limit 3/minute --limit-burst 3 -j LOG --log-prefix "IPT FORWARD packet"
iptables -A POSTROUTING -t nat -j MASQUERADE -o lo
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A INPUT -j ACCEPT
iptables -A OUTPUT -j ACCEPT
iptables -A FORWARD -j ACCEPT
```

ssh -l root -p 22 localhost => OK
ssh -l root -p 2222 localhost => KO

```
iptables -A INPUT -j ACCEPT
iptables -A OUTPUT -j ACCEPT
iptables -A FORWARD -j ACCEPT
iptables -A PREROUTING -t nat -i end0 -p udp --dport 2222 -j DNAT --to 192.168.1.135:22
iptables -A PREROUTING -t nat -i end0 -p tcp --dport 2222 -j DNAT --to 192.168.1.135:22
iptables -A FORWARD -p tcp -d 192.168.1.135 --dport 2222 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -m limit --limit 3/minute --limit-burst 3 -j LOG --log-prefix "IPT FORWARD packet"
iptables -A POSTROUTING -t nat -j MASQUERADE -o end0
iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
```

ssh -l root -p 22 192.168.1.135 => OK
ssh -l root -p 2222 192.168.1.135 => KO

### Branch

main (main development branch)

### On which host OS are you running the build script and observing this problem?

Ubuntu 24.04 Noble

### Are you building on Windows WSL2?

- [ ] Yes, my Ubuntu/Debian/OtherOS is running on WSL2

### Relevant log URL

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

I'm building a DTS overlay for a SPI Touchscreen and every pin I try to use is showing this error:
 

[    1.441808] sun50i-h616-pinctrl 300b000.pinctrl: pin PC11 already requested by 5011000.spi; cannot claim for 300b000.pinctrl:75

[    1.441817] sun50i-h616-pinctrl 300b000.pinctrl: pin-75 (300b000.pinctrl:75) status -22

[    1.441829] sun6i-spi 5011000.spi: cannot register SPI master

I'm trying to configure my touchscreen dts to use the SPI1.0 & SPI1.1.  However, the pins exposed on the headers are all allocated for device use under 300b000.pinctrl.

How do you allocate header pins for another use?

I need 5 pins + SPI1 for the touchscreen to work.

My dts

/dts-v1/;
/plugin/;

/ {
	compatible = "allwinner,sun8i-h3";

	fragment@0 {
		target = <&pio>;
		__overlay__ {
			spi1_cs1: spi1_cs1 {
				pins = "PC11"; 
				function = "gpio_out";
				output-high;
			};

			opiz_display_pins: opiz_display_pins {
				pins = "PC9", "PC6", "PC5";
				function = "gpio_out";
			};

			ads7846_pins: ads7846_pins {
				pins = "PH6";
				function = "irq";
			};
		};
	};

	fragment@1 {
		target = <&spi1>;
		__overlay__ {
			#address-cells = <1>;
			#size-cells = <0>;
			status = "okay";
			pinctrl-1 = <&spi1_cs1>;
			pinctrl-names = "default", "default";
			cs-gpios= <0>, <&pio 2 11 0>; /* PH9 PC11 */

                        opizdisplay: opiz-display@0 {
                                reg = <0>; /* Chip Select 0 */
                                compatible = "ilitek,ili9341";
                                spi-max-frequency = <16000000>;
                                status = "okay";
                                pinctrl-names = "default";
                                pinctrl-0 = <&opiz_display_pins>;
                                rotate = <90>;
                                bgr = <0>;
                                fps = <10>;
                                buswidth = <8>;
                                dc-gpios = <&pio 2 6 0>;      /* PC6 */
                                reset-gpios = <&pio 2 9 1 >; /* PC9 */
                                led-gpios=<&pio 2 5 0>;      /*  PC5 */
                                debug=<0>;
                        };

			ads7846: ads7846@1 {
				reg = <1>; /* Chip Select 1 */
				compatible = "ti,ads7846";
				spi-max-frequency = <500000>;
				status = "okay";
				pinctrl-names = "default";
				pinctrl-0 = <&ads7846_pins>;
				interrupt-parent = <&pio>;
				interrupts = <7 6 2>; /* PH6 IRQ_TYPE_EDGE_FALLING */
				pendown-gpio = <&pio 7 6 0>; /* PH6 */
				/* driver defaults, optional */
				ti,x-min = /bits/ 16 <0>;
				ti,y-min = /bits/ 16 <0>;
				ti,x-max = /bits/ 16 <0x0FFF>;
				ti,y-max = /bits/ 16 <0x0FFF>;
				ti,pressure-min = /bits/ 16 <0>;
				ti,pressure-max = /bits/ 16 <0xFFFF>;
				ti,x-plate-ohms = /bits/ 16 <400>;
			};
		};

	};

};

I really apologise if the information is out there and I just haven't found it.

I was looking to buy a board for a small embedded GUI application and this one seems to fit the bill.

I would like to use Wi-Fi, Bluetooth and HDMI.

Is there a list of what is working or not working on each build/version? (This is probably a more general question to Armbian for any device)

The only thing I could find is this: 

But it's not that recent.

On the download page: https://www.armbian.com/orange-pi-zero-2/ under specifications it does list, Bluetooth and Wi-Fi but I'm not sure if this means its now working?

I also saw some forum posts talk about old builds, where can they be found, all I can see is this (linked on the download page): https://fi.mirror.armbian.de/archive/orangepizero2/archive/ and it only has 1 version.

One last question, if Wi-Fi or Bluetooth don't work, does that only mean onboard Wi-Fi and Bluetooth and that a dongle would work?

Thanks!

I've been using OPiZ2 for about 2 years as Pi-hole in gravity-sync with another one (Orange Pi 3 LTS running Open Media Vault with no problem).

Today I found out it was dead, no connection and just a blank screen. It must have happened in the past few days, because I checked it on sunday and it was up and running.

I'm almost sure I was using it with Armbian_22.11.0-trunk_Orangepizero2_sid_edge_6.0.6.

i have extracted the sd card and checked it on Windows with Diskinternals reader and Minitool Partition Wizard, no problem found.

The most recent files and folders have been modified on 2024-07-12, eleven days ago, much prior to my checking, so there is no info about the last hours/days.

When I first installed Armbian, I used a version that would brick the OpiZ2 with apt upgrade, but a long time has passed and I don't remember if that issue was fixed.

Now, can I somehow resuscitate this install? If not, can I clone/recover at least the pi-hole/unbound/gravitysinc settings? And what version of Armbian should I use? 

I've downloaded Armbian_24.5.3_Orangepizero2_bookworm_current_6.6.31_minimal, but I came here to ask before doing something.

The display is one I bought from Amazon

Hosyond 2.8 Inches TFT LCD Touch Screen Shield Display Module 320x240 SPI Serial ILI9341 with Touch Pen Compatible with Arduino R3/Mega2560 Development Board

This document was very helpful getting the display set up on the OPZero 2:
https://tienda.tettsa.gt/wp-content/uploads/2022/08/OrangePi_Zero2_H616_User-manual_v3.7.pdf

I still don't have the touch part working.  If anyone has success getting 2 selects working with SPI1 on OPZero2 and touch working, let me know.

The basic steps to getting the SPI LCD to work are:

1) wire up the display to the OPZero2
 

2.8 Inch TFT SPI 240x320 => OPZero2

1 - VCC   =>  (1) 3.3v
2 - GND  =>   (6) Gnd
3 - CS      =>   (24) Spi1 CS
4 - RESET  =>   (7) GPIO 6
5 - DC    =>     (11) GPIO 1
6 - SDI (MOSI) =>    (19) Spi1 MOSI
7 - SCLK  =>  (23) Spi1 CLK
8 - LED    =>    (13) GPIO 0
9 - SDO (MISO) =>    (21) Spi1 MISO
10 - T_CLK     
11 - T_CS       
12 - T_DIN    
13 - T_DO    
14 - T_IRQ    
 

2) Install Armbian_23.5.2_Orangepizero2_bookworm_legacy_4.9.318_minimal - must be legacy kernel to work 4.9 is OK

3) sudo apt install fbi kbd armbian-config

4) sudo armbian-config

set up desktop

now to make the LCD work and start on boot

5) sudo nano /boot/armbianEnv.txt

overlays=spi-spidev
param_spidev_spi_bus=1
param_spidev_spi_cs=1
extraargs=fbcon=map:1

6) sudo nano /etc/modules-load.d/fbtft.conf

fbtft
fbtft_device

7) sudo nano etc/modprobe.d/fbtft.conf

options fbtft_device custom name=fb_ili9341 gpios=dc:70,reset:73,led:69 speed=16000000 busnum=1 cs=1 bgr=1 txtbuflen-32768 fps=10 rotate=90
 

😎 sudo dpkg-reconfigure console-setup

select UTF-8

select Guess optimal character set

select terminus

select 6/12

9) sudo nano /usr/share/X11/xorg.conf.d/99-fbdev.conf

Section "Device"
  Identifier "myfb"
  Driver "fbdev"
  Option "fbdev" "/dev/fb1"
EndSection

Now when it boots it should boot to the SPI LCD Display

does anyone have experience with video playback? is playing 1080p in anyway possible? Which image would you recommend for Orange Pi Zero 2 H616 1GB? Is a desktop x11 mandatory?

I am new to Armbian and Linux in general. I am using an OrangePi Zero 2 (H616) board and need to enable the hardware UART. To do this, I tried using the simplest method I could find: running the command armbian-config -> System -> Hardware. However, in the section where I should find options for peripherals to enable, I found nothing.

I have tried installing different versions of Armbian, but nothing changed:

- Armbian_24.5.1_Orangepizero2_jammy_current_6.6.31.img
- Armbian_24.2.1_Orangepizero2_bookworm_current_6.6.16.img
- Armbian_23.8.3_Orangepizero2_bookworm_current_6.1.53.img
- Armbian_24.5.1_Orangepizero2_noble_current_6.6.31.img

I also tried installing the system on different SD cards, but nothing changed.

Please tell me, what am I doing wrong?

Thank you.

Linux orangepizero2 6.6.31-current-sunxi64 #1 SMP Fri May 17 10:02:40 UTC 2024 aarch64 GNU/Linux 

Trying to restrict ssh to listen on  IP assigned to end0 only, but it is ignoring the ListenAddress 192.168.8.1:22 directive. It listens on all interfaces, which I do not want.

sudo service ssh status
● ssh.service - OpenBSD Secure Shell server
     Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
     Active: active (running) since Thu 2024-05-30 16:10:42 UTC; 22s ago
TriggeredBy: ● ssh.socket
       Docs: man:sshd(8)
             man:sshd_config(5)
    Process: 1362 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
   Main PID: 1363 (sshd)
      Tasks: 1 (limit: 932)
     Memory: 1.3M
        CPU: 231ms
     CGroup: /system.slice/ssh.service
             └─1363 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

May 30 16:10:41 orangepizero2 systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
May 30 16:10:42 orangepizero2 sshd[1363]: debug3: already daemonized
May 30 16:10:42 orangepizero2 sshd[1363]: debug3: oom_adjust_setup
May 30 16:10:42 orangepizero2 systemd[1]: Started ssh.service - OpenBSD Secure Shell server.
May 30 16:10:42 orangepizero2 sshd[1363]: debug1: Set /proc/self/oom_score_adj from 0 to -1000
May 30 16:10:42 orangepizero2 sshd[1363]: debug2: fd 3 setting O_NONBLOCK
May 30 16:10:42 orangepizero2 sshd[1363]: Server listening on :: port 22.

orangepizero2:~$ sudo armbianmonitor -r
Installing RPi-Monitor. This can take up to 5 minutes. Be patient pleaseE: Unable to locate package rpimonitor
/usr/bin/armbianmonitor: line 697: /usr/share/rpimonitor/scripts/updatePackagesStatus.pl: No such file or directory
/usr/bin/armbianmonitor: line 193: /etc/rpimonitor/template/raspbian.conf: No such file or directory
/usr/bin/armbianmonitor: line 196: cd: /etc/rpimonitor/: No such file or directory
sed: can't read /etc/rpimonitor/template/temperature.conf: No such file or directory
sed: can't read /etc/rpimonitor/template/cpu.conf: No such file or directory
sed: can't read /etc/rpimonitor/template/version.conf: No such file or directory

Can I do something to resolve this or do I just need to have patience

Hello

I've tried both Bookworm and Jammy (also older version). None boot up - nothing. The red LED starts blinking after after a few seconds.

Yes the SD card is good, Yes the power supply is good (both work with the official images). Yes I've tried different SD card and power supplies.

Is there an image/version someone can confirm was tested and works?

thank you

I have tried setting the following settings in /boot/armbianEnv.txt

overlay_prefix=sun8i-h6
overlay=i2c0 i2c1 i2c2

However, I am not able to use i2c tools to read the DS3231.

Any suggestions are welcomed. Thank you in advance!

The board has startup issue, the serial output seems to load some files in wrong format:

U-Boot SPL 2021.10-armbian (Feb 26 2022 - 17:45:38 +0000)
DRAM: 1024 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.6(debug):510155aa-dirty
NOTICE:  BL31: Built : 17:45:34, Feb 26 2022
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a082570, model: OrangePi Zero2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP305 on RSB
INFO:    PMIC: aldo1 voltage: 3.300V
INFO:    PMIC: aldo2 voltage: 3.300V
INFO:    PMIC: aldo3 voltage: 3.300V
INFO:    PMIC: bldo1 voltage: 1.800V
INFO:    PMIC: dcdcd voltage: 1.500V
INFO:    PMIC: dcdce voltage: 3.300V
INFO:    Changed devicetree to reserve BL31 memory.
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 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

U-Boot 2021.10-armbian (Feb 26 2022 - 17:45:38 +0000) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: OrangePi Zero2
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@4020000: 0
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   phy interface7
eth0: ethernet@5020000
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
2612 bytes read in 2 ms (1.2 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
131 bytes read in 1 ms (127.9 KiB/s)
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
12522800 bytes read in 518 ms (23.1 MiB/s)
Failed to load '/boot/uImage'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk mmc@4020000.blk...
Found 2 disks
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
ethernet@5020000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-02-00-86-a3-61-86
ethernet@5020000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
ethernet@5020000 Waiting for PHY auto negotiation to complete..

I tried another image: Armbian_22.02.2_Orangepizero2_focal_legacy_4.9.255.img.xz

This one works okay

sudo nmcli device show
GENERAL.DEVICE:                         end0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         02:00:9E:C4:55:73
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     Wired connection 1
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/2
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         10.11.12.140/24
IP4.GATEWAY:                            10.11.12.1
IP4.ROUTE[1]:                           dst = 10.11.12.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]:                           dst = 0.0.0.0/0, nh = 10.11.12.1, mt = 100
IP4.ROUTE[3]:                           dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
IP4.DNS[1]:                             10.11.12.1
IP4.DOMAIN[1]:                          lan
IP4.SEARCHES[1]:                        lan
IP6.ADDRESS[1]:                         fe80::573f:9a69:7cbf:6308/64
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 1024

GENERAL.DEVICE:                         lo
GENERAL.TYPE:                           loopback
GENERAL.HWADDR:                         00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.STATE:                          100 (connected (externally))
GENERAL.CONNECTION:                     lo
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         ::1/128
IP6.GATEWAY:                            --

I've also tried loading the edge kernel (Linux opizero2 6.4.12-edge-sunxi64 #1 SMP Wed Aug 23 15:32:56 UTC 2023 aarch64 GNU/Linux) and that's not working either.

My question is, what capabilities are supported by Armbian on the zero2. What is working and tested?

- wifi

-Bluetooth

-HDMI

-sound

-gpio

-i2c, spi

It would be helpful to know what works today on zero2 to avoid duplicating efforts on zero3. Any changes being developed for zero3 should also be tested on zero2.

//192.168.1.2/Descargas /mnt/Descargas/ cifs uid=1000,gid=1000,guest 0 0

tried _netdev to wait for network and then mount with the same results

//192.168.1.2/Descargas /mnt/Descargas/ cifs uid=1000,gid=1000,guest, _netdev 0 0

If I run mount -a it works, tried to add it into root crontab with 

* * * * /bin/mount -a

Still, no results, even schedule reboot doesn't work

30 5 * * * /sbin/shutdown -r

I even tried to make an executable script on /etc/network/if-up.d with mount -a on it that was supposed to run after network is up but nothing.

I'm no linux expert but not a total newbie either, this has me really stressed, I don´t know if my OS doesn't run any auto script or what is going on, I even tried Armbian_23.02.2_Orangepizero2_jammy_legacy_4.9.318.img today but it doesn´t start, my Opi Zero 2 LED doesn´t turn on even after 20 minutes.

Any help or right direction will be apreciated. Thanks in advance

Best regards

SOLUTION: I had to add sudo before cron commands, I feel so stupid right now, I'm leaving this here if it helps someone

30 5 * * * sudo /sbin/shutdown -r
* * * * * sudo /bin/mount -a

Any suggestions how to solve that?

When testing on the stock images provided orange pi I am able to connect with both the Orangepizero2_3.0.6_ubuntu_jammy_server_linux5.16.17.img and Orangepizero2_2.2.0_ubuntu_focal_server_linux4.9.170 images it works. Connecting also works on the Amrbian focal_legacy images I tried.

If I use a fresh SD card (Sandisk 16GB A1) then it works ok.

My question is regarding the SD card imaging ( i am using Balena-etcher), is there something change inside the SDcard after reflash so that OPI does not recognise the booting part anymore??

Let me think about how to descript this situation......

I have a movable disk and mount in path:

 /mnt/sba1

It happened first time when I using a program called "Syncthing" , I try to sync my file into my movable disk.

I get lot of files in my directory. When the "Syncthing" start scanning. the system will stuck.

Not that kind of whole system stuck, but only if you trying to read anything about /mnt/sda1.

If you trying to "df -h", you'll get stuck.

"fdisk -l", stuck.

"cd /mnt/sba1", stuck again.

"mount" "umount" "lsblk" all will be stuck.

Such like this ......

Reboot the system is only way to restore. No need to unplug the disk. Just reboot and get normal.

So I tried writing a Golang program, the program will read huge number of files in my disk instantly. Yes, stuck again.

So I came to the conclusion: When I try to read a large number of files, there will be a malfunction.

I thought it's about usb driver problem, so I change "UAS" to "USB-Storage".  Still stuck again and again. ( With this topic : How can I change usb-disk driver "UAS" to "usb-storage" ? ) 

I change 3 Orangepi Zero2 board and 3 different movable disk, Still like this.

Right now,I'm writing this post, the situation has reappeared, again......

root@OPIZ2-0146:/# ulimit -n
102400

root@OPIZ2-0146:/# ulimit -a
real-time non-blocking time  (microseconds, -R) unlimited
core file size              (blocks, -c) 0
data seg size               (kbytes, -d) unlimited
scheduling priority                 (-e) 0
file size                   (blocks, -f) unlimited
pending signals                     (-i) 3756
max locked memory           (kbytes, -l) 123522
max memory size             (kbytes, -m) unlimited
open files                          (-n) 102400
pipe size                (512 bytes, -p) 8
POSIX message queues         (bytes, -q) 819200
real-time priority                  (-r) 0
stack size                  (kbytes, -s) 8192
cpu time                   (seconds, -t) unlimited
max user processes                  (-u) 3756
virtual memory              (kbytes, -v) unlimited
file locks                          (-x) unlimited

root@OPIZ2-0146:/# cat /proc/sys/fs/file-max
9223372036854775807

How can I locate the cause of this problem?

https://imola.armbian.com/dl/orangepizero2/archive/

There are no current images for Orange Pi Zero 2 at https://www.armbian.com/cf7stdb-entries/orange-pi-zero-2/

The Zero image does not work. I did manage to find an archived legacy image based on some posts from 2022 however nothing on the new kernel works.

My question is this: Is there a reason why these devices require unique builds? I understand the kernel drivers may not be in 6.x for this board however I'm more referring to the huge number of builds that need to be supported.

Thanks,

Jason

U-Boot 2018.05-armbian (Jan 10 2023 - 07:48:03 +0000) Xunlong Software

[00.535]CPU:   Allwinner H616
[00.538]Model: Orange Pi Zero 2
I2C:   ready
[00.542]DRAM:  1 GiB
Relocation Offset is: 35ec7000
[00.583]secure enable bit: 0
[00.586]PMU: AXP806
[00.591]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[00.773]sunxi overlay merged okqv
[00.776]drv_disp_init
[00.805]__clk_enable: clk is null.
tv_init()950 fetch tv0 err.
[00.811]drv_disp_init finish
[00.813]gic: sec monitor mode
[00.819]flash init start
[00.821]workmode = 0,storage type = 1
[00.824]MMC:     0
[00.825][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.832][mmc]: get sdc_type fail and use default host:tm1.
[00.842][mmc]: Using default timing para
[00.846][mmc]: SUNXI SDMMC Controller Version:0x40200
[00.872][mmc]: card_caps:0x3000000a
[00.876][mmc]: host_caps:0x3000003f
[00.881]sunxi flash init ok
[00.884]Loading Environment from FAT... 
[00.888][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.894][mmc]: get sdc_type fail and use default host:tm1.
[00.904][mmc]: Using default timing para
[00.908][mmc]: SUNXI SDMMC Controller Version:0x40200 
** Bad device mmc 1 **
Failed (-5)
[00.919]usb burn from boot
delay time 0
weak:otg_phy_config
[00.932]usb prepare ok
[01.104]usb sof ok
[01.106]usb probe ok
[01.108]usb setup ok
set address 0x12
set address 0x12 ok
[04.114]do_burn_from_boot usb : have no handshake
[04.118]boot_gui_init:start
190 bytes read in 11 ms (16.6 KiB/s)
Set HDMI disp_mode to 1080p60
190 bytes read in 10 ms (18.6 KiB/s)
Set fb0_width to 1280
Set fb0_height to 720
[04.430]boot_gui_init:finish
[04.433]bmp_name=/boot/boot.bmp
230454 bytes read in 32 ms (6.9 MiB/s)
[04.481]update dts
Net:   [04.484]No ethernet found.
Hit any key to stop autoboot:  1 0 
no mmc device at slot 1
[05.520][mmc]: card_caps:0x3000000a
[05.523][mmc]: host_caps:0x3000003f
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3259 bytes read in 13 ms (244.1 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
190 bytes read in 10 ms (18.6 KiB/s)
262144 bytes read in 38 ms (6.6 MiB/s)
** File not found /boot/dtb/allwinner/overlay/-fixup.scr **
7225390 bytes read in 618 ms (11.1 MiB/s)
** File not found /boot/Image **
Unknown command 'booti' - try 'help'
SCRIPT FAILED: continuing...
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
armbian# 

After some investigation it appears that the problem occurs when updating armbian-bsp-cli-orangepizero2 to version 22.11.4, holding the package on version 22.11.3 prevent the bug and allow to update all other packages, including kernel updates (last check on 31.01.2023) without issue.

Thank you for your great work on this distribution and have a nice day.

Also, if I upgrade the kernel with apt-get upgrade in version 4.9.318, the card does not boot afterward and gets a "No ethernet found" error.

Versions I tried :

Armbian_22.11.3_Orangepizero2_jammy_legacy_4.9.318.img [Worked but no wifi connection]

Armbian_22.02.2_Orangepizero2_bullseye_legacy_4.9.255.img [Works good]

Armbian_22.08.7_Orangepizero2_jammy_edge_5.19.16.img [Not working !!]

Armbian_22.11.1_Orangepizero2_jammy_edge_6.0.10_minimal.img [Not working !!]

Armbian_23.02.0-trunk.0141_Orangepizero2_jammy_edge_6.1.2.img [Not working !!]

Armbian_23.02.0-trunk.0191_Orangepizero2_jammy_edge_6.1.6_minimal.img [Not working !!]

Armbian_23.02.0-trunk.0236_Orangepizero2_jammy_edge_6.1.9_minimal.img [Not working !!]

Armbian_23.02.0-trunk_Orangepizero2_lunar_edge_6.1.8.img [Not working !!]

Armbian_23.02.0-trunk_Orangepizero2_lunar_edge_6.1.8_minimal.img [Not working !!]

I tried to build it myself and the result still does not work the same.

Armbian_23.02.0-trunk_Orangepizero2_jammy_current_5.15.90.img [I have built but not working]

Image:

Armbian 22.11 Jammy
Kernel 4.9.y, Size: 445Mb, Release date: Jan 10, 2023
SHA hash | PGP signature

I'm working on a few Orange Pi Zero 2 v1.5's, and they won't finish booting on a few of the most recent images. (Just testing jammy right now to keep things consistent)

Boot Successfully:

• Armbian_22.11.3_Orangepizero2_jammy_edge_6.1.4
• Armbian_22.05.3_Orangepizero2_jammy_edge_5.17.11

Do Not Boot Successfully:

• Armbian_23.02.2_Orangepizero2_jammy_edge_6.1.11
• Armbian_22.11.1_Orangepizero2_jammy_edge_6.0.10
• Armbian_22.08.7_Orangepizero2_jammy_edge_5.19.16

Typically, when the boot fails, all I get is this over serial with no LED's:

U-Boot SPL 2022.07-armbian (Feb 17 2023 - 23:33:06 +0000)
DRAM: 2048 MiB
Trying to boot from MMC1

But occasionally (once every 10-20 boots) I get this with the red LED:

U-Boot SPL 2022.07-armbian (Feb 17 2023 - 23:33:06 +0000)
DRAM: 1024 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.8(debug):a84636ad-dirty
NOTICE:  BL31: Built : 23:33:00, Feb 17 2023
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a0903e0, model: OrangePi Zero2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP305 on RSB
INFO:    PMIC: aldo1 voltage: 3.300V
INFO:    PMIC: aldo2 voltage: 3.300V
INFO:    PMIC: aldo3 voltage: 3.300V
INFO:    PMIC: bldo1 voltage: 1.800V
INFO:    PMIC: bldo2 voltage: 1.800V
INFO:    PMIC: dcdcd voltage: 1.500V
INFO:    PMIC: dcdce voltage: 3.300V
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 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 2022.07-armbian (Feb 17 2023 - 23:33:06 +0000) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: OrangePi Zero2
DRAM:  1 GiB
Core:  52 devices, 18 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   phy interface8
eth0: ethernet@5020000
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
2669 bytes read in 2 ms (1.3 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
131 bytes read in 2 ms (63.5 KiB/s)
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
10693326 bytes read in 444 ms (23 MiB/s)
Failed to load '/boot/uImage'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
SCRIPT FAILED: continuing...
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
ethernet@5020000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-02-00-2d-bc-f3-17
ethernet@5020000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Retrieving file: pxelinux.cfg/00000000

I've read most of the other posts about this board, and I'm curious if there's some kind of difference in the v1.5 HW. It seems like v1.5 seems to have more issues, and there are significant visual differences (v1.5, v1.2). Unfortunately OrangePi only published schematics for v1.3, so I'm not sure how to tell what exactly would have changed. 

I've been trying to get my DS1820 temp sensor working but cant seem to get the device to show up om my orange pi zero 2 running Orange Pi 3.0.6 Bullseye

Most info i find starts our with run armbian-config but orangpi doesnt have it. All i got is the orangepi-config but it doesnt have the "Go to the “system” section and select “Hardware” then activate w1-gpio."

so i was looking arround and found you need to enable overlays in  /boot/armbianEnv.txt  but dont have it aswell but the alternative  /boot/orangepiEnv.txt

there i add the 

 /boot/orangepiEnv.txt

overlay_prefix=sun50i-h616
overlays=w1-gpio
param_w1_pin=PC8                          <<<<< not sure about the pin numers
param_w1_pin_int_pullup=1

looking at the output i would say PC8 is correct pin name.

root@orangepizero2:~# gpio readall
 +------+-----+----------+------+---+   H616   +---+------+----------+-----+------+
 | GPIO | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | GPIO |
 +------+-----+----------+------+---+----++----+---+------+----------+-----+------+
 |      |     |     3.3V |      |   |  1 || 2  |   |      | 5V       |     |      |
 |  229 |   0 |    SDA.3 |  OFF | 0 |  3 || 4  |   |      | 5V       |     |      |
 |  228 |   1 |    SCL.3 |  OFF | 0 |  5 || 6  |   |      | GND      |     |      |
 |   73 |   2 |      PC9 |  OFF | 0 |  7 || 8  | 0 | OFF  | TXD.5    | 3   | 226  |
 |      |     |      GND |      |   |  9 || 10 | 0 | OFF  | RXD.5    | 4   | 227  |
 |   70 |   5 |      PC6 | ALT5 | 0 | 11 || 12 | 0 | OFF  | PC11     | 6   | 75   |
 |   69 |   7 |      PC5 | ALT5 | 0 | 13 || 14 |   |      | GND      |     |      |
 |   72 |   8 |      PC8 |  OFF | 0 | 15 || 16 | 0 | OFF  | PC15     | 9   | 79   |
 |      |     |     3.3V |      |   | 17 || 18 | 0 | OFF  | PC14     | 10  | 78   |
 |  231 |  11 |   MOSI.1 |  OFF | 0 | 19 || 20 |   |      | GND      |     |      |
 |  232 |  12 |   MISO.1 |  OFF | 0 | 21 || 22 | 0 | OFF  | PC7      | 13  | 71   |
 |  230 |  14 |   SCLK.1 |  OFF | 0 | 23 || 24 | 0 | OFF  | CE.1     | 15  | 233  |
 |      |     |      GND |      |   | 25 || 26 | 0 | OFF  | PC10     | 16  | 74   |
 |   65 |  17 |      PC1 |  OFF | 0 | 27 || 28 |   |      |          |     |      |
 |  272 |  18 |     PI16 | ALT2 | 0 | 29 || 30 |   |      |          |     |      |
 |  262 |  19 |      PI6 |  OFF | 0 | 31 || 32 |   |      |          |     |      |
 |  234 |  20 |     PH10 | ALT3 | 0 | 33 || 34 |   |      |          |     |      |
 +------+-----+----------+------+---+----++----+---+------+----------+-----+------+
 | GPIO | wPi |   Name   | Mode | V | Physical | V | Mode | Name     | wPi | GPIO |
 +------+-----+----------+------+---+   H616   +---+------+----------+-----+------+

if i understaand correct i need to add the kernel moduels by doing:

modprobe w1-therm
modprobe w1-gpio

after reboot i should see the device show up? using:

ls /sys/bus/w1/devices

but go nothing.

so i check :

root@orangepizero2:~# cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 0-287, parent: platform/300b000.pinctrl, 300b000.pinctrl:
 gpio-76  (                    |red:power           ) out lo
 gpio-77  (                    |green:status        ) out hi
 gpio-80  (                    |usb1-vbus           ) out hi
 gpio-166 (                    |cd                  ) in  lo IRQ ACTIVE LOW
 gpio-210 (                    |reset               ) out hi ACTIVE LOW

gpiochip1: GPIOs 352-383, parent: platform/7022000.pinctrl, 7022000.pinctrl:

it seems like im missing something fundamentally? can some one point me in the write direction?

[FAILED] Failed to start Access poi…server for Wi-Fi and Ethernet.
See 'systemctl status hostapd.service' for details.
[  OK  ] Finished OpenVPN service.
openvpn.service
[  OK  ] Started /etc/rc.local Compatibility.
rc-local.service
rpc-statd-notify.service
[  OK  ] Started Notify NFS peers of a restart.
[  OK  ] Finished Permit User Sessions.
systemd-user-sessions.service
[  OK  ] Started Bluetooth service.
bluetooth.service
[  OK  ] Reached target Bluetooth Support.
         Starting Hold until boot process finishes up...
         Starting Terminate Plymouth Boot Screen...
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
         Starting Hostname Service...
[  OK  ] Finished resolvconf-pull-resolved.service.
[  OK  ] Finished Hold until boot process finishes up.
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Finished Terminate Plymouth Boot Screen.
[   19.330374] proc: unrecognized mount option "hidepid=invisible" or missing value

Armbian 22.11.3 Jammy ttyS0 

orangepizero2 login: [   22.434473] WCN_ERR: dumpmem_rx_callback open  error no.-21 retry:1
[   22.608383] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   22.726784] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   22.845212] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   22.963555] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   23.081861] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   23.200187] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   23.318572] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   23.437000] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   23.555333] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   23.673674] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   23.792089] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   23.910506] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   24.028921] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   24.147344] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   24.265778] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   24.384217] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   24.502618] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   24.621046] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   24.739480] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   24.857837] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   24.976168] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   25.094571] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   25.212879] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   25.331223] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   25.449659] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   25.568189] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   25.686517] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   25.804861] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   25.923205] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   26.041563] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   26.159978] sunxi-mmc sdc1: smc 1 p1 err, cmd 53, RD DTO !!
[   26.166416] sunxi-mmc sdc1: retry:set phase failed or over retry times
[   26.173888] sunxi-mmc sdc1: retry:give up
[   26.178527] sdiohal err:dt read fail ret:-110, system_addr=0x4024f000
[   26.187652] WCN_ERR: mdbg_dump_data dump memory error:-110
[   26.193952] WCN_ERR: read HCI_ARM_WR_RD_MODE reg error:-1
[   26.200105] WCN_ERR: mdbg_dump_data dump memory error:-1
[   26.206191] WCN_ERR: mdbg_dump_data dump memory error:-1
[   26.212273] WCN_ERR: mdbg_dump_data dump memory error:-1
[   26.218347] WCN_ERR: mdbg_dump_data dump memory error:-1
[   26.224430] WCN_ERR: mdbg_dump_data dump memory error:-1
[   26.230510] WCN_ERR: mdbg_dump_data dump memory error:-1
[   26.236538] WCN_ERR: mdbg_dump_data dump memory error:-1
[   26.242632] WCN_ERR: mdbg_dump_data dump memory error:-1
[   26.248709] WCN_ERR: mdbg_dump_data dump memory error:-1
[   26.254770] WCN_ERR: mdbg_dump_data dump memory error:-1
[   35.679877] WCN_ERR: Not dump again!

Unfortunately, having no cable to connect it to a monitor or serial, my diagnostics are quite limited - after booting dmesg looks mostly clean, but maybe in case it's a semi-common problem and someone could direct me to a solution? Or if not, suggest what's the best way to diagnose further?

(OS: Orange Pi 3.0.6 Bullseye with Linux 5.16.17-sun50iw9 )

I'm flash u-boot-sunxi-with-spl.bin into spi-flash,  but have error No Bootable media found. Sorry for my English

How to disable private ethernet MAC on OPZ2? Router says my device has one.

With the Orange Pi image (which looks strangely like armbian), once the device is booted, the red led goes off, and the green led turns on.  With the armbian image, the red light stays on, and the HDMI output does not turn on in the CLI image. This led me initially to think this board was not working.  Once I hooked up a USB to Serial interface, I noticed it booted. Well, at least when the SD card was seated correctly, but that is a hardware problem.  

Once booted, `armbian-config` does not show the wifi interface settings.   

I am asking because I am a little bit confused because of this

This topic is more than 2 years old but I see no update.

Release date: Jan 10, 2023

Legacy kernel has more or less full hardware support, while mainline lack functions such is wireless, HDMI, ...

https://www.armbian.com/orange-pi-zero-2/

Looking for maintainer!

But now my OPIZ2 would not boot anymore, nothing seen in the serial communication either. No red/green LED ever lit.

Sadly, this is my 2nd dead OPIZ2.....

Seeking for help if those boards are still recoverable...

I've changed the hostname through sudo armbian-config but just cannot connect to it via hostname. 

Has anyone managed to get this working?

I realise the included files must be pre-processed before compiled and have tried numerous approaches all which failed miserably by not being able to move beyond the following error.

Error: dt-bindings/interrupt-controller/arm-gic.h:6.1-8 syntax error
FATAL ERROR: Unable to parse input tree

The relevant lines in arm-gic.h:

#ifndef _DT_BINDINGS_INTERRUPT_CONTROLLER_ARM_GIC_H
#define _DT_BINDINGS_INTERRUPT_CONTROLLER_ARM_GIC_H

#include <dt-bindings/interrupt-controller/irq.h>

I’m unsure whether or not this is a cpp or dtc error.

The paths seem to be resolved:

alistair@orangepizero2:/boot/dtb-5.15.46-sunxi64/allwinner$ ls -l dt-bindings
lrwxrwxrwx 1 root root 58 Jun 18 21:49 dt-bindings -> /usr/src/linux-headers-5.15.43-sunxi64/include/dt-bindings
alistair@orangepizero2:/boot/dtb-5.15.46-sunxi64/allwinner$ ls -l dt-bindings/interrupt-controller/arm-gic.h
-rw-r--r-- 1 root root 536 Jun 17 15:55 dt-bindings/interrupt-controller/arm-gic.h
alistair@orangepizero2:/boot/dtb-5.15.46-sunxi64/allwinner$

Perhaps the error is obvious, here one of the failed instructions:

alistair@orangepizero2:/boot/dtb-5.15.46-sunxi64/allwinner$ sudo gcc -I /boot/dtb/allwinner/ -E -nostdinc -undef -D__DTS__ -x assembler-with-cpp -o sun-h616-orangepi-zero2-b.dts.tmp sun-h616-orangepi-zero2-b.dts
alistair@orangepizero2:/boot/dtb-5.15.46-sunxi64/allwinner$ 

alistair@orangepizero2:/boot/dtb-5.15.46-sunxi64/allwinner$ sudo dtc -I dts -O dtb -o sun-h616-orangepi-zero2-b.dtb sun-h616-orangepi-zero2-b.dts.tmp
Error: dt-bindings/interrupt-controller/arm-gic.h:6.1-8 syntax error
FATAL ERROR: Unable to parse input tree
alistair@orangepizero2:/boot/dtb-5.15.46-sunxi64/allwinner$

Any help would be gratefully appreciated.

Best,

Alistair

Armbian 22.08 Bullseye
Kernel 5.19.y, Size: 388Mb, Release date: Oct 22, 2022

Bug report:

1: When i reboot my orangepi zero 2 , my devices will be power off.

2: I use the newest image , display nothing on screen. But i have an older version image. It display to screen by Micro-HDMI perfect.

3: Is possible to light up green LED after system start?

    I mean, when the device power on, red LED light up. It's nice. But if light the green LED up after system start up, I can know my system get no troubles and it's running now.

mkdir: cannot create directory ‘/root/.cache/oh-my-zsh’: Read-only file system
rm: cannot remove '/root/.zcompdump-orangepizero2-5.8': Read-only file system
zsh: locking failed for /root/.zsh_history: read-only file system: reading anyway

What is happening?!

Will there be a desktop version of Jammy for Orange pi Zero 2 available to download?

I'm using Jammy with a desktop on a Orange Pi One and it works fine.

Thanks

can someone help me, unfortunately i still have little knowledge of linux, thanks

[214]HELLO! BOOT0 is starting May 13 2020 14:10:04!
[219]BOOT0 commit : 593cf83
[222]set pll start
[224]periph0 has been enabled
[227]set pll end
[229]unknow PMU
[231]PMU: AXP806
[238]vaild para:8  select dram para0
[242]board init ok
[243]DRAM BOOT DRIVE INFO: V0.52
[247]the chip id is 0x5000
[249]chip id check OK
[252]DRAM_VCC set to 1500 mv
[256]write_leveling error
[258]read_calibration error
[262]write_leveling error
[265]read_calibration error
[269]write_leveling eration error
[449]read_calibration error
[453]read_calibration error
[457]read_calibration error
[461]read_calibration error
[464]read_calibration error
[468]read_calibration error
[472]read_calibration error
[475]retraining final error

Any tips for getting spi-double-spidev-cs.dts to work?

Thanks so much,

Is possible to solve problem ? After reboot command orange pi zero 2 not want start and it stay turner off  . I read article about changing R_WDOG instead of WDOG in ATF fix for different boad:

Thanks

[c.SerialPortPoc] type=1400 audit(0.0:532): avc: denied { read write } for name="ttyS5" dev="tmpfs" ino=2487 scontext=u:r:untrusted_app_27:s0:c512,c768 tcontext=u:object_r:serial_device:s0 tclass=chr_file permissive=1 app=SerialPortPoc.SerialPortPoc

Device: Orange Pi Zero 2, Android 10

[#] nft -f /dev/fd/63
/dev/fd/63:1:1-26: Error: Could not process rule: Operation not supported
...

Quick google search showed something concerning nf_tables module in kernel or something like this. (I'm not an experienced linux user).

Is there any chance to set up my OPi Z 2 with wg + nftables?

Thanks.

I have abandoned the Orangepizero2 I had bought months ago to use with Armbian, I have confused zero and zero 2.

Seeing new release, I have just downloaded/install Armbian 22.05 Jammy. Install is ok, good work, thank you !

The wireless interface seems not enabled, I have looked at dmesg output and nmtui-connect.

I could not find info about it, the board name doesn't help a lot. I understand the support of this board is pretty new.

Is there a known technic to enable the wifi ?

Have a nice day,

▒[100]HELLO! BOOT0 is starting May 13 2020 14:10:04!
[105]BOOT0 commit : 593cf83
[107]set pll start
[110]periph0 has been enabled
[113]set pll end
[115]unknow PMU
[117]PMU: AXP806
[124]vaild para:8  select dram para0
[127]board init ok
[129]DRAM BOOT DRIVE INFO: V0.52
[132]the chip id is 0x5000
[135]chip id check OK
[137]DRAM_VCC set to 1500 mv
[141]read_calibration error
[145]read_calibration error
[149]read_calibration error
[153]read_calibration error
[157]read_calibration error
[161]read_calibration error
[165]read_calibration error
[169]read_calibration error
[173]read_calibration error
[177]read_calibration error
[180]retraining final error
[184][AUTO DEBUG]32bit,1 ranks training success!
[192]DRAM CLK =720 MHZ
[194]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[200]Actual DRAM SIZE =1024 M
[203]DRAM SIZE =1024 MBytes, para1 = 30fa, para2 = 4000000, dram_tpr13 = 6041
[216]DRAM simple test OK.
[219]rtc standby flag is 0x0, super standby flag is 0x0
[224]dram size =1024
[226]*****dram handle ok****
[230]card no is 0
[231]sdcard 0 line count 4
[234][mmc]: mmc driver ver 2019-12-19 10:41
[238][mmc]: sdc0 spd mode error, 2
[242][mmc]: set f_max to 50M, set f_max_ddr to 25M
[247][mmc]: mmc 0 bias 0
[255][mmc]: Wrong media type 0x0
[258][mmc]: ***Try SD card 0***
[267][mmc]: HSSDR52/SDR25 4 bit
[270][mmc]: 50000000 Hz
[272][mmc]: 15200 MB
[274][mmc]: ***SD/MMC 0 init OK!!!***
[373]Loading boot-pkg Succeed(index=0).
[377]Entry_name        = u-boot
[386]Entry_name        = monitor
[390]Entry_name        = dtbo
[393]Entry_name        = dtb
[397]Jump to second Boot.
NOTICE:  BL3-1: v1.0(debug):9fecd83
NOTICE:  BL3-1: Built : 17:08:29, 2020-05-28
NOTICE:  BL3-1 commit: 8
ERROR:   Error initializing runtime service tspd_fast
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3

U-Boot 2018.05-orangepi (Mar 31 2022 - 11:47:20 +0800) Xunlong Software

[00.474]CPU:   Allwinner H616
[00.477]Model: Orange Pi Zero 2
I2C:   ready
[00.482]DRAM:  1 GiB
Relocation Offset is: 35ec7000
[00.522]secure enable bit: 0
[00.525]PMU: AXP806
[00.530]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[00.717]sunxi overlay merged okqv
[00.720]drv_disp_init
[00.748]__clk_enable: clk is null.
tv_init()950 fetch tv0 err.
[00.753]drv_disp_init finish
[00.756]gic: sec monitor mode
[00.761]flash init start
[00.763]workmode = 0,storage type = 1
[00.767]MMC:     0
[00.768][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.774][mmc]: get sdc_type fail and use default host:tm1.
[00.785][mmc]: Using default timing para
[00.788][mmc]: SUNXI SDMMC Controller Version:0x40200
[00.806][mmc]: card_caps:0x3000000a
[00.809][mmc]: host_caps:0x3000003f
[00.813]sunxi flash init ok
[00.816]Loading Environment from FAT...
[00.820][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.826][mmc]: get sdc_type fail and use default host:tm1.
[00.836][mmc]: Using default timing para
[00.840][mmc]: SUNXI SDMMC Controller Version:0x40200
** Bad device mmc 1 **
Failed (-5)
[00.851]usb burn from boot
delay time 0
weak:otg_phy_config
[00.864]usb prepare ok
[01.667]overtime
[01.671]do_burn_from_boot usb : no usb exist
[01.675]boot_gui_init:start
206 bytes read in 8 ms (24.4 KiB/s)
Set HDMI disp_mode to 1080p60
206 bytes read in 8 ms (24.4 KiB/s)
Set fb0_width to 1920
Set fb0_height to 1080
[01.976]boot_gui_init:finish
[01.978]bmp_name=/boot/boot.bmp
230456 bytes read in 105 ms (2.1 MiB/s)
[02.098]update dts
Net:   [02.101]No ethernet found.
Hit any key to stop autoboot:  0
no mmc device at slot 1
[03.128][mmc]: card_caps:0x3000000a
[03.131][mmc]: host_caps:0x3000003f
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2771 bytes read in 10 ms (270.5 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
206 bytes read in 8 ms (24.4 KiB/s)
8484924 bytes read in 3769 ms (2.1 MiB/s)
24129608 bytes read in 4252 ms (5.4 MiB/s)
## Booting kernel from Legacy Image at 41000000 ...
   Image Name:
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    24129544 Bytes = 23 MiB
   Load Address: 41000000
   Entry Point:  41000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8484860 Bytes = 8.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 497e8000, end 49fff7fc ... OK
   reserving fdt memory region: addr=48000000 size=1000000
## Linux machid: 00000000, FDT addr: 7be86d60

Starting kernel ...

▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒&[100]HELLO! BOOT0 is starting May 13 2020 14:10:04!
[105]BOOT0 commit : 593cf83
[107]set pll start
[110]periph0 has been enabled
[113]set pll end
[115]unknow PMU
[117]PMU: AXP806
[124]vaild para:8  select dram para0
[127]board init ok
[129]DRAM BOOT DRIVE INFO: V0.52
[133]the chip id is 0x5000
[135]chip id check OK
[137]DRAM_VCC set to 1500 mv
[141]read_calibration error
[145]read_calibration error
[149]read_calibration error
[153]read_calibration error
[157]read_calibration error
[161]read_calibration error
[165]read_calibration error
[169]read_calibration error
[173]read_calibration error
[177]read_calibration error
[180]retraining final error
[184][AUTO DEBUG]32bit,1 ranks training success!
[192]DRAM CLK =720 MHZ
[194]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[200]Actual DRAM SIZE =1024 M
[203]DRAM SIZE =1024 MBytes, para1 = 30fa, para2 = 4000000, dram_tpr13 = 6041
[216]DRAM simple test OK.
[219]rtc standby flag is 0x0, super standby flag is 0x0
[224]dram size =1024
[226]*****dram handle ok****
[230]card no is 0
[232]sdcard 0 line count 4
[234][mmc]: mmc driver ver 2019-12-19 10:41
[238][mmc]: sdc0 spd mode error, 2
[242][mmc]: set f_max to 50M, set f_max_ddr to 25M
[247][mmc]: mmc 0 bias 0
[255][mmc]: Wrong media type 0x0
[258][mmc]: ***Try SD card 0***
[267][mmc]: HSSDR52/SDR25 4 bit
[270][mmc]: 50000000 Hz
[272][mmc]: 15200 MB
[274][mmc]: ***SD/MMC 0 init OK!!!***
[375]Loading boot-pkg Succeed(index=0).
[378]Entry_name        = u-boot
[387]Entry_name        = monitor
[391]Entry_name        = dtbo
[394]Entry_name        = dtb
[398]Jump to second Boot.
NOTICE:  BL3-1: v1.0(debug):9fecd83
NOTICE:  BL3-1: Built : 17:08:29, 2020-05-28
NOTICE:  BL3-1 commit: 8
ERROR:   Error initializing runtime service tspd_fast
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3

U-Boot 2018.05-orangepi (Mar 31 2022 - 11:47:20 +0800) Xunlong Software

[00.475]CPU:   Allwinner H616
[00.477]Model: Orange Pi Zero 2
I2C:   ready
[00.482]DRAM:  1 GiB
Relocation Offset is: 35ec7000
[00.523]secure enable bit: 0
[00.525]PMU: AXP806
[00.530]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[00.717]sunxi overlay merged okqv
[00.721]drv_disp_init
[00.748]__clk_enable: clk is null.
tv_init()950 fetch tv0 err.
[00.754]drv_disp_init finish
[00.756]gic: sec monitor mode
[00.762]flash init start
[00.764]workmode = 0,storage type = 1
[00.767]MMC:     0
[00.769][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.775][mmc]: get sdc_type fail and use default host:tm1.
[00.785][mmc]: Using default timing para
[00.789][mmc]: SUNXI SDMMC Controller Version:0x40200
[00.807][mmc]: card_caps:0x3000000a
[00.810][mmc]: host_caps:0x3000003f
[00.813]sunxi flash init ok
[00.817]Loading Environment from FAT...
[00.820][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.826][mmc]: get sdc_type fail and use default host:tm1.
[00.837][mmc]: Using default timing para
[00.840][mmc]: SUNXI SDMMC Controller Version:0x40200
** Bad device mmc 1 **
Failed (-5)
[00.852]usb burn from boot
delay time 0
weak:otg_phy_config
[00.865]usb prepare ok
[01.668]overtime
[01.672]do_burn_from_boot usb : no usb exist
[01.676]boot_gui_init:start
206 bytes read in 15 ms (12.7 KiB/s)
Set HDMI disp_mode to 1080p60
206 bytes read in 9 ms (21.5 KiB/s)
Set fb0_width to 1920
Set fb0_height to 1080
[01.984]boot_gui_init:finish
[01.986]bmp_name=/boot/boot.bmp
230456 bytes read in 127 ms (1.7 MiB/s)
[02.128]update dts
Net:   [02.131]No ethernet found.
Hit any key to stop autoboot:  0
orangepi# ls -l /dev | grep -E 'sd|hd'
syntax error
orangep
orangepi# fdisk
Unknown command 'fdisk' - try 'help'
orangepi# help
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
bootz   - boot Linux zImage image from memory
cmp     - memory compare
colorbar- show colorbar
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
dhcp    - boot image via network using DHCP/TFTP protocol
echo    - echo args to console
editenv - edit environment variable
efex    - run to efex
env     - environment handling commands
erase   - erase FLASH memory
exit    - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
ext4load- load binary file from a Ext4 filesystem
ext4ls  - list files in a directory (default /)
ext4size- determine a file's size
ext4write- create a file in the root directory
false   - do nothing, unsuccessfully
fastboot- fastboot - enter USB Fastboot protocol
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fatsize - determine a file's size
fatwrite- write file into a dos filesystem
fdt     - flattened device tree utility commands
flinfo  - print FLASH memory information
fstype  - Look up a filesystem type
go      - start application at address 'addr'
gpt     - GUID Partition Table
help    - print command description/usage
i2c     - I2C sub-system
itest   - return true/false on integer compare
load    - load binary file from a filesystem
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loadx   - load binary file over serial line (xmodem mode)
loady   - load binary file over serial line (ymodem mode)
logo    - show default logo
loop    - infinite loop on address range
ls      - list files in a directory (default /)
md      - memory display
memtester- start application at address 'addr'
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mmc     - MMC sub system
mmcinfo - display MMC info
mw      - memory write (fill)
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
part    - disk partition related commands
pbread  - read data from private data
ping    - send ICMP ECHO_REQUEST to network host
poweroff- Perform POWEROFF of the device
printenv- print environment variables
protect - enable or disable FLASH write protection
pxe     - commands to get and boot from pxe files
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
save    - save file to a filesystem
saveenv - save environment variables to persistent storage
screen_char- show default screen chars
setenv  - set environment variables
setexpr - set environment variable as the result of eval expression
showvar - print local hushshell variables
size    - determine a file's size
sleep   - delay execution for some time
source  - run script from memory
sprite_test- do a sprite test
sunxi_axp- sunxi_axp sub-system
sunxi_bmp_info- manipulate BMP image data
sunxi_bmp_show- manipulate BMP image data
sunxi_card0_probe- probe sunxi card0 device
sunxi_flash- sunxi_flash sub-system
sunxi_nand_test- sunxi_nand_test sub systerm
sysboot - command to get and boot from syslinux files
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
timer_test- do a timer and int test
timer_test1- do a timer and int test
true    - do nothing, successfully
uburn   - do a burn from boot
version - print monitor, compiler and linker version
orangepi# fsck
Unknown command 'fsck' - try 'help'
orangepi# ls
ls - list files in a directory (default /)

Usage:
ls <interface> [<dev[:part]> [directory]]
    - List files in directory 'directory' of partition 'part' on
      device type 'interface' instance 'dev'.
orangepi# cd /
Unknown command 'cd' - try 'help'
orangepi# ls /
** No device specified **
orangepi# fstab
Unknown command 'fstab' - try 'help'
orangepi# tune2fs
Unknown command 'tune2fs' - try 'help'
orangepi# touch /forcefsck
Unknown command 'touch' - try 'help'
orangepi# help
?       - alias for 'help'
base    - print or set address offset
bdinfo  - print Board Info structure
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
bootz   - boot Linux zImage image from memory
cmp     - memory compare
colorbar- show colorbar
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
dhcp    - boot image via network using DHCP/TFTP protocol
echo    - echo args to console
editenv - edit environment variable
efex    - run to efex
env     - environment handling commands
erase   - erase FLASH memory
exit    - exit script
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
ext4load- load binary file from a Ext4 filesystem
ext4ls  - list files in a directory (default /)
ext4size- determine a file's size
ext4write- create a file in the root directory
false   - do nothing, unsuccessfully
fastboot- fastboot - enter USB Fastboot protocol
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fatsize - determine a file's size
fatwrite- write file into a dos filesystem
fdt     - flattened device tree utility commands
flinfo  - print FLASH memory information
fstype  - Look up a filesystem type
go      - start application at address 'addr'
gpt     - GUID Partition Table
help    - print command description/usage
i2c     - I2C sub-system
itest   - return true/false on integer compare
load    - load binary file from a filesystem
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loadx   - load binary file over serial line (xmodem mode)
loady   - load binary file over serial line (ymodem mode)
logo    - show default logo
loop    - infinite loop on address range
ls      - list files in a directory (default /)
md      - memory display
memtester- start application at address 'addr'
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mmc     - MMC sub system
mmcinfo - display MMC info
mw      - memory write (fill)
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
part    - disk partition related commands
pbread  - read data from private data
ping    - send ICMP ECHO_REQUEST to network host
poweroff- Perform POWEROFF of the device
printenv- print environment variables
protect - enable or disable FLASH write protection
pxe     - commands to get and boot from pxe files
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
save    - save file to a filesystem
saveenv - save environment variables to persistent storage
screen_char- show default screen chars
setenv  - set environment variables
setexpr - set environment variable as the result of eval expression
showvar - print local hushshell variables
size    - determine a file's size
sleep   - delay execution for some time
source  - run script from memory
sprite_test- do a sprite test
sunxi_axp- sunxi_axp sub-system
sunxi_bmp_info- manipulate BMP image data
sunxi_bmp_show- manipulate BMP image data
sunxi_card0_probe- probe sunxi card0 device
sunxi_flash- sunxi_flash sub-system
sunxi_nand_test- sunxi_nand_test sub systerm
sysboot - command to get and boot from syslinux files
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
timer_test- do a timer and int test
timer_test1- do a timer and int test
true    - do nothing, successfully
uburn   - do a burn from boot
version - print monitor, compiler and linker version
orangepi# reboot
Unknown command 'reboot' - try 'help'
orangepi# ▒▒[100]HELLO! BOOT0 is starting May 13 2020 14:10:04!
[105]BOOT0 commit : 593cf83
[107]set pll start
[110]periph0 has been enabled
[113]set pll end
[115]unknow PMU
[117]PMU: AXP806
[124]vaild para:8  select dram para0
[127]board init ok
[129]DRAM BOOT DRIVE INFO: V0.52
[132]the chip id is 0x5000
[135]chip id check OK
[137]DRAM_VCC set to 1500 mv
[141]read_calibration error
[145]read_calibration error
[149]read_calibration error
[153]read_calibration error
[157]read_calibration error
[161]read_calibration error
[165]read_calibration error
[169]read_calibration error
[173]read_calibration error
[177]read_calibration error
[180]retraining final error
[184][AUTO DEBUG]32bit,1 ranks training success!
[192]DRAM CLK =720 MHZ
[194]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[200]Actual DRAM SIZE =1024 M
[203]DRAM SIZE =1024 MBytes, para1 = 30fa, para2 = 4000000, dram_tpr13 = 6041
[216]DRAM simple test OK.
[219]rtc standby flag is 0x0, super standby flag is 0x0
[224]dram size =1024
[226]*****dram handle ok****
[230]card no is 0
[232]sdcard 0 line count 4
[234][mmc]: mmc driver ver 2019-12-19 10:41
[238][mmc]: sdc0 spd mode error, 2
[242][mmc]: set f_max to 50M, set f_max_ddr to 25M
[247][mmc]: mmc 0 bias 0
[255][mmc]: Wrong media type 0x0
[258][mmc]: ***Try SD card 0***
[267][mmc]: HSSDR52/SDR25 4 bit
[270][mmc]: 50000000 Hz
[272][mmc]: 15200 MB
[274][mmc]: ***SD/MMC 0 init OK!!!***
[373]Loading boot-pkg Succeed(index=0).
[377]Entry_name        = u-boot
[386]Entry_name        = monitor
[390]Entry_name        = dtbo
[393]Entry_name        = dtb
[397]Jump to second Boot.
NOTICE:  BL3-1: v1.0(debug):9fecd83
NOTICE:  BL3-1: Built : 17:08:29, 2020-05-28
NOTICE:  BL3-1 commit: 8
ERROR:   Error initializing runtime service tspd_fast
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3

U-Boot 2018.05-orangepi (Mar 31 2022 - 11:47:20 +0800) Xunlong Software

[00.474]CPU:   Allwinner H616
[00.476]Model: Orange Pi Zero 2
I2C:   ready
[00.481]DRAM:  1 GiB
Relocation Offset is: 35ec7000
[00.522]secure enable bit: 0
[00.524]PMU: AXP806
[00.529]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[00.716]sunxi overlay merged okqv
[00.720]drv_disp_init
[00.747]__clk_enable: clk is null.
tv_init()950 fetch tv0 err.
[00.753]drv_disp_init finish
[00.755]gic: sec monitor mode
[00.761]flash init start
[00.763]workmode = 0,storage type = 1
[00.766]MMC:     0
[00.768][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.774][mmc]: get sdc_type fail and use default host:tm1.
[00.784][mmc]: Using default timing para
[00.788][mmc]: SUNXI SDMMC Controller Version:0x40200
[00.806][mmc]: card_caps:0x3000000a
[00.809][mmc]: host_caps:0x3000003f
[00.812]sunxi flash init ok
[00.816]Loading Environment from FAT...
[00.819][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.825][mmc]: get sdc_type fail and use default host:tm1.
[00.836][mmc]: Using default timing para
[00.839][mmc]: SUNXI SDMMC Controller Version:0x40200
** Bad device mmc 1 **
Failed (-5)
[00.851]usb burn from boot
delay time 0
weak:otg_phy_config
[00.864]usb prepare ok
[01.667]overtime
[01.671]do_burn_from_boot usb : no usb exist
[01.675]boot_gui_init:start
206 bytes read in 8 ms (24.4 KiB/s)
Set HDMI disp_mode to 1080p60
206 bytes read in 8 ms (24.4 KiB/s)
Set fb0_width to 1920
Set fb0_height to 1080
[01.976]boot_gui_init:finish
[01.978]bmp_name=/boot/boot.bmp
230456 bytes read in 83 ms (2.6 MiB/s)
[02.076]update dts
Net:   [02.080]No ethernet found.
Hit any key to stop autoboot:  0
no mmc device at slot 1
[03.106][mmc]: card_caps:0x3000000a
[03.109][mmc]: host_caps:0x3000003f
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2771 bytes read in 11 ms (245.1 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
206 bytes read in 8 ms (24.4 KiB/s)
8484924 bytes read in 3720 ms (2.2 MiB/s)
24129608 bytes read in 4498 ms (5.1 MiB/s)
## Booting kernel from Legacy Image at 41000000 ...
   Image Name:
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    24129544 Bytes = 23 MiB
   Load Address: 41000000
   Entry Point:  41000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8484860 Bytes = 8.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Ramdisk to 497e8000, end 49fff7fc ... OK
   reserving fdt memory region: addr=48000000 size=1000000
## Linux machid: 00000000, FDT addr: 7be86d60

Starting kernel ...

▒[96]HELLO! BOOT0 is starting May 13 2020 14:10:04!
[101]BOOT0 commit : 593cf83
[103]set pll start
[106]periph0 has been enabled
[109]set pll end
[111]unknow PMU
[113]PMU: AXP806
[120]vaild para:1  select dram para0
[123]board init ok
[125]DRAM BOOT DRIVE INFO: V0.52
[128]the chip id is 0x5000
[131]chip id check OK
[133]DRAM_VCC set to 1500 mv
[137]read_calibration error
[141]read_calibration error
[145]read_calibration error
[149]read_calibration error
[153]read_calibration error
[157]read_calibration error
[161]read_calibration error
[165]read_calibration error
[169]read_calibration error
[173]read_calibration error
[175]retraining final error
[180][AUTO DEBUG]32bit,1 ranks training success!
[187]DRAM CLK =720 MHZ
[190]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[196]Actual DRAM SIZE =1024 M
[199]DRAM SIZE =1024 MBytes, para1 = 30fa, para2 = 4000000, dram_tpr13 = 6041
[212]DRAM simple test OK.
[215]rtc standby flag is 0x0, super standby flag is 0x0
[220]dram size =1024
[222]*****dram handle ok****
[226]card no is 0
[227]sdcard 0 line count 4
[230][mmc]: mmc driver ver 2019-12-19 10:41
[234][mmc]: sdc0 spd mode error, 2
[238][mmc]: set f_max to 50M, set f_max_ddr to 25M
[243][mmc]: mmc 0 bias 0
[251][mmc]: Wrong media type 0x0
[254][mmc]: ***Try SD card 0***
[263][mmc]: HSSDR52/SDR25 4 bit
[266][mmc]: 50000000 Hz
[268][mmc]: 15200 MB
[270][mmc]: ***SD/MMC 0 init OK!!!***
[369]Loading boot-pkg Succeed(index=0).
[373]Entry_name        = u-boot
[382]Entry_name        = monitor
[386]Entry_name        = dtbo
[389]Entry_name        = dtb
[393]Jump to second Boot.
NOTICE:  BL3-1: v1.0(debug):9fecd83
NOTICE:  BL3-1: Built : 17:08:29, 2020-05-28
NOTICE:  BL3-1 commit: 8
ERROR:   Error initializing runtime service tspd_fast
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3

U-Boot 2018.05-armbian (Jun 22 2022 - 07:19:38 +0000) Xunlong Software

[00.468]CPU:   Allwinner H616
[00.471]Model: Orange Pi Zero 2
I2C:   ready
[00.476]DRAM:  1 GiB
Relocation Offset is: 35ec7000
[00.516]secure enable bit: 0
[00.519]PMU: AXP806
[00.524]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[00.706]sunxi overlay merged okqv
[00.709]drv_disp_init
[00.738]__clk_enable: clk is null.
tv_init()950 fetch tv0 err.
[00.744]drv_disp_init finish
[00.746]gic: sec monitor mode
[00.752]flash init start
[00.754]workmode = 0,storage type = 1
[00.757]MMC:     0
[00.759][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.765][mmc]: get sdc_type fail and use default host:tm1.
[00.775][mmc]: Using default timing para
[00.779][mmc]: SUNXI SDMMC Controller Version:0x40200
[00.796][mmc]: card_caps:0x3000000a
[00.799][mmc]: host_caps:0x3000003f
[00.803]sunxi flash init ok
[00.806]Loading Environment from FAT...
[00.810][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.816][mmc]: get sdc_type fail and use default host:tm1.
[00.827][mmc]: Using default timing para
[00.830][mmc]: SUNXI SDMMC Controller Version:0x40200
** Bad device mmc 1 **
Failed (-5)
[00.841]usb burn from boot
delay time 0
weak:otg_phy_config
[00.855]usb prepare ok
[01.658]overtime
[01.662]do_burn_from_boot usb : no usb exist
[01.666]boot_gui_init:start
141 bytes read in 9 ms (14.6 KiB/s)
Set HDMI disp_mode to 1080p60
141 bytes read in 8 ms (16.6 KiB/s)
Set fb0_width to 1280
Set fb0_height to 720
[01.967]boot_gui_init:finish
[01.970]bmp_name=/boot/boot.bmp
230454 bytes read in 30 ms (7.3 MiB/s)
[02.013]update dts
Net:   [02.016]No ethernet found.
Hit any key to stop autoboot:  0
no mmc device at slot 1
[03.043][mmc]: card_caps:0x3000000a
[03.046][mmc]: host_caps:0x3000003f
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3202 bytes read in 10 ms (312.5 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
141 bytes read in 8 ms (16.6 KiB/s)
262144 bytes read in 35 ms (7.1 MiB/s)
** File not found /boot/dtb/allwinner/overlay/-fixup.scr **
6995219 bytes read in 595 ms (11.2 MiB/s)
** File not found /boot/Image **
Unknown command 'booti' - try 'help'
SCRIPT FAILED: continuing...
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
armbian# ** Bad device mmc 1 **
Unknown command '**' - try 'help'
armbian# mmc rescan
[63.143][mmc]: card_caps:0x3000000a
[63.146][mmc]: host_caps:0x3000003f
armbian# fatls mmc 0:0
** Unrecognized filesystem type **
armbian# fatls mmc 1:0
** Bad device mmc 1 **
armbian# fatls mmc 1:0
** Bad device mmc 1 **
armbian# fatls mmc 0:1
** Unrecognized filesystem type **
armbian# [90]HELLO! BOOT0 is starting May 13 2020 14:10:04!
[95]BOOT0 commit : 593cf83
[97]set pll start
[100]periph0 has been enabled
[103]set pll end
[105]unknow PMU
[106]PMU: AXP806
[114]vaild para:1  select dram para0
[117]board init ok
[119]DRAM BOOT DRIVE INFO: V0.52
[122]the chip id is 0x5000
[125]chip id check OK
[127]DRAM_VCC set to 1500 mv
[131]read_calibration error
[135]read_calibration error
[139]read_calibration error
[143]read_calibration error
[147]read_calibration error
[151]read_calibration error
[155]read_calibration error
[159]read_calibration error
[163]read_calibration error
[166]read_calibration error
[169]retraining final error
[174][AUTO DEBUG]32bit,1 ranks training success!
[181]DRAM CLK =720 MHZ
[183]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4)
[190]Actual DRAM SIZE =1024 M
[193]DRAM SIZE =1024 MBytes, para1 = 30fa, para2 = 4000000, dram_tpr13 = 6041
[206]DRAM simple test OK.
[208]rtc standby flag is 0x0, super standby flag is 0x0
[214]dram size =1024
[216]*****dram handle ok****
[220]card no is 0
[221]sdcard 0 line count 4
[224][mmc]: mmc driver ver 2019-12-19 10:41
[228][mmc]: sdc0 spd mode error, 2
[232][mmc]: set f_max to 50M, set f_max_ddr to 25M
[237][mmc]: mmc 0 bias 0
[245][mmc]: Wrong media type 0x0
[248][mmc]: ***Try SD card 0***
[257][mmc]: HSSDR52/SDR25 4 bit
[260][mmc]: 50000000 Hz
[262][mmc]: 15200 MB
[264][mmc]: ***SD/MMC 0 init OK!!!***
[363]Loading boot-pkg Succeed(index=0).
[367]Entry_name        = u-boot
[376]Entry_name        = monitor
[380]Entry_name        = dtbo
[383]Entry_name        = dtb
[386]Jump to second Boot.
NOTICE:  BL3-1: v1.0(debug):9fecd83
NOTICE:  BL3-1: Built : 17:08:29, 2020-05-28
NOTICE:  BL3-1 commit: 8
ERROR:   Error initializing runtime service tspd_fast
NOTICE:  BL3-1: Preparing for EL3 exit to normal world
NOTICE:  BL3-1: Next image address = 0x4a000000
NOTICE:  BL3-1: Next image spsr = 0x1d3

U-Boot 2018.05-armbian (Jun 22 2022 - 07:19:38 +0000) Xunlong Software

[00.463]CPU:   Allwinner H616
[00.466]Model: Orange Pi Zero 2
I2C:   ready
[00.471]DRAM:  1 GiB
Relocation Offset is: 35ec7000
[00.511]secure enable bit: 0
[00.514]PMU: AXP806
[00.519]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz  MBus=400Mhz
[00.701]sunxi overlay merged okqv
[00.704]drv_disp_init
[00.733]__clk_enable: clk is null.
tv_init()950 fetch tv0 err.
[00.739]drv_disp_init finish
[00.741]gic: sec monitor mode
[00.747]flash init start
[00.749]workmode = 0,storage type = 1
[00.752]MMC:     0
[00.754][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.760][mmc]: get sdc_type fail and use default host:tm1.
[00.770][mmc]: Using default timing para
[00.774][mmc]: SUNXI SDMMC Controller Version:0x40200
[00.792][mmc]: card_caps:0x3000000a
[00.795][mmc]: host_caps:0x3000003f
[00.798]sunxi flash init ok
[00.802]Loading Environment from FAT...
[00.805][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00
[00.811][mmc]: get sdc_type fail and use default host:tm1.
[00.822][mmc]: Using default timing para
[00.825][mmc]: SUNXI SDMMC Controller Version:0x40200
** Bad device mmc 1 **
Failed (-5)
[00.837]usb burn from boot
delay time 0
weak:otg_phy_config
[00.850]usb prepare ok
[01.653]overtime
[01.657]do_burn_from_boot usb : no usb exist
[01.661]boot_gui_init:start
141 bytes read in 9 ms (14.6 KiB/s)
Set HDMI disp_mode to 1080p60
141 bytes read in 8 ms (16.6 KiB/s)
Set fb0_width to 1280
Set fb0_height to 720
[01.962]boot_gui_init:finish
[01.965]bmp_name=/boot/boot.bmp
230454 bytes read in 29 ms (7.6 MiB/s)
[02.008]update dts
Net:   [02.011]No ethernet found.
Hit any key to stop autoboot:  0
no mmc device at slot 1
[03.038][mmc]: card_caps:0x3000000a
[03.041][mmc]: host_caps:0x3000003f
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3202 bytes read in 11 ms (284.2 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
141 bytes read in 9 ms (14.6 KiB/s)
262144 bytes read in 35 ms (7.1 MiB/s)
** File not found /boot/dtb/allwinner/overlay/-fixup.scr **
6995219 bytes read in 594 ms (11.2 MiB/s)
** File not found /boot/Image **
Unknown command 'booti' - try 'help'
SCRIPT FAILED: continuing...
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-sunxi
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
armbian# File not found /boot/Imageprintenv
Unknown command 'File' - try 'help'
armbian# printenv
arch=arm
baudrate=115200
board=sunxi
board_name=sunxi
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_disp=1034
boot_disp1=0
boot_disp2=0
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf
boot_fb0=7bf4fcc0,500,2d0,20,1400,1e0,f0,320,1e0
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_targets=fel mmc_auto pxe dhcp
bootargs=root=UUID=7af2b6ff-a1ee-4678-af7e-2271601e558c rootwait rootfstype=ext4 console=ttyS0,115200 consoleblank=0 loglevel=1 ubootpart=f9fc421d-01 usb-storage.quirks=   cgroup_enable=memory swapaccount=1
bootcmd=run distro_bootcmd
bootcmd_dhcp=if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;
bootcmd_fel=if test -n ${fel_booted} && test -n ${fel_scriptaddr}; then echo '(FEL boot)'; source ${fel_scriptaddr}; fi
bootcmd_mmc0=setenv devnum 0; run mmc_boot
bootcmd_mmc1=setenv devnum 1; run mmc_boot
bootcmd_mmc_auto=if test ${mmc_bootdev} -eq 1; then run bootcmd_mmc1; run bootcmd_mmc0; elif test ${mmc_bootdev} -eq 0; then run bootcmd_mmc0; run bootcmd_mmc1; fi
bootcmd_pxe=dhcp; if pxe get; then pxe boot; fi
bootdelay=1
bootfstype=ext4
bootlogo=false
bootm_size=0xa000000
bootreason=unknow
console=serial
consoleargs=console=ttyS0,115200
cpu=armv7
devnum=0
devplist=1
devtype=mmc
dfu_alt_info_ram=kernel ram 0x41000000 0x1000000;fdt ram 0x43000000 0x100000;ramdisk ram 0x43300000 0x4000000
disp_mode=1080p60
disp_reserve=3686400,0x7bf4fcc0
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
docker_optimizations=on
fb0_height=720
fb0_width=1280
fdt_addr_r=0x43000000
fdtaddr=43000000
fdtcontroladdr=7be87560
fdtfile=sunxi/sun50i-h616-orangepi-zero2.dtb
fileaddr=43300000
filesize=6abd13
kernel_addr_r=0x41000000
load_addr=0x45000000
mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fi
overlay_error=false
partitions=name=loader1,start=8k,size=32k,uuid=${uuid_gpt_loader1};name=loader2,size=984k,uuid=${uuid_gpt_loader2};name=esp,size=128M,bootable,uuid=${uuid_gpt_esp};name=system,size=-,uuid=${uuid_gpt_system};
partuuid=f9fc421d-01
pxefile_addr_r=0x43200000
ramdisk_addr_r=0x43300000
rootdev=UUID=7af2b6ff-a1ee-4678-af7e-2271601e558c
rootfstype=ext4
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scriptaddr=0x43100000
snum=ac00143c519446f23ce
soc=sunxi
stderr=serial
stdin=serial
stdout=serial
tv_vdid=2078814848
uuid_gpt_esp=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
uuid_gpt_system=69dad710-2ce4-4e3c-b16c-21a1d49abed3
verbosity=1

Environment size: 3588/131068 bytes
armbian# clear
Unknown command 'clear' - try 'help'
armbian# cls
Unknown command 'cls' - try 'help'
armbian# clsscr
Unknown command 'clsscr' - try 'help'
armbian# printenv
arch=arm
baudrate=115200
board=sunxi
board_name=sunxi
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_disp=1034
boot_disp1=0
boot_disp2=0
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf
boot_fb0=7bf4fcc0,500,2d0,20,1400,1e0,f0,320,1e0
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_targets=fel mmc_auto pxe dhcp
bootargs=root=UUID=7af2b6ff-a1ee-4678-af7e-2271601e558c rootwait rootfstype=ext4 console=ttyS0,115200 consoleblank=0 loglevel=1 ubootpart=f9fc421d-01 usb-storage.quirks=   cgroup_enable=memory swapaccount=1
bootcmd=run distro_bootcmd
bootcmd_dhcp=if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;
bootcmd_fel=if test -n ${fel_booted} && test -n ${fel_scriptaddr}; then echo '(FEL boot)'; source ${fel_scriptaddr}; fi
bootcmd_mmc0=setenv devnum 0; run mmc_boot
bootcmd_mmc1=setenv devnum 1; run mmc_boot
bootcmd_mmc_auto=if test ${mmc_bootdev} -eq 1; then run bootcmd_mmc1; run bootcmd_mmc0; elif test ${mmc_bootdev} -eq 0; then run bootcmd_mmc0; run bootcmd_mmc1; fi
bootcmd_pxe=dhcp; if pxe get; then pxe boot; fi
bootdelay=1
bootfstype=ext4
bootlogo=false
bootm_size=0xa000000
bootreason=unknow
console=serial
consoleargs=console=ttyS0,115200
cpu=armv7
devnum=0
devplist=1
devtype=mmc
dfu_alt_info_ram=kernel ram 0x41000000 0x1000000;fdt ram 0x43000000 0x100000;ramdisk ram 0x43300000 0x4000000
disp_mode=1080p60
disp_reserve=3686400,0x7bf4fcc0
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
docker_optimizations=on
fb0_height=720
fb0_width=1280
fdt_addr_r=0x43000000
fdtaddr=43000000
fdtcontroladdr=7be87560
fdtfile=sunxi/sun50i-h616-orangepi-zero2.dtb
fileaddr=43300000
filesize=6abd13
kernel_addr_r=0x41000000
load_addr=0x45000000
mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fi
overlay_error=false
partitions=name=loader1,start=8k,size=32k,uuid=${uuid_gpt_loader1};name=loader2,size=984k,uuid=${uuid_gpt_loader2};name=esp,size=128M,bootable,uuid=${uuid_gpt_esp};name=system,size=-,uuid=${uuid_gpt_system};
partuuid=f9fc421d-01
pxefile_addr_r=0x43200000
ramdisk_addr_r=0x43300000
rootdev=UUID=7af2b6ff-a1ee-4678-af7e-2271601e558c
rootfstype=ext4
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done
scriptaddr=0x43100000
snum=ac00143c519446f23ce
soc=sunxi
stderr=serial
stdin=serial
stdout=serial
tv_vdid=2078814848
uuid_gpt_esp=c12a7328-f81f-11d2-ba4b-00a0c93ec93b
uuid_gpt_system=69dad710-2ce4-4e3c-b16c-21a1d49abed3
verbosity=1

Environment size: 3588/131068 bytes
armbian# mtest
Unknown command 'mtest' - try 'help'
armbian# ls
ls - list files in a directory (default /)

Usage:
ls <interface> [<dev[:part]> [directory]]
    - List files in directory 'directory' of partition 'part' on
      device type 'interface' instance 'dev'.
armbian#
 

tl;dr: Put your Zero2 and/or any other H616 based device on the shelf and WAIT for proper support to come. And no. There is no ETA. Assuming usable state end 2021/beginning 2022.

Software support is still work in progress and under heavy development. Provided preview images can break any time. Do not report this, we are aware of that and can/will not help you with that if you are not willing to investigate and research by yourself.

Feel free to join fellow developers to their efforts to create proper software support. But don't waste our time with complains. Thank you!

https://github.com/apritzel/linux/commits/h616-v5

https://github.com/jernejsk/u-boot/tree/h616-v2

https://github.com/apritzel/arm-trusted-firmware/tree/h616-v2-wip

-----------------------------------------------------------------------------

I started to play with this board and obviously failed miserably creating a basic Armbian integration.

Anyway. These are the information I collected so far:

dtb extraction from Xulong image: https://pastebin.com/raw/Uni2JzBF

orangepimonitor 🙄  http://ix.io/2FM0

root@orangepizero2:/etc/apt# lsmod
Module                  Size  Used by
zram                   36864  2
sprdwl_ng             438272  0
sprdbt_tty             36864  2
uwe5622_bsp_sdio      294912  2 sprdbt_tty,sprdwl_ng

kernel config: https://pastebin.com/raw/e2jTTZ7A

config-4.9.255-sun50iw9

The stable armbian Focal image with Kernel 5.16.y fails to initialize the board. If I install the kernel 4.19.y image it does work in both Focal and Bullseye but when I try to change the kernel from armbian -config then it installs but on reboot it fails once again to reinitialise the board.

I am using an orange pi zero 2 1gb.

Just a couple of days ago Orange pi released two new images (Bullseye and Focal) with kernel 5.16 and 5.13 respectively. They do work and install. Although I would prefer to use armbian to the orange pi versions of it.

Maybe someone can have a look at those two images to compare them with armbian to see where do they differ and why one fails to start the board while the other ones work

orange pi official Bullseye (Debian) images

orange pi official Focal and bionic (Ubuntu) images

Thanks.

I just download the image for Oranegpi Zero2 :

Armbian 21.08 Bullseye

Kernel 4.9.y, Size: 337Mb, Updated: Jan 24, 2022

And I use "usbimage" write the image to my SD card .

And,  nothing happen, Red LED and Green LED not lighting. Serial Port has no any message.

I have 3 SD card, 2 Orangepi Zero2. All of it I test still failure.

I have a older image for Orangepi Zero2 name "Armbian_21.08.1_Orangepizero2_buster_legacy_4.9.280.img.xz". This one is useful. BUT, can not "apt upgrade". If you do so , you cannot boot up next time.

So I just confuse now......

Hi,

Im running Armbian_21.08.2_Orangepizero2_buster_legacy_4.9.255 on Orangepi zero 2. 
I don't see ttyUSB in my /dev/ but I can see it when  I list usb :

root@orangepizero2:~# lsusb
Bus 006 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 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0781:5591 SanDisk Corp. Ultra Flair
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Any Idea what should I do ? 
Thank in advance ! 

log.txt

U-Boot SPL 2021.10-rc1-armbian (Aug 08 2021 - 16:21:36 +0200)
DRAM: 1024 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.5(debug):87311b4-dirty
NOTICE:  BL31: Built : 16:21:30, Aug  8 2021
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a082220, model: OrangePi Zero2
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    PMIC: Probing AXP305 on RSB
INFO:    PMIC: aldo1 voltage: 3.300V
INFO:    PMIC: aldo2 voltage: 3.300V
INFO:    PMIC: aldo3 voltage: 3.300V
INFO:    PMIC: bldo1 voltage: 1.800V
INFO:    PMIC: dcdcd voltage: 1.500V
INFO:    PMIC: dcdce voltage: 3.300V
INFO:    Changed devicetree to reserve BL31 memory.
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for 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


U-Boot 2021.10-rc1-armbian (Aug 08 2021 - 16:21:36 +0200) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: OrangePi Zero2
I2C:   ready
DRAM:  1 GiB
MMC:   mmc@4020000: 0
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   phy interface7
eth0: ethernet@5020000
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
3202 bytes read in 2 ms (1.5 MiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
131 bytes read in 1 ms (127.9 KiB/s)
19495 bytes read in 4 ms (4.6 MiB/s)
Failed to load '/boot/dtb/allwinner/overlay/-fixup.scr'
12106416 bytes read in 501 ms (23 MiB/s)
22200328 bytes read in 918 ms (23.1 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41790000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    12106352 Bytes = 11.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Ramdisk to 49474000, end 49fffa70 ... OK
   Loading Device Tree to 0000000049406000, end 0000000049473fff ... OK

Starting kernel ...

I am looking for support library for GPIO, SPi for Orange pi zero2 H616. I searched everywhere but found only 1 library https://github.com/orangepi-xunlong/wiringOP. I tested by flashing one led but stopped like the GPIO pins are the same? I don't know what's going on here? Is there a library to support me?

Please help.

Board: orange pi zero 2+ h5

Upgraded packages(from apt upgrade):

Get:1 http://security.debian.org buster/updates/main arm64 libp11-kit0 arm64 0.23.15-2+deb10u1 [303 kB]
Get:2 http://httpredir.debian.org/debian buster-updates/main arm64 tzdata all 2020e-0+deb10u1 [266 kB]
Get:4 http://security.debian.org buster/updates/main arm64 nodejs arm64 10.23.1~dfsg-1~deb10u1 [87.3 kB]       
Get:5 http://security.debian.org buster/updates/main arm64 libnode-dev arm64 10.23.1~dfsg-1~deb10u1 [397 kB]
Get:6 http://security.debian.org buster/updates/main arm64 libnode64 arm64 10.23.1~dfsg-1~deb10u1 [5,280 kB]
Get:3 https://mirrors.dotsrc.org/armbian-apt buster/main arm64 armbian-config all 20.11.6 [44.5 kB]                                                                                         
Get:8 https://armbian.hosthatch.com/apt buster/main arm64 linux-dtb-current-sunxi64 arm64 20.11.7 [81.8 kB]                                                                                 
Get:7 https://mirrors.dotsrc.org/armbian-apt buster/main arm64 linux-buster-root-current-orangepizeroplus2-h5 arm64 20.11.6 [415 kB]                                                        
Get:11 https://armbian.systemonachip.net/apt buster/main arm64 linux-u-boot-orangepizeroplus2-h5-current arm64 20.11.6 [273 kB]                                                             
Get:9 https://minio.k-space.ee/armbian/apt buster/main arm64 linux-headers-current-sunxi64 arm64 20.11.7 [11.4 MB]                                                                          
Get:10 https://uk.mirrors.fossho.st/armbian/apt buster/main arm64 linux-image-current-sunxi64 arm64 20.11.7 [31.0 MB]                                                                
Get:12 http://security.debian.org buster/updates/main arm64 python-apt-common all 1.8.4.3 [96.3 kB]                                                  
Get:13 http://security.debian.org buster/updates/main arm64 python3-apt arm64 1.8.4.3 [179 kB]
 

Upgrade without problems. After reboot: