Gunjan Gupta

@Gunjan Gupta, Would you be able move forward the following patch. I have been working on the zero3 overlays and with your help I have made some progress. But it all depends on having the overlay_prefix set.  It makes sense to point to the h616 overlays as the zero3 and zero2 are common for the items that would normally go into the overlays. I have been using the proposed change and it makes the fixup.scr work on boot and allows armbian-config > System > Hardware to work and load overlays on boot
 
diff --git a/config/boards/orangepizero3.wip b/config/boards/orangepizero3.wip
index 18bcae79d..642eb216f 100644
--- a/config/boards/orangepizero3.wip
+++ b/config/boards/orangepizero3.wip
@@ -3,6 +3,7 @@ BOARD_NAME="Orange Pi Zero3"
 BOARDFAMILY="sun50iw9"
 BOARD_MAINTAINER="viraniac"
 BOOTCONFIG="orangepi_zero3_defconfig"
+OVERLAY_PREFIX=sun50i-h616
 BOOT_LOGO="desktop"
 KERNEL_TARGET="current,edge"
 FORCE_BOOTSCRIPT_UPDATE="yes"
 

Thats becuase loading overlays from configfs is something that was viewed as not a recommended way and hence was not merged into the kernel. If you still wants to do the same, I believe our Allwinner kernels do have a patch that adds that functionality. Not sure if the same can be said for every soc family supported by Armbian. Also I am not sure if loading overlay via configfs is ever tested and hence cant say how well that works.

As h616 and h618 are suppose to be pin compatible, same overlays should work between the same

Yeah I see what you mean. But then orangepi zero is a 32-bit device, so the developer might have thought that it would be obvious that a dtsi in arm64 directory will not be applicable to the same.

Thanks for testing, raised https://github.com/armbian/build/pull/6113 to replace the binary for everyone.

Yeah, seems like hciattach binary crashes some times as reported by @Stephen Graf as well. Try replacing /usr/bin/hciattach_opi with https://github.com/orangepi-xunlong/orangepi-build/raw/next/external/packages/blobs/bt/hciattach/hciattach_opi_arm64. Make sure to keep the filename the same i.e hciattach_opi. Let me know if it works after reboot

The key is at http://fi.mirror.armbian.de/apt/armbian.key
 
you can try adding it with
 
wget -qO - http://fi.mirror.armbian.de/apt/armbian.key | sudo apt-key add -  

Looks like you misread the board name posted by mattdebauge. We currently have no support Orange Pi Zero 2w right now.

BTW I am working on migrating armbian to 6.7 kernel - https://github.com/armbian/build/pull/6079
 
Feel free to test and comeback. currently it fails compilation for xradio and some realtek wifi drivers that I will fix today. It can be compiled when building with EXTRAWIFI=no, but that will skip compiling uwe5622 driver.
 
Edit: Compilation issue is now fixed.

Yes, it was fixed as part of https://github.com/armbian/build/pull/6040

omg total noob mistake, had the SDA (MOSI) line on the MISO pin!!! 
but it works on reboot now!! 
thank you so much! you are an absolute legend!!
 
haha ok i will remove the "param_spidev_spi_cs=1" from armbianEnv.txt
 
Thank you again!
 

BTW I am working on migrating armbian to 6.7 kernel - https://github.com/armbian/build/pull/6079
 
Feel free to test and comeback. currently it fails compilation for xradio and some realtek wifi drivers that I will fix today. It can be compiled when building with EXTRAWIFI=no, but that will skip compiling uwe5622 driver.
 
Edit: Compilation issue is now fixed.

Looks like there might be another H618 board in the pipeline named orange pi r1b - https://github.com/orangepi-xunlong/orangepi-build/blob/next/external/config/boards/orangepir1b.conf

That message is pretty early in boot. Also 517 is EPROBE_DEFER which means pin is not available right now and driver will retry to grab it later. Its feel its ok to have that message unless it breaking some functionality. 
 
That sounds correct
 
That not needed. Are your changes in your git branch? May be I can take a look

@pixdriftTry hdmi on orange pi zero 2 for both 6.1 and 6.6 kernel from my branch - https://github.com/viraniac/armbian_build/tree/h616-hdmi 
 
If this works, I will then move all the orangepizero2 patches to orangepizero.dtsi. I want to get this out of the way before I bump the edge kernel to 6.7

@pixdrift could you please test the kernel from the following link on Orange Pi Zero 2 - https://drive.google.com/drive/folders/1cjCyISx3r7bVlXEPapf_5BbONQMyTcHX?usp=drive_link 
 
This kernel has all of the sun4i-drm patches enabled. See if HDMI works

@pixdriftTry hdmi on orange pi zero 2 for both 6.1 and 6.6 kernel from my branch - https://github.com/viraniac/armbian_build/tree/h616-hdmi 
 
If this works, I will then move all the orangepizero2 patches to orangepizero.dtsi. I want to get this out of the way before I bump the edge kernel to 6.7

@pixdrift could you please test the kernel from the following link on Orange Pi Zero 2 - https://drive.google.com/drive/folders/1cjCyISx3r7bVlXEPapf_5BbONQMyTcHX?usp=drive_link 
 
This kernel has all of the sun4i-drm patches enabled. See if HDMI works

https://github.com/armbian/build/pull/6070 should fix the cpufreq hang issue and should also get bluetooth working for orange pi zero 2

https://github.com/armbian/build/pull/6070 should fix the cpufreq hang issue and should also get bluetooth working for orange pi zero 2

Adjust patch/kernel/archive/sunxi-6.6/patches.armbian/arm64-dts-allwinner-h616-Add-efuse_xlate-cpu-frequency-scaling-v1_6_2.patch to patch arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero.dtsi instead of arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts
 
Interesting. So it happens on h616 as well. Its that wifi driver causing the trouble again. I have encountered this issue on Orange Pi 3 LTS as well. I ended up removing sprdwl_ng from MODULES and loaded it instead using a systemd service. See https://github.com/armbian/build/commit/608618a6f5b341a1a171d3a0841a4807432d8294

There are five different patches that are imported from megous kernel tree (xff.cz) that conflicts with hdmi patch. The hdmi patch has to be rewritten to fix the same. I haven't started working on it yet, but I will do it soon. Most likely within next 2 weeks window as I would be bumping the allwinner kernel versions. Legacy kernel will be moved o 6.1, current to 6.6 and edge kernel to 6.7

Bluetooth is not going to work. Its currently broken in zero2 as well. The kernel has the required driver, but the hciattach binary and corresponding service file for the same is missing. I am going to create a extension for uwe5622 wireless module that should make it easy to set this thing in the future

Bluetooth is not going to work. Its currently broken in zero2 as well. The kernel has the required driver, but the hciattach binary and corresponding service file for the same is missing. I am going to create a extension for uwe5622 wireless module that should make it easy to set this thing in the future

There are five different patches that are imported from megous kernel tree (xff.cz) that conflicts with hdmi patch. The hdmi patch has to be rewritten to fix the same. I haven't started working on it yet, but I will do it soon. Most likely within next 2 weeks window as I would be bumping the allwinner kernel versions. Legacy kernel will be moved o 6.1, current to 6.6 and edge kernel to 6.7