[leoppark94]

• Boots UFS images with the vendor SPI NOR firmware.
• The image and the installer do not write to SPI NOR.
• Add more detailed comments on the configuration.

Description

Promote the Firefly AIBOX-K3 board config from .wip to .csc (community supported).

The board keeps its bootloader in SPI NOR. Armbian only provides the UFS image, so the board file:

• does not write U-Boot into the image,
• uses the vendor UFS layout: bootfs at 12 MiB, rootfs at 268 MiB,
• uses 4 KiB sectors, because the UFS reports 4096-byte logical sectors and a 512-byte boot FAT does not mount,
• writes env_k3.txt, which the vendor U-Boot reads to find the kernel and the DTB.

Comments in the file explain these points. No other board is affected.

GitHub issue reference: [Feature Request]: Support Firefly AIBOX-K3
Jira reference: none

Documentation summary for feature / change

Documentation PR link

Documentation is prepared in armbian/documentation, section
"SpacemiT" of Writing the image:

• short description: Flash SpacemiT boards with TitanFlasher
• summary: the board is flashed over USB with the vendor tool; only bootfs and rootfs come from the Armbian image, the SPI NOR bootloader stays in place.
• example of usage: extract the two partitions from the image, put them in the vendor firmware directory, replace the matching entries in TitanFlasher, and flash.

Label: Needs Documentation

How Has This Been Tested?

Tested on a Firefly AIBOX-K3 (SpacemiT K3, 16 GB RAM, UFS), with the vendor SPI NOR firmware unchanged.

• Build: ./compile.sh build BOARD=firefly-aibox-k3 BRANCH=legacy RELEASE=resolute BUILD_MINIMAL=yes
• Flash: TitanFlasher, vendor firmware package with bootfs and rootfs replaced by the partitions of the built image

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules (no dependent changes)

Summary by CodeRabbit

• Refactor
  • Updated the Firefly AIBox K3 board configuration with release metadata and clarifications about storage layout, sector-size requirements, bootloader handling, and vendor installation inputs.
  • Renamed an internal configuration callback; its environment-file writing behavior remains unchanged. No end-user behavior changes are noted in this update.

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

Run configuration

• Source mode: Auto
• Repository: armbian/build
• Branch: main
• File: .coderabbit.yaml
• Commit: 6c0096e
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 8d2262f0-791c-4bfb-b571-8f09fa51d8b3

Commits

Reviewing files that changed from the base of the PR and between 0519bd1 and ff031bd.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Walkthrough

The Firefly AIBOX-K3 configuration adds its introduction year and comments about UFS, SPI NOR, and vendor flasher inputs. It also renames the pre-unmount callback; the environment-file writing implementation is unchanged.

Changes: Firefly AIBOX-K3 board configuration

Layer / File(s)	Summary
Board metadata, image notes, and callback config/boards/firefly-aibox-k3.csc	Adds the introduction year and comments about UFS partitioning, sector size, SPI NOR U-Boot, and vendor flasher inputs. Renames the pre-unmount callback without changing its body.

Estimated code review effort: 1 (Trivial) | ~4 minutes

Change: Feature

Possibly related issues

• [Feature Request]: Support Firefly AIBOX-K3 #10955: The issue requests Firefly AIBOX-K3 support. This change documents the board's UFS and vendor SPI NOR setup, though the supplied change summary does not describe additional board-support behavior.

Possibly related PRs

• armbian/build#11100: This PR and #11100 both concern the Firefly AIBOX-K3 configuration and its promotion to .csc.

Suggested reviewers: igorpecovnik

Merge Risk: Minimal · previous review 0519b

The configuration update is mergeable with no identified behavioral risk.

Pre-merge checks: 4

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: promoting the Firefly AIBOX-K3 board configuration to community-supported status.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ This PR has been reviewed and approved — all set for merge!