fix(dwt): stop resetting CYCCNT, a counter six modules share

Three of the six DWT CYCCNT users wrote the counter to zero on init:
console_log, net_latency_test and ch395f_reuse_bench. Every one of them
only ever takes the difference (CYCCNT - t0) against a local snapshot, so
the reset bought nothing and instead caused a bogus ~2^32 delta for
anyone who sampled across it. That delta trips the task_prof glitch guard
(TASK_PROF_GLITCH_CYC = 10 s worth of cycles), which discards the sample,
so a whole worst-case measurement could vanish silently.

All three call sites now leave the counter alone; the shared contract is
"enable only, never reset", documented at each of the six users. The
documented behaviour in the link latency test guide (section 4.3) is
updated to match.

Net source change is three deleted lines, no new executable code.

Verification:
- grep for a zero assignment to CYCCNT across the tree: no hits left.
- Keil build: Code=257932 RO-data=32108 RW-data=2104 ZI-data=152688,
  0 errors 0 warnings.
- Host unit tests: console_log 153/153, task_prof 27/27, ioboard 100/100,
  sb_link 164/164.
- Four console_log assertions pinned the absolute number of DWT register
  touches; dropping the reset write lowers it by one, so their expected
  counts move from 3 to 2 (and 4 to 3 for TC-CONLOG-093). The test text
  now says why the third write disappeared.
- check_doc_links: 6 known issues, unchanged from baseline.
This commit is contained in:
2026-11-16 19:58:44 +08:00
parent e4981aa2f6
commit cc7f17f231
7 changed files with 41 additions and 16 deletions
+5 -1
View File
@@ -50,7 +50,11 @@ void lat_time_init(void)
return;
}
CoreDebug->DEMCR |= CoreDebug_DEMCR_TRCENA_Msk; /* 使能 DWT 的前置条件 */
DWT->CYCCNT = 0U;
/* 不清零 CYCCNT:本模块只用前后两次读数的差值,基准是各自快照而非绝对零点。
* 而 CYCCNT 是全内核共享的单一计数器,本仓另有 console_log.c(发送超时)、
* App/util/task_prof.c(探针最坏值)、IOBOARD 驱动(微秒延时)、
* ScreenLink 驱动(组帧耗时)四处同样取差值;清零会让它们"在途"的基准失效,
* 差值变成接近 2^32 的回绕并被各自的守卫静默丢弃。2026-11-16 统一为"只开不清"。 */
DWT->CTRL |= DWT_CTRL_CYCCNTENA_Msk;
s_dwt_ready = 1;
}