BootHarbor

English | 简体中文

BootHarbor is a board-focused bring-up and recovery lab for embedded Linux systems. The repository follows one board path from BootROM and SPL through U-Boot, Linux, and userspace health reporting, with update, rollback, recovery, and driver-facing integration kept in view.

Table Of Contents

• BootHarbor
  • Table Of Contents
  • What This Project Is
  • Quick Start
  • Design Philosophy
  • Architecture
  • Feature Support
  • Usage
  • System Requirements
  • FAQ
  • License

What This Project Is

BootHarbor is a systems repository for board bring-up, boot flow inspection, and recovery-path work.

The repository keeps these parts in one place:

• SPL and U-Boot integration for a board target
• boot state and slot selection
• storage and environment layout
• Linux handoff and userspace success marking
• rollback and recovery behavior after a failed update
• board-level notes, logs, tests, and walkthroughs

Quick Start

git clone https://github.com/Zw-awa/BootHarbor.git
cd BootHarbor

Start with:

• this README for project scope
• board documents for target-specific notes
• usage and walkthrough documents for boot, rollback, and recovery paths

Design Philosophy

• Keep the full boot path visible from BootROM to userspace.
• Keep update, rollback, and recovery in the same system path.
• Keep board assumptions explicit.
• Keep driver and platform work tied to real device behavior.
• Keep failure cases visible alongside success cases.

Architecture

BootHarbor is organized around a board-oriented boot and recovery chain:

BootROM
  -> SPL
    -> U-Boot
      -> Linux kernel
        -> rootfs / userspace
          -> health report
            -> boot state update

The runtime model centers on:

• boot-stage handoff
• image and partition layout
• boot-state tracking
• userspace health reporting
• rollback and rescue behavior
• driver or platform integration points tied to the board path

Feature Support

Repository content includes:

• boot flow inspection
• SPL and U-Boot integration
• update and rollback model
• recovery-path notes
• driver or platform integration records
• logs, tests, and walkthroughs

Usage

BootHarbor is intended as a board bring-up and recovery reference.

Typical use includes:

• checking the boot path for a supported board
• reviewing image layout and boot-state behavior
• following update and rollback walkthroughs
• comparing normal boot logs with failure and recovery logs
• checking driver or platform integration notes tied to that board path

System Requirements

General environment requirements:

• a Linux host or WSL environment
• serial console access for board bring-up
• a supported target board
• access to the target boot media such as SD, eMMC, SPI NOR, or equivalent storage
• a way to flash, recover, or replace boot media during tests

Board-specific requirements will be listed with each supported target.

FAQ

• Which board is BootHarbor built around The first public target board has not been published yet.
• Does BootHarbor stop at U-Boot No. The repository follows the path through Linux and userspace health reporting, and may include board-tied driver or platform integration notes.
• Will BootHarbor cover failed updates only, or also failed boots Both belong to the same recovery path. The repository keeps boot failure, rollback, rescue, and health-state behavior in the same board story.
• Is QEMU part of BootHarbor It may appear where it helps inspection or testing, but the repository is organized around board bring-up rather than emulation by itself.

License

BootHarbor uses GPL-2.0-only.

See LICENSE.