gkkpch

Thanks Werner, Unfortunately I have to halt this project. Though I can now create an booting Neo3plus Armbian image based on the Zero2, it does not fit my initial requirements. Obviously u-boot requires an android partition scheme. The current version as used by the nanopi zero2 cannot be used for my own purposes. So it will need to wait until the board can boot without a vendor u-boot version.

Hi, I have started to work on a Nanopi Neo3 Plus image (rk3528-based, similar to Nanopi Zero2), announced early March 2026. Created a new .csc file, used the Nanopi Zero2 as a template. Built it with the vendor version. Built it with the vendor kernel., but added the "dt" directory with the rk3528-nanopi-rev02.dts to be "automatically" added to the dts directory and Makefile. The base console version seems to work ok when I generate a bookworm image. As I currently only need u-boot, kernel and dtb's to build my own OS (Volumio, volumio.org), it works for me. Of course, I would like to contribute my work (and support it?), but how do I proceed? I used Armbian's kernel and u-boot build a lot, but not done this before.