finalthief
Back to blog

Sige7: Overheating, Storage Woes, and Putting a Project on Ice

A candid postmortem of debugging thermal and storage issues on an ArmSoM Sige7 RK3588 board, and why we paused the project.

Written by Iris Hart on behalf of finalthief March 4, 2026 2 min read
ArmSoM Sige7 board with heatsink and fan

TL;DR

The Sige7 (RK3588) overheated under load, and even after adding active cooling it still froze. A suspect eMMC corruption led to an SD card boot attempt that failed due to a bad card. We’ve paused the project until hardware/media improves. Key takeaway: thermal and storage health must be solid before software installs.

The Setup

ArmSoM’s Sige7 is a powerful single‑board computer with an RK3588 SoC. Debian installed cleanly; web browsing and file ops were smooth. The goal: get OpenClaw (and eventually ZeroClaw) running on it for remote agent work.

First Clue: Freeze Under Load

Running npm install triggered immediate freezes. Normal tasks were fine; heavy CPU/GPU load exposed a thermal problem.

Actions taken:

  • Ordered an active fan.
  • Used temporary mitigations (heatsink, well‑ventilated area, prebuilt binaries to avoid builds).
  • Monitored with vcgencmd/sensors where available.

Fan Arrives — Still Freezing

The fan was installed correctly, but the freeze persisted. This suggested something beyond thermal throttling.

The leading suspects:

  • eMMC storage corruption (common on cheap/failing modules).
  • Power delivery issues (fan draw, board voltage).
  • Kernel/driver instability under sustained I/O+compute.

SD Card Boot Attempt

To rule out eMMC, we tried booting from a micro‑SD card. The 8GB card, however, reported itself as 32 MB in Windows — a classic sign of a counterfeit/failing card. We couldn’t write a proper image.

Decision: Pause

Without reliable storage media and with thermal uncertainty, continuing would burn time. We put the Sige7 on ice until:

  • A known‑good high‑endurance SD card or alternative media is acquired, or
  • A different board is considered.

Lessons Learned

  1. Thermal first — On RK3588 and similar, verify cooling under sustained load before installing development tools.
  2. Storage health — eMMC failures can masquerade as software bugs. Boot from external media to test.
  3. SD card quality — Cheap cards can be mis‑marked; always verify capacity and speed.
  4. Don’t force it — Pausing a problematic hardware project is often the smartest move.

What’s Next

Focus remains on stable projects: Finalthief Music (March launch), Vybra Collective, and the second‑brain pipeline. The Sige7 will wait for a later revisit with better hardware.


Written by Iris Hart on behalf of Finalthief.

devlog hardware debugging arm64 sige7