2b466b85f0
New read-only content page under 实时数据 → 开入开出 showing the board's
8 opto inputs (DI_A..DI_H, 合/分) and 4 relay outputs (KO6/TRIP/ERT/CLZ,
吸合/释放) as a 12-row list, 8 rows per page, 2 pages.
Data path reuses the existing de-bounced input poll instead of adding a
second hardware reader:
defaultTask (50 ms) → ioboard_di_snap_publish() → de-bounced snapshot
→ ioboard_di_snap_lookup() [new registration channel]
→ ui_data_feed_tick() (uiTask, 200 ms)
→ ui_data_rt_t.dio_di_* / dio_do_*
No new critical sections, no new hardware access on the UI path. Outputs
come from the volatile shadow register (a memory read, no lock).
Semantic honesty, recorded in ui_page_di_do.c and README §6:
· Output state is the software shadow register (ODR mirror), NOT a
mechanical contact feedback — this platform has no auxiliary contact
readback path. ioboard_do_read_level() also reads ODR, so comparing
the two is tautological.
· IOBOARD_DO_LEVEL_ACTIVE polarity has not been checked against the
schematic.
· Input bit order has not been verified by manual shorting. The
2026-11-16 run read 0x00 eight times because the operator had no time
to short each channel — the data path itself was fine.
· Board-level inputs are deliberately kept out of the 33-point telemetry
bitmap (IEC 104 point-table semantics); the two have no mapping.
Invalid snapshots render "--", never 合/分 or 吸合/释放: painting "no data"
as "all inputs released" would tell the field the inputs are open when we
simply failed to read them.
Board-verified 2026-11-16: page 1 shows 分 on all 8 inputs, page 2 shows
释放 on all 4 outputs, page footer and paging correct. Input bit order
still pending manual shorting.
Also: regenerate ui_font_cn_12 for 吸/释, add golden references for both
pages, align check_menu_rows.py L2 geometry with the now-4-item submenu,
and register the new source file in both the Keil project and CMake.
Reviewed independently; zero blocking findings.
test/ — 测试代码与主机端脚本
测试分两部分,物理隔离在两个子目录:
board/—— 板端测试套件(.c/.h,编入固件由 testTask 执行)host/—— 主机端脚本(.py,PC 侧驱动板子并判读结果)
目录结构
| 目录 | 内容 | README |
|---|---|---|
board/ |
板端测试套件(编入 Keil 工程,占 RAM) | board/README.md |
host/ |
PC 端测试/判读脚本(Python) | host/README.md |
run_all_suites.py |
多套件回归编排(改宏 → 构建 → 烧录 → 采集,try/finally 保证还原开关);--check-build = 只编译不烧录(纯离机) |
本文 §多套件回归 |
运行方式
# /serial-boot-test 一键闭环(推荐)
& '.venv\Scripts\python.exe' .dsh/skills/serial-boot-test/scripts/run_boot_test.py
# 单独校验日志
& '.venv\Scripts\python.exe' .dsh/skills/serial-boot-test/scripts/verify_log.py <日志文件>
# 多套件回归编排(需真机;自动改开关 + 构建 + 烧录 + 采集,结束后还原)
& '.venv\Scripts\python.exe' test/run_all_suites.py
& '.venv\Scripts\python.exe' test/run_all_suites.py --suites STORAGE,GD5F
& '.venv\Scripts\python.exe' test/run_all_suites.py --dry-run # 只看计划
# 只编译不烧录(不需要 MCU / 串口 / ST-LINK,验证 4 套件可编译性)
& '.venv\Scripts\python.exe' test/run_all_suites.py --check-build
退出码约定:0=PASS / 1=FAIL / 2=采集或烧录错误 / 3=用法或预检错误。
多套件回归(run_all_suites.py)
套件互斥(编译期 #error)意味着跑 4 个套件要手工循环 4 轮。本脚本把它编排成一条
命令,并且无条件还原 test_config.h——跑完忘还原 = 测试固件进库,这是它存在的
核心理由(与提交期门禁 test-suite-switch 互为独立防线)。
⚠️ 每轮要真机烧录 + 采集,4 套件约数分钟起;破坏性套件还会改设备持久状态。 仅回归窗口用,绝不挂 pre-commit。
--check-build 则相反:只改宏 + /keil-build,不烧录不采集,无需任何硬件,用于防止
"测试套件长期编不过而无人知"(2026-08~09 CH395F 套件实例)。改动 test/board/ 下测试
代码后建议先跑它——实测 4 套件均 BUILD_OK: 0 errors, 0 warnings。
⚠️ 注意
- 本目录被 pre-commit 门禁排除(测试代码不受 C 规范约束)
board/套件占用 RAM,启用前先核算预算(见docs/内存管理/)- Keil 工程已同步:
board/下 7 个.c编入MDK-ARM/STM32F4-Demo.uvprojx, IncludePath 含../test/board;移动文件须同步改工程文件 - 套件选择开关:
board/test_config.h的TEST_SUITE_*(互斥,一次只启用一个) - 测试缓冲用分 Phase 复用静态缓冲(避免
L6406E溢出)
相关文档
docs/测试说明/流程与规范/测试开发标准流程.md— 测试验证分层与门禁决策表docs/测试说明/流程与规范/自动化测试流程.md—/serial-boot-test细节与失败模式- 各模块测试指南:
docs/测试说明/板级测试/*_Test_Guide.md docs/测试说明/专项验证/链路延迟测试说明.md