rollinglabs

Hi everyone, wanted to share what we found attempting Armbian support for Zero2. Zero2 utilises an Android-style partition layout from FriendlyElec, which I found to be fundamentally incompatible with Armbian's partition scheme. It seems to use an Android layout (boot at partition 4, rootfs at partition 8, etc.) vs Armbian's standard GPT layout. U-Boot is configured to look for partitions at specific Android-style locations Zero2 assigns SD=mmcblk0, eMMC=mmcblk2 (opposite of typical RK3528 boards) What I think is needed: Adapt hinlink_rk3528_defconfig for Android partition layout Modify partition table generation in the Armbian build system Update bootloader scripts to match partition locations Handle the inverted mmcblk device assignments LED mapping adjustments (Zero2 uses 2-LED system: sys_led, user_led vs typical 3-LED RK3528 boards) Network interface detection (single ethernet vs dual on R3S/hinlink) The device tree is already merged (rk3528-nanopi-zero2.dtb - thanks Jonas!), so that part is straightforward. It's specifically the bootloader/partition integration that's the blocker. Would love to hear thoughts. For now as a workaround, we've stayed with FriendlyElec's Ubuntu base to keep our project moving.

Hi Armbian Community, I'm creating a board configuration for NanoPi Zero2 (RK3528A) and wanted to coordinate with the community before submitting. Great News: Mainline Support Exists! I discovered that Jonas Karlman has already merged NanoPi Zero2 device tree support into mainline Linux kernel: Device tree: rk3528-nanopi-zero2.dts (merged for v6.15-6.18) U-Boot support: Also merged Source: https://github.com/ziyao233/rk3528-mainline Since the hinlink-h28k.csc config already provides RK3528 support, creating a NanoPi Zero2 config should be straightforward. Quick Questions Is anyone already working on this? (Don't want to duplicate!) Kernel branch: Should I target current (6.12) or edge (6.15+) for the DTB? Bootconfig: Can I reuse hinlink_rk3528_defconfig or does Zero2 need its own? My Plan # Copy existing RK3528 config cp hinlink-h28k.csc nanopi-zero2.csc # Update: BOARD_NAME="NanoPi Zero2" BOOT_FDT_FILE="rockchip/rk3528-nanopi-zero2.dtb" KERNEL_TARGET="current,edge" Testing Commitment Hardware: NanoPi Zero2 arriving next week Use case: Production IoT device (headless, Docker, eMMC boot) Will test: Full manufacturing flow, LED control, eMMC boot, network, Docker Will contribute: Tested config + documentation Why This Board? Tiny form factor: 40×40mm Production-ready: Good margins, reliable supply Sufficient specs: 2GB RAM, eMMC, single GbE Mainline support: Thanks to Jonas Karlman's work! Any advice before I proceed? Happy to collaborate or take guidance from maintainers. Thanks! 🙏