COMPANY NEWS · 2026-10-12

Winge Completes Headless OpenHarmony 6.1 Stage-0 Validation on RK3588

Beijing Winge Technology Co., Ltd. completed minimum headless Stage-0 validation of OpenHarmony 6.1 on the specified RK3588 board.

Published: 2026-10-12Evidence cutoff: 2026-10-12 19:43:05 +08:00RK3588 · OpenHarmony 6.1 · Build22

Milestone summary

Build22 booted Linux 5.10.210 and OpenHarmony init from SD, mounted the root filesystem, /vendor, and /data, opened a serial root shell, and completed 480 seconds of continuous logging. This is an engineering milestone, not completion of all peripherals or a production BSP.

What this stage verified

  • Pinned OpenHarmony-v6.1-Release and the RK3588 AArch64 build target
  • Generated and inspected Loader, U-Boot, boot, and system images
  • Read back the primary and backup GPT plus 12 images with matching SHA-256 values
  • Automatically booted Linux 5.10.210 from SD through U-Boot
  • Mounted the root filesystem, /vendor, and /data from SD
  • Started OpenHarmony init and obtained a serial root shell
  • Captured 480 seconds without kernel panic, Oops, or critical-service fatal
  • Did not write to or erase onboard eMMC

Why RK3588 adaptation requires layered verification

A board port combines Loader, U-Boot, device tree, kernel drivers, partition tables, storage paths, and system services. A successful compile is not a substitute for media readback, boot logs, and on-board checks.

Versioned patches, pinned hashes, pre-write media checks, post-write readback, and automated serial evaluation keep each iteration tied to specific inputs and results.

What the 480-second Build22 run proves

Build21 triggered an intentional kernel crash near 332 seconds after a service-failure cascade. Build22 changed failure propagation for the headless Stage-0 profile, passed the former failure point, and completed the 480-second window.

Automated analysis reported PASS_STAGE0, boot_count=1, and fatal_hits=[]; an active probe still confirmed the shell at 447.82 seconds. This is not a long-duration or full-function acceptance result.

Current evidence scope for Build23

FaultLogger located the direct foundation failure in the SELinux restorecon path. Patch 0027 skips file-contexts handle initialization when SELinux is disabled while retaining the original path for SELinux-enabled products.

Build23 completed a full build and passed static checks for image hashes, GPT, extlinux, SD storage paths, and patch markers. Its evidence does not include an on-board regression, so the public result remains the Build22 on-board run.

How Winge approaches OpenHarmony board adaptation

Winge follows a build–image inspection–safe write–on-board boot–log analysis–regression workflow and records each conclusion against a specific version, board, medium, and test condition.

  • OpenHarmony system customization and RK3588 BSP work
  • Loader, U-Boot, extlinux, and GPT boot chains
  • HDF and Linux driver adaptation
  • System images and guarded media-writing tools
  • Serial, FaultLogger, and native crash analysis

Related services and references

OpenHarmony, Rockchip, RK3588, and related names and marks belong to their respective owners. This page records independent engineering work by Beijing Winge Technology Co., Ltd. and does not imply participation, approval, or endorsement by those owners.

DIRECT CONTACT

Discuss an RK3588 OpenHarmony adaptation

Share the board model, hardware revision, source or BSP, boot assets, serial logs, peripheral list, and acceptance criteria. Phone, email, WeChat, and WhatsApp are available directly on this page.

Online
Phone
13910119357
WeChat
WhatsApp
Winge Technology WhatsApp QR code Scan or click to contact us
Top