firmwareloop 0.0.9__tar.gz → 0.0.11__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {firmwareloop-0.0.9/firmwareloop.egg-info → firmwareloop-0.0.11}/PKG-INFO +78 -19
- firmwareloop-0.0.9/PKG-INFO → firmwareloop-0.0.11/README.md +361 -330
- firmwareloop-0.0.9/README.md → firmwareloop-0.0.11/firmwareloop.egg-info/PKG-INFO +389 -302
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/pyproject.toml +1 -1
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/__init__.py +1 -1
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/common/fw.psm1 +13 -5
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/fw_mcp_server.py +6 -6
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/setup-agent-mcp.ps1 +64 -30
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/LICENSE +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/firmwareloop.egg-info/SOURCES.txt +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/firmwareloop.egg-info/dependency_links.txt +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/firmwareloop.egg-info/entry_points.txt +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/firmwareloop.egg-info/requires.txt +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/firmwareloop.egg-info/top_level.txt +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/setup.cfg +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/acceptance-scenario.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/build.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/can.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/check-qoder-mcp.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/common/build-backends.psm1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/common/uart_probe.py +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/doctor.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/flash.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/instrument_cli.py +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/lib/__init__.py +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/lib/instruments.py +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/logic_capture.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/logic_decode.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/reset.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/test-backends.ps1 +0 -0
- {firmwareloop-0.0.9 → firmwareloop-0.0.11}/tools/test.ps1 +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: firmwareloop
|
|
3
|
-
Version: 0.0.
|
|
3
|
+
Version: 0.0.11
|
|
4
4
|
Summary: AI Agent Firmware Development and Lab Automation Platform (Dual-Tier MCP Server)
|
|
5
5
|
Author-email: WeilinZhang <19523330249@163.com>
|
|
6
6
|
License: MIT
|
|
@@ -104,41 +104,92 @@ FirmwareLoop 为 AI Agent 暴露了开箱即用的 MCP 工具,涵盖 5 大核
|
|
|
104
104
|
|
|
105
105
|
---
|
|
106
106
|
|
|
107
|
-
##
|
|
107
|
+
## 极速起步(3 步搞定)
|
|
108
108
|
|
|
109
|
-
|
|
110
|
-
1. **上层工作流 MCP (`fwloop` / `firmwareloop`)**:面向工程构建(Keil/CMake/Make 等 7 大后端)、pytest 12项自动化 HIL 测试、安全测量与全链路验收。
|
|
111
|
-
2. **下层硬件驱动 MCP (`agentic-hil`)**:面向物理探针(ST-LINK / J-Link)、JTAG/SWD 固件刷写、芯片复位、串口会话与符号级断点调试。
|
|
109
|
+
无论你使用 **Google Antigravity**、**Claude Code**、**Qoder** 还是 **Cursor**,只需以下 3 步即可开始 AI 驱动的单片机自动化开发:
|
|
112
110
|
|
|
113
|
-
###
|
|
111
|
+
### 第一步:全局安装核心 CLI 工具
|
|
112
|
+
|
|
113
|
+
从 PyPI 官方源安装(全电脑仅需执行一次):
|
|
114
114
|
|
|
115
|
-
1. 全局安装 CLI 工具到系统(直接从 PyPI 官方源下载):
|
|
116
115
|
```bash
|
|
117
116
|
uv tool install firmwareloop
|
|
118
117
|
uv tool install agentic-hil
|
|
119
118
|
```
|
|
120
119
|
|
|
121
|
-
|
|
120
|
+
---
|
|
121
|
+
|
|
122
|
+
### 第二步:全局注册到各大 AI Agent
|
|
123
|
+
|
|
124
|
+
按你日常使用的 Agent 执行对应的注册命令(全电脑仅需配置一次):
|
|
125
|
+
|
|
126
|
+
1. **Google Antigravity / Gemini CLI(全自动配置,推荐)**:
|
|
127
|
+
```bash
|
|
128
|
+
fwloop setup
|
|
129
|
+
```
|
|
130
|
+
> **说明**:该命令会自动将双层 MCP 写入 Antigravity 全局配置(`~/.gemini/config/mcp_config.json`),并全自动将全套技能包同步到全局 Skill 目录。
|
|
131
|
+
|
|
132
|
+
2. **Claude Code CLI**:
|
|
122
133
|
```bash
|
|
123
134
|
claude mcp add --scope user fwloop -- fwloop
|
|
124
135
|
claude mcp add --scope user agentic-hil -- agentic-hil mcp-stdio
|
|
125
136
|
```
|
|
126
137
|
|
|
127
|
-
3.
|
|
128
|
-
- **GUI 方式**:按快捷键 `Ctrl + Shift + ,`(Mac: `Cmd + Shift + ,`)进入「MCP」->「我的服务」-> 点击「+ 添加」粘贴配置。
|
|
129
|
-
- **工作区方式**:项目根目录放置 `.mcp.json`,Qoder 会自动发现并加载。
|
|
130
|
-
- **CLI 方式**:
|
|
138
|
+
3. **Qoder IDE**:
|
|
131
139
|
```bash
|
|
132
140
|
qoder.cmd mcp add --global fwloop -- fwloop
|
|
133
141
|
```
|
|
134
142
|
|
|
135
|
-
|
|
143
|
+
4. **Cursor / 其他 IDE**(在工程根目录的 `.mcp.json` 中并联配置):
|
|
144
|
+
```json
|
|
145
|
+
{
|
|
146
|
+
"mcpServers": {
|
|
147
|
+
"fwloop": {
|
|
148
|
+
"command": "fwloop"
|
|
149
|
+
},
|
|
150
|
+
"agentic-hil": {
|
|
151
|
+
"command": "agentic-hil",
|
|
152
|
+
"args": ["mcp-stdio"]
|
|
153
|
+
}
|
|
154
|
+
}
|
|
155
|
+
}
|
|
156
|
+
```
|
|
136
157
|
|
|
137
158
|
---
|
|
138
159
|
|
|
139
|
-
###
|
|
160
|
+
### 第三步:在你的单片机工程中开启自动化
|
|
140
161
|
|
|
141
|
-
|
|
162
|
+
进入你的任意单片机工程根目录(如 STM32 Keil / CMake / IAR / PlatformIO 项目):
|
|
163
|
+
|
|
164
|
+
1. 一键生成智能体规范、MCP 描述与台架模板:
|
|
165
|
+
```bash
|
|
166
|
+
fwloop init
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
2. 接入真实硬件(配置串口与探针):
|
|
170
|
+
根据提示打开工程目录下的 `lab/lab.yaml`,填入你的串口号(如 `COM5`)、目标芯片型号(如 `STM32F103C8`)与编译器类型(如 `keil` 或 `cmake`)。
|
|
171
|
+
|
|
172
|
+
3. 打开 AI Agent 对话框,直接用自然语言调度:
|
|
173
|
+
- “*执行 `fw_doctor()` 检查我的硬件和编译器连接状态*”
|
|
174
|
+
- “*帮我编译当前单片机代码,并刷入开发板运行*”
|
|
175
|
+
- “*运行 HIL 自动化测试,抓取串口 Log 并验证开机状态*”
|
|
176
|
+
|
|
177
|
+
---
|
|
178
|
+
|
|
179
|
+
### 核心命令职责速查
|
|
180
|
+
|
|
181
|
+
| 命令 | 适用级别 | 核心作用 | 使用时机 |
|
|
182
|
+
|---|---|---|---|
|
|
183
|
+
| **`fwloop setup`** | **系统全局级** | 给各大 Agent(Antigravity / Claude Code)配置全局 MCP 与同步技能包 | **全电脑只需跑 1 次** |
|
|
184
|
+
| **`fwloop init`** | **工程项目级** | 在当前单片机代码目录下生成 `AGENTS.md`、`GEMINI.md`、`CLAUDE.md` 与台架配置 | **每个新单片机项目跑 1 次** |
|
|
185
|
+
| **`fwloop doctor`** | **环境诊断** | 检查编译器(Keil/GCC)、Python 环境、串口与探针连接健康度 | 随时排查环境时使用 |
|
|
186
|
+
| **`fwloop update`** | **自动更新** | 一键自动拉取最新代码并热重载依赖 | 升级工具版本时使用 |
|
|
187
|
+
|
|
188
|
+
---
|
|
189
|
+
|
|
190
|
+
### 进阶:免克隆即时运行模式(Zero-Clone Mode)
|
|
191
|
+
|
|
192
|
+
如果不想使用全局安装,也可配置 Agent 通过 `uvx` 临时拉取即时运行:
|
|
142
193
|
|
|
143
194
|
1. Claude Code CLI 注册:
|
|
144
195
|
```bash
|
|
@@ -146,7 +197,7 @@ claude mcp add fwloop -- uvx firmwareloop
|
|
|
146
197
|
claude mcp add agentic-hil -- uvx agentic-hil mcp-stdio
|
|
147
198
|
```
|
|
148
199
|
|
|
149
|
-
2.
|
|
200
|
+
2. 工程 `.mcp.json` 配置:
|
|
150
201
|
```json
|
|
151
202
|
{
|
|
152
203
|
"mcpServers": {
|
|
@@ -192,7 +243,15 @@ claude mcp add agentic-hil -- "D:\Tools\FirmwareLoop\.venv\Scripts\agentic-hil.e
|
|
|
192
243
|
fwloop init
|
|
193
244
|
```
|
|
194
245
|
|
|
195
|
-
2.
|
|
246
|
+
2. 自动升级至 PyPI 最新版本(推荐以下任意一种方式):
|
|
247
|
+
```bash
|
|
248
|
+
uv tool upgrade firmwareloop
|
|
249
|
+
```
|
|
250
|
+
或者一键升级全部已安装工具:
|
|
251
|
+
```bash
|
|
252
|
+
uv tool upgrade --all
|
|
253
|
+
```
|
|
254
|
+
或者使用内置热更新命令:
|
|
196
255
|
```bash
|
|
197
256
|
fwloop update
|
|
198
257
|
```
|
|
@@ -277,7 +336,7 @@ claude mcp remove --scope user agentic-hil
|
|
|
277
336
|
├── demo-firmware/ 示例固件(CMake;宿主编译模拟 MCU,闭环验证载体)
|
|
278
337
|
├── demo-make/ 示例固件(Make;构建测试载体)
|
|
279
338
|
├── docs/ DEPENDENCY_MATRIX / REUSE_PLAN / V0.0.2_GAP_VERIFICATION
|
|
280
|
-
├── pyproject.toml 标准 Python 包配置与 CLI 入口声明 (v0.0.
|
|
339
|
+
├── pyproject.toml 标准 Python 包配置与 CLI 入口声明 (v0.0.11)
|
|
281
340
|
├── .mcp.example.json 双层 MCP 配置模板(firmwareloop + agentic-hil)
|
|
282
341
|
├── AGENTS.md 通用智能体规范(Antigravity / Qoder / Cursor 等)
|
|
283
342
|
├── CLAUDE.md Claude Code CLI 指南
|
|
@@ -287,7 +346,7 @@ claude mcp remove --scope user agentic-hil
|
|
|
287
346
|
|
|
288
347
|
---
|
|
289
348
|
|
|
290
|
-
## 能力验证状态(v0.0.
|
|
349
|
+
## 能力验证状态(v0.0.11)
|
|
291
350
|
|
|
292
351
|
> 状态定义:`Implemented`(已实现)/ `Simulator Validated`(模拟验证)/
|
|
293
352
|
> `Real Hardware Validated`(真机验证)/ `Experimental` / `Not Implemented`
|