L
Lion-1209/flashgate
flashgate answers one specific question: the firmware you just built — does
★ 1·更新 2026-10-12
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 1 ★ · Lion-1209/flashgate · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 1 ★ · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
Lion-1209/flashgate;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# flashgate
以下摘录自该仓库的 README(片段)
flashgate answers one specific question: the firmware you just built — does
it actually run on the board?
It automates the whole chain: compile, flash over ST-Link, wait for the
board to report its own identity, then drive the actual feature over the
console and assert on hardware register readbacks. Any broken step ends
with a non-zero exit code and a reason.
build → flash over ST-Link → board boots → evidence → probes → exit code
A remote agent driving the bench over the network (Wi-Fi laptop → wired
bench, OpenOCD backend) — real output:
$ flashgate --board apollo-openocd.yaml verify --all-probes
[verify] apollo-h743: build -> flash -> boot banner -> probes
[build] OK in 1.3s, 0 warning(s)
[flash] Apollo.bin @ 0x08000000 via openocd:port=SWD
[flash] OK (written, verified, started)
FLASHGATE-BOOT board=apollo-h743 git=e87efd8-dirty build=2026-09-16T02:48:14Z rtos=FreeRTOS
[probe] led-demo: LED state-machine set/readback + PWM CCR sanity
step 1: led-demo> led0 breath
board: OK led0 state=BREATH
step 2: led-demo> led0?
board: OK led0 state=BREATH ccr=691 led0 breath
board: OK led0 state=OFF ← readback exposes the silent no-op
The same broken tree is blocked at most twice, then released with a loud
warning — the session can never wedge, and a failure is never silently
swallowed.
One verify at a time per bench: concurrent verifies (a user-level and a
session-level Stop hook firing on the same stop, or a manual run racing
the hook) serialize on an OS-owned lock file under the firmware's
.flashgate/ instead of fighting over the console serial port — the
second one waits (default 300 s, FLASHGATE_VERIFY_LOCK_WAIT), and a
timed-out wait is a truthful exit 6 ("bench busy"), never a misleading
serial error. Register the hook at ONE level only: in the common case
stacking now just costs a redundant second verify; on a very slow bench
it can still exhaust the hook's own subprocess timeout, so it is a
crutch, not a supported setup.
## Verification records
Every verify — passing or failing — leaves an evidence record at
/.flashgate/records/ - - .json: the
per-check verdicts (build/flash/boot/identity/probe:, with
skipped meaning never executed, never a silent absence), the raw
evidence behind them (banner line, SWD signature fields, console tails,
failing probe transcripts), the artifact sha256, and the exact
tree+profile+tool-version identity the verdict applies to. Every record
also carries a coverage block — the "what this PASS proves" statement:
what was verified, what was NOT (physical effects, everything outside
the listed probes, environmental conditions), plus the board profile's
own caveats (coverage.notes) — a green record never reads as "all
functionality passed". The MCP
verify tool returns the same record inline as data.record. Format:
docs/record-schema.md. Keep .flashgate/ in your
firmware repo's .gitignore (the shipped example does), or every record
write churns the fingerprint. A record that cannot be written is a
warning, never a changed exit code — and a crashed run still leaves one.
The newest ~500 records are kept (best-effort pruning). flashgate verify
--json prints this run's record as pure-ASCII JSON on stdout (human logs
it actually run on the board?
It automates the whole chain: compile, flash over ST-Link, wait for the
board to report its own identity, then drive the actual feature over the
console and assert on hardware register readbacks. Any broken step ends
with a non-zero exit code and a reason.
build → flash over ST-Link → board boots → evidence → probes → exit code
A remote agent driving the bench over the network (Wi-Fi laptop → wired
bench, OpenOCD backend) — real output:
$ flashgate --board apollo-openocd.yaml verify --all-probes
[verify] apollo-h743: build -> flash -> boot banner -> probes
[build] OK in 1.3s, 0 warning(s)
[flash] Apollo.bin @ 0x08000000 via openocd:port=SWD
[flash] OK (written, verified, started)
FLASHGATE-BOOT board=apollo-h743 git=e87efd8-dirty build=2026-09-16T02:48:14Z rtos=FreeRTOS
[probe] led-demo: LED state-machine set/readback + PWM CCR sanity
step 1: led-demo> led0 breath
board: OK led0 state=BREATH
step 2: led-demo> led0?
board: OK led0 state=BREATH ccr=691 led0 breath
board: OK led0 state=OFF ← readback exposes the silent no-op
The same broken tree is blocked at most twice, then released with a loud
warning — the session can never wedge, and a failure is never silently
swallowed.
One verify at a time per bench: concurrent verifies (a user-level and a
session-level Stop hook firing on the same stop, or a manual run racing
the hook) serialize on an OS-owned lock file under the firmware's
.flashgate/ instead of fighting over the console serial port — the
second one waits (default 300 s, FLASHGATE_VERIFY_LOCK_WAIT), and a
timed-out wait is a truthful exit 6 ("bench busy"), never a misleading
serial error. Register the hook at ONE level only: in the common case
stacking now just costs a redundant second verify; on a very slow bench
it can still exhaust the hook's own subprocess timeout, so it is a
crutch, not a supported setup.
## Verification records
Every verify — passing or failing — leaves an evidence record at
/.flashgate/records/ - - .json: the
per-check verdicts (build/flash/boot/identity/probe:, with
skipped meaning never executed, never a silent absence), the raw
evidence behind them (banner line, SWD signature fields, console tails,
failing probe transcripts), the artifact sha256, and the exact
tree+profile+tool-version identity the verdict applies to. Every record
also carries a coverage block — the "what this PASS proves" statement:
what was verified, what was NOT (physical effects, everything outside
the listed probes, environmental conditions), plus the board profile's
own caveats (coverage.notes) — a green record never reads as "all
functionality passed". The MCP
verify tool returns the same record inline as data.record. Format:
docs/record-schema.md. Keep .flashgate/ in your
firmware repo's .gitignore (the shipped example does), or every record
write churns the fingerprint. A record that cannot be written is a
warning, never a changed exit code — and a crashed run still leaves one.
The newest ~500 records are kept (best-effort pruning). flashgate verify
--json prints this run's record as pure-ASCII JSON on stdout (human logs
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/lion-1209-flashgate/)
- 来源
- awesome · https://github.com/Lion-1209/flashgate
- 按领域浏览
- MCP 服务
- Traction
- 1 ★
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。