Jump to content

rollinglabs

Validating
  • Posts

    1
  • Joined

  • Last visited

Everything posted by rollinglabs

  1. 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! 🙏
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines