Files
STM32F4-Base/test
wandering1 3e80c301e5 fix(ioboard): repair three judgement bugs in the DI/DO board suite
The suite ran on the bench and reset the target every 56 seconds, right
after the last Phase 3 assertion. Root cause was the suite itself: the
worker thread entry function returned instead of calling vTaskDelete.
Returning from a FreeRTOS task function is undefined behaviour, and on the
Cortex-M4F port the saved LR points at prvTaskExitError, so the return
trips configASSERT. This project routes configASSERT to
vApplicationAssertFailed, which resets the MCU. The assert banner never
reached the console because the reset happened 0.27 s after the last
line, while its bytes were still queued.

Two assertions were also wrong in ways that hid real state:

- The "which relay is commanded" mask was computed as MASK_ALL & ~bit,
  i.e. the complement of what the comment claimed, so the suite reported
  the three idle relays as commanded and failed every Phase 3 row even
  though the shadow register was correct.
- The "other relays stay released" check was written as (a|b)==b, which
  is the same predicate as "at least bit b set" and therefore duplicated
  the check above it instead of testing the remaining channels. It now
  asserts (active & ~only)==0.

Phase counters are also reset on entry to each phase. The report macro
only prints, so without a reset each phase summary carried every earlier
phase's failures and Phase 2 read 44/62 with no failures of its own.

Hard-coded 0x0F masks are replaced by IOBOARD_TEST_DO_MASK_ALL.

Bench result after the fix: the suite completes in about 54 s with one
reset cause line (boot only), and prints Phase 4, the final release check
and "IOBOARD Tests: 17/17 PASSED". Phase 2 moves to 21/21 and Phase 3 to
16/16.

Still unverified, and not claimed as passing: the eight DI channel order
needs a person to short the terminals, and the relay polarity needs a
person to hear the contacts. Note that ioboard_do_read_level reads ODR,
so the Phase 3 level assertions prove write intent propagation, not
electrical actuation.

Keil build with the suite enabled: Code=264880, 0 errors 0 warnings.
Product build after the suite switch is restored: Code=257932, unchanged.
2026-11-16 19:58:52 +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