dsh-stm32 0.1.1 → 0.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (62) hide show
  1. package/README.md +98 -31
  2. package/README_EN.md +96 -29
  3. package/docs/development-notes.md +837 -4
  4. package/docs/reading-guide.md +759 -0
  5. package/lib/commands/register.js +49 -0
  6. package/lib/data/chips.js +147 -30
  7. package/lib/data/clock-f1.js +158 -0
  8. package/lib/data/cmsis-sources.js +237 -42
  9. package/lib/data/device-facts.js +201 -0
  10. package/lib/data/stm32f1.js +130 -0
  11. package/lib/data/svd.js +627 -0
  12. package/lib/engine/assets.js +924 -0
  13. package/lib/engine/breakpoints.js +242 -0
  14. package/lib/engine/build.js +115 -16
  15. package/lib/engine/cache.js +56 -0
  16. package/lib/engine/clock-plan.js +608 -0
  17. package/lib/engine/cmake-sources.js +428 -0
  18. package/lib/engine/debug-session.js +153 -5
  19. package/lib/engine/debug.js +114 -15
  20. package/lib/engine/doctor.js +395 -4
  21. package/lib/engine/fetch.js +174 -30
  22. package/lib/engine/flash.js +70 -9
  23. package/lib/engine/generate.js +11 -0
  24. package/lib/engine/hal-chip.js +230 -0
  25. package/lib/engine/ioc-plan.js +33 -7
  26. package/lib/engine/msys2-install.js +332 -61
  27. package/lib/engine/probe-error.js +212 -0
  28. package/lib/engine/probe-session.js +311 -0
  29. package/lib/engine/project-export.js +129 -0
  30. package/lib/engine/register-clock.js +132 -0
  31. package/lib/engine/register-linker.js +129 -0
  32. package/lib/engine/register-template.js +115 -20
  33. package/lib/engine/regs.js +2 -0
  34. package/lib/engine/rtt.js +600 -0
  35. package/lib/engine/scaffold.js +104 -28
  36. package/lib/engine/zip.js +142 -0
  37. package/lib/index.js +10 -0
  38. package/lib/skill/stm32-workflow.js +3 -3
  39. package/lib/tools/assets.js +341 -0
  40. package/lib/tools/build.js +12 -0
  41. package/lib/tools/cache.js +47 -8
  42. package/lib/tools/debug-session.js +40 -5
  43. package/lib/tools/debug.js +41 -4
  44. package/lib/tools/doctor.js +22 -2
  45. package/lib/tools/flash.js +15 -3
  46. package/lib/tools/generate.js +3 -0
  47. package/lib/tools/ioc-apply.js +2 -0
  48. package/lib/tools/ioc-inspect.js +2 -0
  49. package/lib/tools/ioc-plan.js +198 -4
  50. package/lib/tools/project-create.js +50 -1
  51. package/lib/tools/project-export.js +100 -0
  52. package/lib/tools/regs.js +453 -61
  53. package/lib/tools/route-plan.js +3 -0
  54. package/lib/tools/rtt.js +347 -0
  55. package/package.json +5 -3
  56. package/templates/register/CMakeLists.txt +25 -6
  57. package/templates/register/Core/Inc/rtt.h +103 -0
  58. package/templates/register/Core/Src/main.c +43 -9
  59. package/templates/register/Core/Src/rtt.c +297 -0
  60. package/templates/scaffold/RTT.md +86 -0
  61. package/templates/scaffold/cmake/user/CMakeLists.txt +7 -0
  62. package/templates/scaffold/openocd.cfg +8 -0
@@ -12,6 +12,7 @@
12
12
  * /stm32-build [<工程目录>] [--clean] 编译(默认走 CMake+Ninja 的 build/Debug)
13
13
  * /stm32-doctor [<工程目录>] 体检:工具链 / 残留进程 / 端口 / .elf / .ioc 告警
14
14
  * /stm32-env [<工程目录>] 工具链体检卡:编译/烧录/调试/生成各缺什么、装在哪、怎么装
15
+ * /stm32-setup [<工程目录>] 一条龙:体检 → 出计划 → 真装(要确认)→ 自检,每步给下一句
15
16
  *
16
17
  * 工程目录缺省取会话当前工作目录;也可以直接写路径(相对路径按当前目录解析)。
17
18
  * 带空格的路径要整段用引号包起来(`"C:/Program Files/.../demo proj"`):切词是引号感知的,
@@ -339,6 +340,54 @@ export function registerCommands(ctx) {
339
340
  }
340
341
  },
341
342
  });
343
+ commands.register({
344
+ definitionId: "dsh-stm32/stm32-setup",
345
+ name: "stm32-setup",
346
+ description: "一条龙:体检 → 出计划 → 真装(要确认)→ 自检;缺什么补什么,齐了就直接说齐了",
347
+ input: { hint: "[<工程目录>] [装]" },
348
+ handler: async (invocation) => {
349
+ try {
350
+ const subprocess = needSubprocess(ctx);
351
+ if (typeof subprocess === "string")
352
+ return err(subprocess);
353
+ const wantsInstall = /(^|\s)装(\s|$)/u.test(invocation.rawInput.trim());
354
+ const lines = ["stm32-setup:"];
355
+ // 1) 体检(与 /stm32-env 同一套门禁)
356
+ const rows = [];
357
+ for (const capability of ENV_CAPABILITIES) {
358
+ const gate = await ensureToolchain(ctx, { capability, envCheck: "warn", signal: invocation.signal });
359
+ rows.push({ capability, gate });
360
+ }
361
+ const allOk = rows.every((row) => row.gate.ok);
362
+ if (allOk) {
363
+ lines.push("1/3 体检:四项能力全齐,不用装。");
364
+ lines.push("2/3 下一步:/stm32-build 就能编译(板子接好时 /stm32-doctor 再看一眼硬件)。");
365
+ return { kind: "success", text: lines.join("\n") };
366
+ }
367
+ // 2) 缺件 → 出计划(与 stm32_env_install 同一个引擎,零副作用)
368
+ const { planOrInstallMsys2 } = await import("../engine/msys2-install.js");
369
+ const plan = await planOrInstallMsys2(subprocess, { mode: "plan", writePath: true, ...(invocation.signal === undefined ? {} : { signal: invocation.signal }) });
370
+ lines.push("2/3 计划:" + plan.message);
371
+ if (!wantsInstall) {
372
+ lines.push("3/3 确认:回「/stm32-setup 装」开始真装(只补缺的包,不升级已装的);装完会自动自检。");
373
+ return { kind: "success", text: lines.join("\n") };
374
+ }
375
+ // 3) 真装(第二次带「装」才走到这里)
376
+ const install = await planOrInstallMsys2(subprocess, { mode: "install", writePath: true, ...(invocation.signal === undefined ? {} : { signal: invocation.signal }) });
377
+ if (!install.ok) {
378
+ lines.push("3/3 安装未完成:" + install.message);
379
+ lines.push(" 下一步:" + install.nextStep);
380
+ return { kind: "success", text: lines.join("\n") };
381
+ }
382
+ lines.push("3/3 安装完成:" + install.message);
383
+ lines.push(" 下一步:/stm32-build 编译;/stm32-doctor 做全量体检。");
384
+ return { kind: "success", text: lines.join("\n") };
385
+ }
386
+ catch (error) {
387
+ return err("stm32-setup 异常:" + (error instanceof Error ? error.message : String(error)));
388
+ }
389
+ },
390
+ });
342
391
  commands.register({
343
392
  definitionId: "dsh-stm32/stm32-env",
344
393
  name: "stm32-env",
package/lib/data/chips.js CHANGED
@@ -1,36 +1,153 @@
1
1
  /**
2
- * L1:芯片型号 → 可用引脚表(数据驱动,加型号只改这里)。
2
+ * L1:引脚名合法性 + 由本机 CubeMX db 派生的引脚表。
3
3
  *
4
- * 目前只覆盖用户明确要求支持的 STM32F103C8T6(蓝丸板,LQFP48)。
5
- * 未知型号一律放行(返回 true)——校验是为了拦住手误,不是为了当数据源;
6
- * 将来加新芯片:在 CHIPS 里补一条即可,不用改逻辑。
4
+ * 用户 2026-10-31「内置表删了吧」之后,这里**不再有任何内置芯片/引脚表**(原来的 CHIPS / KNOWN_CHIPS /
5
+ * findChip 已删)。原因:芯片事实的唯一来源是资源包缓存 device/f1/chips.json,而那份文件只有 pinCount
6
+ * (封装上有多少根脚),没有「这个封装有哪几根 GPIO」的清单——拿 pinCount 去猜 PA0-PB15… 等于又造一张表。
7
+ *
8
+ * 于是分工变成:
9
+ * 1. isKnownPin(pin):只校验**引脚名**是不是 STM32 的合法名(P + A..K + 0..15,虚拟引脚 VP_* 恒放行)。
10
+ * 它拦的是手误(PA99、PZ9、PA-1),不再假装知道某个封装有没有这根脚。
11
+ * 2. deriveChipPinTable():引脚**存在性**只认本机 CubeMX 的 db/mcu XML
12
+ * (<Pin Name="PA1" Position="3"/>,Position>0 才是真实封装引脚)。本机没装 CubeMX / 没有这个 XML 时
13
+ * kind="unknown",notes 里明说「没校验」,绝不拿猜测冒充实测。
14
+ *
15
+ * 放行语义(从第一天就在,不能变):没把握的一律当「不是不存在」,只拦一定写错的东西。
7
16
  */
8
- function port(prefix, from, to) {
9
- const out = [];
10
- for (let index = from; index <= to; index += 1)
11
- out.push(prefix + String(index));
12
- return out;
13
- }
14
- const CHIPS = [
15
- {
16
- cpn: "STM32F103C8T6",
17
- // LQFP48:PA0-15、PB0-15、PC13-15、PD0-1(PD0/PD1 默认是 OSC_IN/OSC_OUT)。
18
- pins: [...port("PA", 0, 15), ...port("PB", 0, 15), "PC13", "PC14", "PC15", "PD0", "PD1"],
19
- flashBytes: 64 * 1024,
20
- ramBytes: 20 * 1024,
21
- },
22
- ];
23
- export function findChip(cpn) {
24
- const wanted = cpn.trim().toUpperCase();
25
- return CHIPS.find((chip) => chip.cpn.toUpperCase() === wanted) ?? null;
26
- }
27
- /** 引脚名是否属于该型号;未知型号或虚拟引脚(VP_*)一律放行。 */
28
- export function isKnownPin(cpn, pin) {
29
- if (pin.startsWith("VP_"))
17
+ import { existsSync, readFileSync } from "node:fs";
18
+ import { join } from "node:path";
19
+ /** STM32 的 GPIO 引脚名:PA0..PK15。F1 只用到 A..E,这里按族上界放到 K。 */
20
+ const PIN_NAME = /^P([A-K])(\d{1,2})$/u;
21
+ /** 每个端口最多 16 根(0..15);再大的一定是写错了。 */
22
+ const MAX_PIN_NUMBER = 15;
23
+ /**
24
+ * 引脚名是否合法(未知/虚拟引脚一律放行)。
25
+ *
26
+ * 为什么不再按型号判「有没有这根脚」:那需要「封装 → 引脚清单」的事实,而资源包只给了 pinCount。
27
+ * 真正的引脚存在性请用 deriveChipPinTable(本机 CubeMX db)——它给的是实测清单,不是符号表。
28
+ */
29
+ export function isKnownPin(pin) {
30
+ const raw = pin.trim().toUpperCase();
31
+ if (raw === "")
30
32
  return true;
31
- const chip = findChip(cpn);
32
- if (chip === null)
33
+ if (raw.startsWith("VP_"))
33
34
  return true;
34
- return chip.pins.includes(pin.toUpperCase());
35
+ // .ioc 里同一根脚会带功能后缀(PA0-WKUP / PC13-TAMPER-RTC),比较时只看引脚名本身。
36
+ const name = (raw.split(/[-/]/u)[0] ?? "").trim();
37
+ const matched = PIN_NAME.exec(name);
38
+ if (matched === null)
39
+ return false;
40
+ return Number.parseInt(matched[2] ?? "", 10) <= MAX_PIN_NUMBER;
41
+ }
42
+ // ── 本机 CubeMX db/mcu 派生 ─────────────────────────────────────────────────
43
+ /** db 里 Pin 的 Name 形如 `PA0-WKUP` / `PC13-TAMPER-RTC` / `PD0-OSC_IN` / `PA13` / `VDD_1`。 */
44
+ function normalizeDbPinName(raw) {
45
+ const head = (raw.split(/[-/]/u)[0] ?? "").trim().toUpperCase();
46
+ return /^P[A-K]\d{1,2}$/u.test(head) ? head : "";
47
+ }
48
+ function pinOrder(pin) {
49
+ const matched = /^P([A-K])(\d{1,2})$/u.exec(pin);
50
+ return [matched?.[1] ?? "", Number(matched?.[2] ?? 0)];
51
+ }
52
+ /**
53
+ * 解析 db/mcu/<Mcu.Name>.xml,取出这个封装上真实存在的 GPIO 引脚(PA0…,已排序去重)。
54
+ *
55
+ * 只认 Position>0:CubeMX 把虚拟引脚也写进 <Pin>,Position=0,拿来当"这个型号有这根脚"会误判。
56
+ * 兼容多行标签(真实 db 里属性经常换行)与自闭合/带子节点的写法。
57
+ */
58
+ export function parseMcuDbXmlPins(xml) {
59
+ const pins = [];
60
+ const seen = new Set();
61
+ for (const tag of xml.match(/<Pin\b[^>]*>/gu) ?? []) {
62
+ const name = /\bName\s*=\s*"([^"]*)"/u.exec(tag)?.[1] ?? "";
63
+ const positionText = /\bPosition\s*=\s*"([^"]*)"/u.exec(tag)?.[1] ?? "";
64
+ const position = Number.parseInt(positionText.trim(), 10);
65
+ if (!Number.isFinite(position) || position <= 0)
66
+ continue;
67
+ const pin = normalizeDbPinName(name);
68
+ if (pin === "" || seen.has(pin))
69
+ continue;
70
+ seen.add(pin);
71
+ pins.push(pin);
72
+ }
73
+ pins.sort((left, right) => {
74
+ const [leftPort, leftNumber] = pinOrder(left);
75
+ const [rightPort, rightNumber] = pinOrder(right);
76
+ if (leftPort !== rightPort)
77
+ return leftPort < rightPort ? -1 : 1;
78
+ return leftNumber - rightNumber;
79
+ });
80
+ return pins;
81
+ }
82
+ /** 本机 CubeMX 的 db/mcu 目录(<CubeMX 安装根>/db/mcu);没有返回 null。 */
83
+ export function findMcuDbDir(cubeMxRoots) {
84
+ for (const root of cubeMxRoots ?? []) {
85
+ if (root.trim() === "")
86
+ continue;
87
+ const dir = join(root, "db", "mcu");
88
+ if (existsSync(dir))
89
+ return dir;
90
+ }
91
+ return null;
92
+ }
93
+ /**
94
+ * 在 db/mcu 下按候选文件名找 XML(CubeMX 用 Mcu.Name,例如 STM32F103C(8-B)Tx.xml;
95
+ * 也可能有人按完整型号存成 STM32F103RCT6.xml),读到就解析,读不到返回 null。
96
+ */
97
+ export function readMcuDbPins(dbMcuDir, names) {
98
+ if (dbMcuDir === null || dbMcuDir === undefined || dbMcuDir.trim() === "")
99
+ return null;
100
+ for (const name of names) {
101
+ const wanted = name.trim();
102
+ if (wanted === "")
103
+ continue;
104
+ const xmlPath = join(dbMcuDir, wanted + ".xml");
105
+ if (!existsSync(xmlPath))
106
+ continue;
107
+ try {
108
+ const pins = parseMcuDbXmlPins(readFileSync(xmlPath, "utf8"));
109
+ if (pins.length > 0)
110
+ return { xmlPath, pins };
111
+ }
112
+ catch {
113
+ // 读不了/不是合法 db:当作没有 db,notes 里会说明没校验。
114
+ }
115
+ }
116
+ return null;
117
+ }
118
+ /**
119
+ * 型号 → 引脚表(只认本机 CubeMX db)。
120
+ *
121
+ * "没校验"这件事必须写进 notes:没有 db 就没有任何引脚存在性事实,此时 pins 是空的、kind=unknown,
122
+ * 报告里要说清「没校验」,而不是让上层以为「这个型号没有引脚」。
123
+ */
124
+ export function deriveChipPinTable(input) {
125
+ const cpn = input.cpn.trim();
126
+ const mcuName = (input.mcuName ?? "").trim();
127
+ const names = [mcuName, cpn].filter((name) => name !== "");
128
+ const dbHit = readMcuDbPins(input.dbMcuDir ?? null, names);
129
+ if (dbHit !== null) {
130
+ return {
131
+ kind: "db",
132
+ cpn,
133
+ mcuName,
134
+ pins: dbHit.pins,
135
+ notes: [
136
+ "引脚表:来自本机 CubeMX db(" + dbHit.xmlPath + "," + String(dbHit.pins.length) + " 个封装引脚)",
137
+ ],
138
+ };
139
+ }
140
+ const why = input.dbMcuDir === null || input.dbMcuDir === undefined
141
+ ? "本机没找到 CubeMX 的 db/mcu"
142
+ : "db/mcu 下没有 " + (names.length === 0 ? "该型号" : names.join(" / ")) + ".xml";
143
+ return {
144
+ kind: "unknown",
145
+ cpn,
146
+ mcuName,
147
+ pins: [],
148
+ notes: [
149
+ "引脚表:没有本机 CubeMX db(" + why + "),引脚存在性不校验(isKnownPin 只查引脚名是否合法);" +
150
+ "插件不内置引脚表,需要逐脚校验请装 CubeMX 或用 stm32_assets 的 chipdb",
151
+ ],
152
+ };
35
153
  }
36
- export const KNOWN_CHIPS = CHIPS;
@@ -0,0 +1,158 @@
1
+ /**
2
+ * STM32F1 时钟树事实表(只放"书上写的数字",不放算法)。
3
+ *
4
+ * 为什么单独一张表:F1 的时钟上限、PLL 可选倍频、外设挂在哪条总线,这些是芯片事实,
5
+ * 而"给定目标频率怎么挑组合"是策略(src/engine/clock-plan.ts)。事实和策略分开,
6
+ * 以后扩 F0/F4 只换这张表,算法不用动。
7
+ *
8
+ * 依据:RM0008 §7(RCC)、DS5319(F103x8/xB)电气特性。F1 全系(value / connectivity)
9
+ * 的 SYSCLK 上限都是 72 MHz;connectivity(105/107)多一级 PREDIV1,本插件暂不规划。
10
+ */
11
+ export const F1_PLL_SOURCES = [
12
+ {
13
+ id: "hse",
14
+ label: "HSE 8 MHz",
15
+ iocValue: "RCC_PLLSOURCE_HSE",
16
+ defaultHz: 8_000_000,
17
+ selectable: true,
18
+ note: "外部晶振(板上 8 MHz,值料号 HSE 范围 4–16 MHz)。精度由晶振决定,通常 ≤50 ppm,UART 波特率靠它就够准。",
19
+ },
20
+ {
21
+ id: "hsi-div2",
22
+ label: "HSI÷2 4 MHz",
23
+ iocValue: "RCC_PLLSOURCE_HSI_DIV2",
24
+ defaultHz: 4_000_000,
25
+ selectable: true,
26
+ note: "内部 RC 8 MHz ÷2。全温区 ±1%,UART 波特率会跟着漂,只在不接晶振时用。",
27
+ },
28
+ {
29
+ id: "hsi",
30
+ label: "HSI 8 MHz",
31
+ iocValue: "RCC_PLLSOURCE_HSI",
32
+ defaultHz: 8_000_000,
33
+ selectable: false,
34
+ note: "F1 值料号的 PLLSRC 只有 HSE / HSI÷2 两档;HSI 直接进 PLL 是互联型(105/107)经 PREDIV1 才有的路,本插件不规划。",
35
+ },
36
+ ];
37
+ export function pllSourceById(id) {
38
+ return F1_PLL_SOURCES.find((source) => source.id === id) ?? null;
39
+ }
40
+ export const F1_PLL_MULS = Array.from({ length: 15 }, (_unused, index) => {
41
+ const mul = index + 2;
42
+ return { mul, iocValue: "RCC_PLL_MUL" + String(mul) };
43
+ });
44
+ export function pllMulValue(mul) {
45
+ return "RCC_PLL_MUL" + String(mul);
46
+ }
47
+ /** 从 RCC.PLLMUL 的值(RCC_PLL_MUL9)反解倍频;认不出来返回 null。 */
48
+ export function pllMulFromValue(value) {
49
+ const matched = /^RCC_PLL_MUL(\d{1,2})$/u.exec(value.trim());
50
+ if (matched === null)
51
+ return null;
52
+ const mul = Number.parseInt(matched[1], 10);
53
+ return Number.isFinite(mul) && mul >= 2 && mul <= 16 ? mul : null;
54
+ }
55
+ /** AHB / APB1 / APB2 分频:÷1、2、4、8、16(RM0008 RCC_CFGR.HPRE/PPRE1/PPRE2)。 */
56
+ export const F1_APB_DIVS = [1, 2, 4, 8, 16].map((div) => ({
57
+ div,
58
+ iocValue: "RCC_HCLK_DIV" + String(div),
59
+ }));
60
+ /** ADC 预分频:÷2、4、6、8(RCC_CFGR.ADCPRE)。 */
61
+ export const F1_ADC_DIVS = [2, 4, 6, 8].map((div) => ({
62
+ div,
63
+ iocValue: "RCC_ADCPCLK2_DIV" + String(div),
64
+ }));
65
+ /** USB 时钟:只能从 PLLCLK ÷1.5 来,所以 PLLCLK 必须是 72 MHz(→48 MHz)。 */
66
+ export const F1_USB_PRESCALER = {
67
+ iocValue: "RCC_USBCLKSOURCE_PLL_DIV1_5",
68
+ hz: 48_000_000,
69
+ requiresPllClkHz: 72_000_000,
70
+ note: "F1 的 USB 只有 PLLCLK÷1.5 一路:PLLCLK=72 MHz 时 48 MHz 可用,其它频率下 USB 跑不起来。",
71
+ };
72
+ export function apbDivValue(div) {
73
+ return "RCC_HCLK_DIV" + String(div);
74
+ }
75
+ export function adcDivValue(div) {
76
+ return "RCC_ADCPCLK2_DIV" + String(div);
77
+ }
78
+ export function apbDivFromValue(value) {
79
+ const matched = /^RCC_HCLK_DIV(\d{1,2})$/u.exec(value.trim());
80
+ if (matched === null)
81
+ return null;
82
+ const div = Number.parseInt(matched[1], 10);
83
+ return [1, 2, 4, 8, 16].includes(div) ? div : null;
84
+ }
85
+ export function adcDivFromValue(value) {
86
+ const matched = /^RCC_ADCPCLK2_DIV(\d{1,2})$/u.exec(value.trim());
87
+ if (matched === null)
88
+ return null;
89
+ const div = Number.parseInt(matched[1], 10);
90
+ return [2, 4, 6, 8].includes(div) ? div : null;
91
+ }
92
+ /** 上限(Hz)。USB 不是"上限"而是"必须等于":必须正好 48 MHz。 */
93
+ export const F1_CLOCK_LIMITS = {
94
+ sysclkHz: 72_000_000,
95
+ apb1Hz: 36_000_000,
96
+ apb2Hz: 72_000_000,
97
+ adcHz: 14_000_000,
98
+ usbHz: 48_000_000,
99
+ };
100
+ /** 上限的人读标签,报告里拼错误消息用。 */
101
+ export const F1_CLOCK_LIMIT_LABELS = {
102
+ sysclkHz: "SYSCLK",
103
+ apb1Hz: "APB1",
104
+ apb2Hz: "APB2",
105
+ adcHz: "ADC",
106
+ usbHz: "USB",
107
+ };
108
+ /**
109
+ * 外设 → 总线(RM0008 的 memory map 与 RCC 使能寄存器分组):
110
+ * APB2 = USART1 / SPI1 / ADC1-3 / TIM1 / TIM8 / GPIO / AFIO;
111
+ * APB1 = USART2-5 / SPI2-3 / I2C1-2 / TIM2-7 / USB / CAN / DAC。
112
+ * 这里只列报告要展示的那批,够覆盖 F1 值料号常见的用法。
113
+ */
114
+ export const F1_PERIPHERAL_CLOCKS = [
115
+ { id: "USART1", label: "USART1", bus: "apb2", kind: "usart" },
116
+ { id: "USART2", label: "USART2", bus: "apb1", kind: "usart" },
117
+ { id: "USART3", label: "USART3", bus: "apb1", kind: "usart" },
118
+ { id: "SPI1", label: "SPI1", bus: "apb2", kind: "spi" },
119
+ { id: "SPI2", label: "SPI2", bus: "apb1", kind: "spi" },
120
+ { id: "I2C1", label: "I2C1", bus: "apb1", kind: "i2c" },
121
+ { id: "I2C2", label: "I2C2", bus: "apb1", kind: "i2c" },
122
+ { id: "ADC1", label: "ADC1/2", bus: "apb2", kind: "adc" },
123
+ { id: "TIM1", label: "TIM1", bus: "apb2", kind: "tim" },
124
+ { id: "TIM2", label: "TIM2", bus: "apb1", kind: "tim" },
125
+ { id: "TIM3", label: "TIM3", bus: "apb1", kind: "tim" },
126
+ { id: "TIM4", label: "TIM4", bus: "apb1", kind: "tim" },
127
+ { id: "USB", label: "USB", bus: "apb1", kind: "usb" },
128
+ { id: "Cortex", label: "Cortex-SysTick", bus: "ahb", kind: "core" },
129
+ ];
130
+ /** UART 波特率整除误差默认算这几档(F1 值料号常用档)。 */
131
+ export const F1_BAUD_LIST = [9600, 19200, 38400, 57600, 115200, 230400];
132
+ /**
133
+ * templates/scaffold/demo.ioc 里 RCC.IPParameters 列出的那 20 个键。
134
+ * 改时钟时必须成套重算——只改 RCC.PLLMUL 会让 CubeMX 下次打开按旧 Freq_Value 生成
135
+ * SystemClock_Config,HAL_RCC_ClockConfig 直接算错(这是本插件最容易埋雷的地方)。
136
+ */
137
+ export const F1_RCC_IP_KEYS = [
138
+ "ADCFreqValue",
139
+ "AHBFreq_Value",
140
+ "APB1CLKDivider",
141
+ "APB1Freq_Value",
142
+ "APB1TimFreq_Value",
143
+ "APB2Freq_Value",
144
+ "APB2TimFreq_Value",
145
+ "FCLKCortexFreq_Value",
146
+ "FamilyName",
147
+ "HCLKFreq_Value",
148
+ "MCOFreq_Value",
149
+ "PLLCLKFreq_Value",
150
+ "PLLMCOFreq_Value",
151
+ "PLLMUL",
152
+ "PLLSourceVirtual",
153
+ "SYSCLKFreq_VALUE",
154
+ "SYSCLKSource",
155
+ "TimSysFreq_Value",
156
+ "USBFreq_Value",
157
+ "VCOOutput2Freq_Value",
158
+ ];