Hi everyone, I'm very new to Armbian Linux. I'm about to acquire Orange Pi Zero 2W for my audio project. I have read some of the forum posts related to the SOC's native I2S, and I'd like to know if those problems mentioned in the posts have been resolved in the new kernel? Meaning that users don't have to write and compile their own device tree overlay and kernel mode driver? My project require a full duplex I2S with the CODEC as the master. Nothing fancy, just 2 channels in and 2 channels out. Hope someone can help clear the doubts so that I know for sure I will not be buying what I can not use. Thanks

I have dtb files used by manufacturers for compiling on the Android 5.1 system (OEM versions 2.17 and 2.19). It differs from boards like the firefly, for example: using a 100 Mbps network port, USB GPIO uses <0x50 0x0c 0x00>. Can anyone help with adapting this board? I want to compile it for armbian. 2.17.dtb 2.19.dtb

@xiboliyadongtu Did you try Hangover (which is Fex-emu)? https://github.com/AndreRH/hangover I saw someone had a problem with a similar online game with Box64 before. https://github.com/ptitSeb/box64/issues/3073#issuecomment-3689810679

Greetings, i own a CB1, however i cannot get it to work well either. Perhaps we can help each other.

@hexdump I also have the exact constraints, I've detached eMMC from my HG680P. I've tried your u-boot using armbian and velvet's image tester, but boot of them failed to boot, and on UART I can't see anything. Any idea what should I try next ? Anyway, I managed to boot custom OpenWrt and I attached the scripts that I used to generate image run.sh insomwrt_with_vendor_u_boot.log