e4981aa2f6
AGENTS.md stopped being the store of record for build steps, Python env, hardware pins, doc conventions, log cost and task ownership. Those facts already live in docs, skills and role files; the entry file now only points at them. This commit moves every reference that used to name the entry file to the authoritative landing point, so a reader who follows a link arrives at the fact instead of at a sentence that no longer exists. What changed is links and prose, not behaviour. Code, scripts and tests only have comment and docstring lines touched; the only non-comment edit in the whole changeset is one note string inside the generated pin table JSON, and its generator was changed in the same step so the two stay byte-identical. New landing points created before the references were retargeted: - The console single-writer log design doc, section 7.1, is now the single authority for log cost: about 90 B flash and 216 B stack per DBG_ line, and the rule that deep call chains must predefine DBG_LINE_BUF_MAX. It also carries the full list of the twelve translation units that have tightened it, plus the grep command that decides the truth if the list and the code ever disagree. - The document writing standard, section 2, now holds the BOM list. - keil-build skill gains an exit code table: 0 success, 1 build failure, 2 BuildEnvError, 3 usage, 4 build lock held. This corrects a belief that was never actually written down anywhere: exit 2 does not simply mean environment error, argparse also exits 2 and the wrapper script was remapped so the two no longer collide. Regenerated and checked byte for byte: - The end-to-end architecture SVG in docs/images from its generator. - tools/netlist_semantics/pinout_kb.json from gen_kb.py. Both are idempotent; running the generators again produces no diff. Deliberately not touched, because machines read them: - scripts/check_bom_drift.py joins every line containing BOM and asserts four paths are present, so the entry file BOM line must stay one line. - scripts/gen_task_table.py reads the TASK_TABLE anchors directly. - scripts/rename_maps and scripts/archive keep their historical wording; they describe what happened, not what is true now. Verified: doc links report the same six pre-existing findings as the base commit and no new ones, generated-fresh passes, bom drift is clean across 101 files, and AGENTS.md itself is unchanged in this commit.
App/protocol/ — 通信协议(纯逻辑层)
存放跨接口复用的协议逻辑(解析 / 组帧 / 状态机),零 I/O、依赖注入, 可被任意任务/接口承载;板端 I/O 胶水在对应 task(如
App/task/iec104_serv.c)。 其余协议实现暂分散在:
- RS-485 侧:
App/task/rs485_task.c(CRC 在驱动内)- 网络侧:
Drivers/BSP/NET/- 远端显示:
docs/UI设计/RemoDispBus协议与接收设计说明.md
已落地协议
| 子目录 | 协议 | 说明 |
|---|---|---|
iec104/ |
IEC 60870-5-104 被控站(TCP 工厂默认 2404 上行) | 纯逻辑三件套(asdu/pts/link,零 I/O,数据源 vtable 注入)→ 全栈主机侧纯逻辑单测;板端胶水与点表决策 → docs/子系统设计/IEC104上行设计说明.md |
何时使用本目录
当出现跨接口复用的协议逻辑(如统一的帧编解码器、协议状态机)时,落到此处, 避免散落到各 task 里。新增后请在本 README 补一行说明。