NanoPi Zero2 support

[rollinglabs]

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

1. Is anyone already working on this? (Don't want to duplicate!)
2. Kernel branch: Should I target current (6.12) or edge (6.15+) for the DTB?
3. 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! 🙏
 

Edited 10 hours ago by rollinglabs

[Werner]

Even though current is an LTS kernel it probably makes more sense to focus on vendor an edge. vendor because its rockchip bsp and close to being feature-complete. And edge for likely becoming the next LTS kernel which ultimately become current at some point.

You can try to see what actually works on current at this time.

You can ignore 6.15-6.17 since those patches, if still present, are for archival purposes only and will be remove at some point.

 

4 hours ago, rollinglabs said:

Bootconfig: Can I reuse hinlink_rk3528_defconfig or does Zero2 need its own?

In theory it could be re-used but may introduce confusion. If in doubt, copy and rename.

 

Edit: Seems like lots of stuff has been mainlined already. So I suggest shifting your primary focus on edge.