Files
STM32F4-Base/test
wandering1 515db819ab feat(ui): fold board inputs and outputs into the telemetry page
The 12 board-level rows now live at the end of the 遥信量 page instead of
a separate 开入开出 page: 8 opto inputs (DI_A..DI_H) and 4 relay outputs
(KO6/TRIP/ERT/CLZ). 33 rows become 45, five pages become six. The
standalone page, its menu entry, its golden references and both build
registrations are removed.

Folding the display is not folding the point table. The board rows
render from dio_di_* / dio_do_* and stay out of yx_bits / yx_valid /
yx_dp: any change to those carriers is provably absent from this diff.
IEC 104 mapping and YX_VALID_MASK are untouched, so nothing new is
reported to a master station.

Input polarity was wrong and is fixed here. On this board a 24 V input
drives the opto, which pulls the 74HC165 pin LOW, so the raw mask is
inverted relative to "has signal". The bit assembly only reordered bits;
nothing converted the level. The screen showed 分 on every channel no
matter what the operator drove in. Polarity now converts once, in the
driver, behind IOBOARD_DI_LEVEL_ACTIVE (0 = active low), so callers see
1 = has signal for both inputs and outputs.

Verified on the board: page 5 shows YX33 followed immediately by DI_A,
crossing the 33-point boundary with no drift; DI_C reads 合 because the
operator's signal is on channel C, the other seven read 分; page 6 shows
DI_H then all four outputs 释放. Page rows end at y=134, the footer
starts at y=144.

Input bit order is only partly verified: channel C was confirmed against
a real signal, the other seven have not been exercised channel by
channel. The board detects the presence of 24 V, not contact closure,
and the output rows show the shadow register (our intent) rather than
mechanical contact feedback. All three limits are recorded in the page
header and in the IOBOARD README.

Also adds a polarity guard to the host tests: the input polarity was
flipped once already, and until now no assertion would have caught a
silent re-flip, since only the DO side was pinned.
2026-11-16 23:30:35 +08:00
..

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