ARM64 · ROCKCHIP · EDGE LINUX
Build evidence,
not assumptions.
Technical notes for bringing up, measuring, and deploying ArmSoM RK3576 and RK3588 systems. Every guide focuses on a reproducible starting point and the evidence needed to validate it.
Browse the seriesTHE SERIES
RK35xx technical articles
How to Choose RK3576 or RK3588 for an Edge Linux Design
Select the platform from interfaces, memory topology, media paths, and lifecycle constraints rather than a TOPS headline.
Read note →First Boot and Serial Recovery on ArmSoM RK3576 and RK3588 Boards
Establish a repeatable serial-first bring-up workflow for Sige5, CM5, Sige7, AIM5, and AIM7 deployments.
Read note →Device Tree Overlays for GPIO I2C and SPI on RK3576 and RK3588
Use overlays and pin control deliberately when extending an ArmSoM RK3576 or RK3588 design.
Read note →Building a Reproducible Camera Pipeline with V4L2 and GStreamer
Move from sensor detection to a debuggable capture pipeline without assuming a camera module or format.
Read note →Deploying an RKNN Model at the Edge without Inventing Benchmarks
Build an auditable inference path for ArmSoM RK3576 and RK3588 devices while separating vendor claims from measured results.
Read note →DRM KMS Multi Display Bring Up on Rockchip RK3588 and RK3576
Bring up displays with the Linux DRM model, connector state, and device-tree routing in view.
Read note →Hardware Video Encode and Decode Pipelines for Rockchip Linux
Design media pipelines around caps negotiation, buffers, and supported codecs instead of unverified frame-rate claims.
Read note →Production Friendly Containers for ArmSoM Edge Applications
Package an ARM64 edge service with explicit device access, image provenance, and a practical update path.
Read note →Boot Media and eMMC Flashing Safety for Rockchip ArmSoM Platforms
Create a safer flashing procedure that preserves evidence and avoids treating recovery tooling as a universal fix.
Read note →Thermal and Performance Observability for RK3576 and RK3588 Edge Systems
Measure an ArmSoM edge system as a thermal and workload-dependent system, not a single benchmark number.
Read note →EDITORIAL STANDARD
Designed for review before deployment.
Claims are tied to documented capabilities. Commands are starting points, not unreported test results. Each article includes troubleshooting, references, and a pre-publication checklist.