ALIGMSTEN

for uwe5622, when it comes to allwinner, only device tree specific thing needed is to mark the corresponding mmc node status as ok. Other than that, only available option is for configuring bt_wake pin for bluetooth low power mode. But that is optional. So as long as mmc node is present and status is set to ok, wifi should work find once the corresponding drivers are loaded either manually or via kernel commandline.

@kriptonusFYI, the boot issue is resolved and the fix has been merged into latest armbian/main. So you should be able to either build it yourself or take latest nightly images dated 24 Aug or higher. We however have kind of hijacked the thread to resolve other issues experienced by ALIGMSTEN during testing of the fix on this board. You can also give the build a try and let us know of any other issues you might face and we will try to resolve the same.

Thanks, this will be helpful. I will try to find the cause tomorrow

Thats great news. We have similar issue with nanopineo2 black as well. And I suspect its the same cause. Sending a image to Igor to confirm. Will raise a PR with the fix once he confirms

Hello @Gunjan Gupta .... thanks for your efforts - you have success!
 
The board boots with your patch changes.
 
https://paste.next.armbian.com/samaqedifo
 
alistair@h616-hdmi:~/build$ git status On branch sunxi Your branch is up to date with 'origin/sunxi'. Untracked files: (use "git add <file>..." to include in what will be committed) patch/u-boot/u-boot-sunxi/board_orangepi3-lts/0002-update-defconfig.patch ptmain.sh nothing added to commit but untracked files present (use "git add" to track) alistair@h616-hdmi:~/build$ git rev-parse HEAD af42e9d3ec25a89977d04f9d8bd8baa21803316e alistair@h616-hdmi:~/build$  

Terribly sorry for misleading, my mistake, checking out bc46fd509a50db4bcef014d79569b68287ecc19b~1 build boots (I forgot about the ~1).
 
I will do the patch this evening.

The only solution for legacy images is to downgrade to cgroups v1 with kernel parameter 
 
You add this in armbianEnv.txt
 
extraargs=systemd.unified_cgroup_hierarchy=0  
 
To use cgroup v2, you need to have kernel 4.15 or later https://github.com/opencontainers/runc/blob/v1.0.0-rc95/docs/cgroup-v2.md#host-requirements.
 
Other requirements you might need to set iptables debian os
 
The docker installer uses iptables for nat. Unfortunately Debian uses nftables. You can convert the entries over to nftables or just setup Debian to use the legacy iptables. sudo update-alternatives --set iptables /usr/sbin/iptables-legacy sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy  
 
As for non booting zero2 images please check latest, builds are working fine for me at this point, although I will check, (limited time atm, also 'not sure about mirrors synching').

Wow! Thanks ALIGMSTEN! This solve the issue completely. The last docker version is now working on Armbian bullseye kernel 4.9 on Orange pi zero2.
Thanks for your help and for what you are doing!
Here is the detailed procedure for the people that may experience the same issue.
 
-Fresh install of Armbian_23.02.3_Orangepizero2_bullseye_legacy_4.9.318.img.xz
http://xogium.performanceservers.nl/archive/orangepizero2/archive/Armbian_23.02.3_Orangepizero2_bullseye_legacy_4.9.318.img.xz
 
sudo apt-get update
sudo apt-get upgrade
 
-add the following to /boot/armbianEnv.txt
extraargs=systemd.unified_cgroup_hierarchy=0
 
-return to prompt
sudo update-alternatives --set iptables /usr/sbin/iptables-legacy
sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
 
-reboot
 
-install docker according to https://docs.docker.com/engine/install/debian/ (below)
sudo apt-get update
sudo apt-get install ca-certificates curl gnupg
sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
sudo chmod a+r /etc/apt/keyrings/docker.gpg
 
-Then
echo \
  "deb [arch="$(dpkg --print-architecture)" signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/debian \
  "$(. /etc/os-release && echo "$VERSION_CODENAME")" stable" | \
  sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
 
sudo apt-get update
sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo reboot
 
-Test docker with
sudo docker run hello-world
 

My humble apologies, in haste copy/paste incorrectly! have amended the example.
 
 
Correct I've found that change to be visually appealing and closest to the 4.9 legacy kernels  
 
Thanks, valid points, noted the on-page posting last couple, instead of correctly formatted text in attachments or links, agreed that might be easier read.
 
Trigger Options:
usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlo ck kbd-ctrlllock kbd-ctrlrlock usbport disk-activity disk-read disk-write ide-di sk mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 activity default-on panic mmc 0 rfkill-any rfkill-none stmmac-0:01:link stmmac-0:01:1Gbps stmmac-0:01:100Mbps stmmac-0:01:10Mbps  
Lets see, perhaps doing this in a 'democratic-manner' here is not the way.
 
Merged - https://github.com/armbian/build/pull/5270
 
As above your preferences can be altered when you build!

Hi
 
I am afraid I cannot contribute much to this project, as I lack the technical expertise - but I have the orangepizero2 H616, and I think it is a fantastic bit of hardware for the price. I would like to do much more with it (currently I am using it as a pikvm, which works nicely and is fun... and a lot cheaper than a raspberypi based solution).
 
It is a shame it is not more fully supported and I just wanted to say thank you for your work and efforts on this.
 
Thank you!

Hello @elliotmatson Welcome.
 
Would you mind to please elaborate on the hardware differences you can see.
 
Unfortunately, you are correct, there do not seem to be schematics readily available for newer revisions. 
I have worked on V1.3 boards and have been used to having to power cycle occasionally, this might likely be tied to the current development, mainline, edge(here), and the fact that all is WIP.
 
I did look into the power cycling more thoroughly, and although there are a few 'net crumbs' to be found, nothing indicative that I have yet seen or tried.
 
At the moment I've had stable power on's with latest minimal build. Some of the work I've done in isolation has also improved boots.
 
 
 
Right now am testing cpu-frequency-scaling, I will add that v1 to main 6.1.11 fairly shortly its ready, I am adding proper current sensing to my test bench, for more elaborate stability testing, hopefully resulting in better v2
 
Next will most likely follow the progress with DRAM. I also prefer to work with debian os so not entirely sure if ubuntu has some difference.
 
While this doesn't answer your questions, these are known problems, and do not have definitive solutions anywhere right now.
 

https://www.armbian.com/newsflash/armbian-23-02/
 
 
Changelog: https://docs.armbian.com/Release_Changelog/

Might be minimal image and firstlogin don't like each other?
Either way, please open GitHub issue with those, can't keep up with 2 places for issues.

Different series of the same chip.
It is sad. I'll think about what can be done.

In order to disable the patch, it is enough to put a minus sign at the beginning of the line with this patch in the "series.conf" file.
These patches exist, but they don't apply.

@going and @Igor checking the H616 mainlining thread, the x_late patch is running currently unoptimized WIP, we can improve on this as testing play's out. I will add the recommended thermal changes for now and can submit a pr to 6.1 they will be fine if that is good.

H616_User_Manual_V1.0.
Yes it is different from other allwinner chips. The register is read-only and a jumper is needed.

I was successful to boot uBoot over SPI-FLASH and continue to boot over network (PXE+NFS), and my few comments:
uboot (orangepi)
 - https://github.com/orangepi-xunlong/u-boot-orangepi.git (v2021.10-sunxi)
does not support SPI-FLASH boot  upstream uboot hungs, but it has patch to support SPI boot (since v2023.01-rc1)
- https://patchwork.ozlabs.org/project/uboot/list/?series=252044&state=*
- https://github.com/u-boot/u-boot/commit/e50ee3a8d7328142eb24741305f751e5c0952380 so I extend 1. with 2. (attached) and rebuild uBoot flash uboot, in linux ` nandwrite /dev/mtd0 u-boot-sunxi-with-spl.bin ` (erase: ` flash_eraseall /dev/mtd0 `) install jumper between PC5 and GND (13-14 pinheader)
... and boot U-Boot SPL 2021.10-g0b91e222-dirty (Jan 09 2023 - 02:10:12 +0100) DRAM: 1024 MiB Trying to boot from sunxi SPI NOTICE: BL31: v2.8(debug):f4d8ed5 NOTICE: BL31: Built : 23:43:55, Jan 7 2023 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a087b80, 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 2021.10-g0b91e222-dirty (Jan 09 2023 - 02:10:12 +0100) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: OrangePi Zero2 I2C: ready DRAM: 1 GiB MMC: mmc@4020000: 0 Loading Environment from SPIFlash... SF: Detected mx25l1606e with page size 256 Bytes, erase size 4 KiB, total 2 MiB OK In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: phy interface7 eth0: ethernet@5020000 Autoboot in 2 seconds, press <Space> to stop MMC: no card present ethernet@5020000 Waiting for PHY auto negotiation to complete.. done BOOTP broadcast 1 *** Unhandled DHCP Option in OFFER/ACK: 2 *** Unhandled DHCP Option in OFFER/ACK: 42 *** Unhandled DHCP Option in OFFER/ACK: 4 *** Unhandled DHCP Option in OFFER/ACK: 252 *** Unhandled DHCP Option in OFFER/ACK: 2 *** Unhandled DHCP Option in OFFER/ACK: 42 *** Unhandled DHCP Option in OFFER/ACK: 4 *** Unhandled DHCP Option in OFFER/ACK: 252 DHCP client bound to address 192.168.1.242 (45 ms) *** Warning: no boot file name; using 'C0A801F2.img' Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'C0A801F2.img'. Load address: 0x42000000 Loading: * TFTP error: 'Access violation' (2) Not retrying... missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-00-d2-c3-32-42 Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'pxelinux.cfg/01-02-00-d2-c3-32-42'. Load address: 0x4fd00000 Loading: * TFTP error: 'Access violation' (2) Not retrying... missing environment variable: bootfile Retrieving file: pxelinux.cfg/C0A801F2 Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'pxelinux.cfg/C0A801F2'. Load address: 0x4fd00000 Loading: # 11.7 KiB/s done Bytes transferred = 126 (7e hex) Config file found 1: linux missing environment variable: bootfile Retrieving file: uInitrd Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'uInitrd'. Load address: 0x4ff00000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ######################### 9.2 MiB/s done Bytes transferred = 15625901 (ee6ead hex) missing environment variable: bootfile Retrieving file: Image Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'Image'. Load address: 0x40080000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ###################### 9.8 MiB/s done Bytes transferred = 22259720 (153a808 hex) append: root=/dev/nfs nfsroot=192.168.1.1:/sunxi/ ip=dhcp rw missing environment variable: bootfile Retrieving file: dtb/allwinner/sun50i-h616-orangepi-zero2.dtb Using ethernet@5020000 device TFTP from server 192.168.1.1; our IP address is 192.168.1.242 Filename 'dtb/allwinner/sun50i-h616-orangepi-zero2.dtb'. Load address: 0x4fa00000 Loading: ### 706.1 KiB/s done Bytes transferred = 38323 (95b3 hex) Moving Image from 0x40080000 to 0x40200000, end=417a0000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15625837 Bytes = 14.9 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 49119000, end 49fffe6d ... OK Loading Device Tree to 000000004910c000, end 00000000491185b2 ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.16.17-sun50iw9 (martin@martin-v15) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #3 SMP Wed Jan 11 14:07:16 CET 2023 [ 0.000000] Machine model: OrangePi Zero2 [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000007fffffff] [ 0.000000] NUMA: NODE_DATA [mem 0x7fdca040-0x7fdcbfff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000040000000-0x000000007fffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x000000004007ffff] [ 0.000000] node 0: [mem 0x0000000040080000-0x000000007fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000007fffffff] [ 0.000000] cma: Reserved 128 MiB at 0x0000000076c00000 [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs  
spiboot.patch

Ok! This means that something has been fixed.
I was building this release htop/releases/tag/3.2.1
 
 I'll check the build from the head git.

Adding wireless: uwe5622 driver support at a cursory glance looks like 215 file changes totaling 210,075 additions. 
 
Those changes depend what is currently in the latest release, I am sure there quite an overlap already in place. I've only just started looking at the diff's, so quite a lot to digest before knowing exactly what would need to be done.

Hello Bruno,
 
I don't have any BPI boards, but in addition to Myron's request to understand specifics.
 
What is the output ?
demsg | grep spi*  
armbianEnv selections look correct, but will require more info.

sudo update-alternatives --set iptables /usr/sbin/iptables-legacy sudo update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy  
 

Hi @yar83,
 
Sorry for responding late. Don't underestimate yourself, from what you have said, you have already done much and made a sensible choice with your project. Embedded Linux is a different subject from micro controllers which although OT, might be more appropriate for the physical computing aspects of your project.
 
I read it that you were struggling with the zero2 hardware, specifically integrating GPIO uses and possibly protocols such as SPI and i2c as an example. My agreement of that struggle specifically with zero2 is that the development of this boards peripheral's is non existent and have no easy way forward at the moment. 
 
You will have to brush up on device trees and overlays in order to start to use the capabilities of the board and you seem keen to have a serious punt at it for learning purposes.
 
Best,
Alistair

Good start if you have the time and use case.
 
 
You will have to think outside the 'book' its examples are different soc.
 
Whats your use case? Is it fun or fairly serious project.
 
If it a project that you have time to put into, then effort might be justifiable, should you make some progress contribute back to the community. Otherwise keep hoping that someone else will make the effort and part with that back to community.
 
Best of luck.