dsh-stm32 0.1.2 → 0.1.4
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.
- package/README.md +92 -40
- package/README_EN.md +85 -36
- package/assets/README.md +85 -0
- package/assets/VERSION +1 -0
- package/assets/device/c0/chips.json +1108 -0
- package/assets/device/f0/chips.json +1570 -0
- package/assets/device/f1/chips.json +1238 -0
- package/assets/device/f1/svd/100.json +943 -0
- package/assets/device/f1/svd/101.json +901 -0
- package/assets/device/f1/svd/102.json +522 -0
- package/assets/device/f1/svd/103.json +1139 -0
- package/assets/device/f1/svd/105.json +1117 -0
- package/assets/device/f1/svd/107.json +1195 -0
- package/assets/device/f2/chips.json +674 -0
- package/assets/device/f3/chips.json +1318 -0
- package/assets/device/f4/chips.json +2942 -0
- package/assets/device/f7/chips.json +1710 -0
- package/assets/device/g0/chips.json +2102 -0
- package/assets/device/g4/chips.json +2494 -0
- package/assets/device/h5/chips.json +898 -0
- package/assets/device/h7/chips.json +1948 -0
- package/assets/device/l0/chips.json +2494 -0
- package/assets/device/l1/chips.json +1234 -0
- package/assets/device/l4/chips.json +2130 -0
- package/assets/device/l4+/chips.json +856 -0
- package/assets/device/l5/chips.json +226 -0
- package/assets/device/u0/chips.json +688 -0
- package/assets/device/u3/chips.json +310 -0
- package/assets/device/u5/chips.json +884 -0
- package/assets/device/wba/chips.json +506 -0
- package/assets/device/wl/chips.json +184 -0
- package/assets/headers/f1/stm32f100xb.h +5972 -0
- package/assets/headers/f1/stm32f100xe.h +6587 -0
- package/assets/headers/f1/stm32f101x6.h +5315 -0
- package/assets/headers/f1/stm32f101xb.h +5446 -0
- package/assets/headers/f1/stm32f101xe.h +6503 -0
- package/assets/headers/f1/stm32f101xg.h +6713 -0
- package/assets/headers/f1/stm32f102x6.h +6448 -0
- package/assets/headers/f1/stm32f102xb.h +6570 -0
- package/assets/headers/f1/stm32f103x6.h +10109 -0
- package/assets/headers/f1/stm32f103xb.h +10240 -0
- package/assets/headers/f1/stm32f103xe.h +11767 -0
- package/assets/headers/f1/stm32f103xg.h +11951 -0
- package/assets/headers/f1/stm32f105xc.h +14340 -0
- package/assets/headers/f1/stm32f107xc.h +15253 -0
- package/assets/headers/f1/stm32f1xx.h +273 -0
- package/assets/headers/f1/system_stm32f1xx.h +96 -0
- package/assets/ioc/family/C0.ioc +82 -0
- package/assets/ioc/family/F0.ioc +71 -0
- package/assets/ioc/family/F2.ioc +91 -0
- package/assets/ioc/family/F3.ioc +94 -0
- package/assets/ioc/family/F4.ioc +91 -0
- package/assets/ioc/family/F7.ioc +102 -0
- package/assets/ioc/family/G0.ioc +90 -0
- package/assets/ioc/family/G4.ioc +110 -0
- package/assets/ioc/family/H5.ioc +116 -0
- package/assets/ioc/family/H7.ioc +133 -0
- package/assets/ioc/family/L0.ioc +92 -0
- package/assets/ioc/family/L1.ioc +87 -0
- package/assets/ioc/family/L4+.ioc +92 -0
- package/assets/ioc/family/L4.ioc +93 -0
- package/assets/ioc/family/L5.ioc +91 -0
- package/assets/ioc/family/U0.ioc +103 -0
- package/assets/ioc/family/U3.ioc +113 -0
- package/assets/ioc/family/U5.ioc +102 -0
- package/assets/ioc/family/WBA.ioc +100 -0
- package/assets/ioc/family/WL.ioc +93 -0
- package/assets/ioc/minimal/STM32F100C8Tx.ioc +113 -0
- package/assets/ioc/minimal/STM32F100RCTx.ioc +113 -0
- package/assets/ioc/minimal/STM32F101C4Tx.ioc +113 -0
- package/assets/ioc/minimal/STM32F101C8Tx.ioc +113 -0
- package/assets/ioc/minimal/STM32F101RCTx.ioc +113 -0
- package/assets/ioc/minimal/STM32F101RFTx.ioc +113 -0
- package/assets/ioc/minimal/STM32F102C4Tx.ioc +113 -0
- package/assets/ioc/minimal/STM32F102C8Tx.ioc +113 -0
- package/assets/ioc/minimal/STM32F103C4Tx.ioc +113 -0
- package/assets/ioc/minimal/STM32F103C8Tx.ioc +113 -0
- package/assets/ioc/minimal/STM32F103RCTx.ioc +113 -0
- package/assets/ioc/minimal/STM32F103RFTx.ioc +113 -0
- package/assets/ioc/minimal/STM32F105RCTx.ioc +113 -0
- package/assets/ioc/minimal/STM32F107RCTx.ioc +113 -0
- package/assets/ld/f1/STM32F100C8Tx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F100RCTx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F101C4Tx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F101C8Tx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F101RCTx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F101RFTx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F102C4Tx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F102C8Tx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F103C4Tx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F103C8Tx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F103RCTx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F103RFTx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F105RCTx_FLASH.ld +249 -0
- package/assets/ld/f1/STM32F107RCTx_FLASH.ld +249 -0
- package/assets/manifest.json +1130 -0
- package/assets/startup/f1/startup_stm32f100xb.s +407 -0
- package/assets/startup/f1/startup_stm32f100xe.s +449 -0
- package/assets/startup/f1/startup_stm32f101x6.s +322 -0
- package/assets/startup/f1/startup_stm32f101xb.s +338 -0
- package/assets/startup/f1/startup_stm32f101xe.s +423 -0
- package/assets/startup/f1/startup_stm32f101xg.s +439 -0
- package/assets/startup/f1/startup_stm32f102x6.s +330 -0
- package/assets/startup/f1/startup_stm32f102xb.s +346 -0
- package/assets/startup/f1/startup_stm32f103x6.s +348 -0
- package/assets/startup/f1/startup_stm32f103xb.s +364 -0
- package/assets/startup/f1/startup_stm32f103xe.s +470 -0
- package/assets/startup/f1/startup_stm32f103xg.s +466 -0
- package/assets/startup/f1/startup_stm32f105xc.s +463 -0
- package/assets/startup/f1/startup_stm32f107xc.s +472 -0
- package/assets/templates/family/C0.ioc +82 -0
- package/assets/templates/family/F0.ioc +71 -0
- package/assets/templates/family/F2.ioc +91 -0
- package/assets/templates/family/F3.ioc +94 -0
- package/assets/templates/family/F4.ioc +91 -0
- package/assets/templates/family/F7.ioc +102 -0
- package/assets/templates/family/G0.ioc +90 -0
- package/assets/templates/family/G4.ioc +110 -0
- package/assets/templates/family/H5.ioc +116 -0
- package/assets/templates/family/H7.ioc +133 -0
- package/assets/templates/family/L0.ioc +92 -0
- package/assets/templates/family/L1.ioc +87 -0
- package/assets/templates/family/L4+.ioc +92 -0
- package/assets/templates/family/L4.ioc +93 -0
- package/assets/templates/family/L5.ioc +91 -0
- package/assets/templates/family/U0.ioc +103 -0
- package/assets/templates/family/U3.ioc +113 -0
- package/assets/templates/family/U5.ioc +102 -0
- package/assets/templates/family/WB.ioc +81 -0
- package/assets/templates/family/WBA.ioc +100 -0
- package/assets/templates/family/WL.ioc +93 -0
- package/docs/reading-guide.md +94 -71
- package/lib/data/chips.js +38 -51
- package/lib/data/clock-db.js +830 -0
- package/lib/data/clock-f1.js +12 -45
- package/lib/data/cmsis-sources.js +264 -17
- package/lib/data/db-presets.js +252 -0
- package/lib/data/device-facts.js +274 -0
- package/lib/data/family.js +515 -0
- package/lib/data/firmware-packages.js +562 -0
- package/lib/data/install-guides.js +2 -2
- package/lib/data/ioc-presets.js +248 -0
- package/lib/data/ioc-schema.js +1058 -0
- package/lib/data/rm-topics/stm32c0.json +227 -0
- package/lib/data/rm-topics.js +103 -0
- package/lib/data/search-roots.js +42 -1
- package/lib/data/stm32f1.js +95 -150
- package/lib/data/svd.js +643 -0
- package/lib/data/toolchain-config.js +0 -14
- package/lib/engine/assets.js +659 -0
- package/lib/engine/breakpoints.js +297 -0
- package/lib/engine/clock-derived.js +101 -0
- package/lib/engine/clock-direct.js +313 -0
- package/lib/engine/clock-plan.js +96 -52
- package/lib/engine/clock-pllmn.js +319 -0
- package/lib/engine/cmake-sources.js +67 -13
- package/lib/engine/cube-mx-guard.js +44 -0
- package/lib/engine/cube-programmer.js +137 -0
- package/lib/engine/cubemx-db.js +273 -0
- package/lib/engine/debug-session.js +576 -22
- package/lib/engine/debug.js +99 -46
- package/lib/engine/doctor.js +162 -19
- package/lib/engine/facts-acquire.js +416 -0
- package/lib/engine/facts.js +134 -0
- package/lib/engine/firmware-install.js +176 -5
- package/lib/engine/firmware-official.js +451 -0
- package/lib/engine/flash.js +317 -76
- package/lib/engine/gdb-mi.js +476 -0
- package/lib/engine/generate.js +9 -2
- package/lib/engine/hal-chip.js +124 -41
- package/lib/engine/ioc-plan.js +1247 -63
- package/lib/engine/ioc-rules.js +698 -0
- package/lib/engine/ioc-verify.js +706 -0
- package/lib/engine/ioc.js +43 -4
- package/lib/engine/msys2-install.js +4 -4
- package/lib/engine/probe-error.js +231 -0
- package/lib/engine/probe-session.js +347 -0
- package/lib/engine/probe.js +18 -3
- package/lib/engine/register-clock.js +41 -0
- package/lib/engine/register-gpio.js +115 -0
- package/lib/engine/register-linker.js +12 -7
- package/lib/engine/register-template.js +130 -45
- package/lib/engine/regs.js +43 -8
- package/lib/engine/rm-extract.js +144 -0
- package/lib/engine/rm-sources.js +360 -0
- package/lib/engine/rm-text.js +56 -0
- package/lib/engine/rtt.js +758 -0
- package/lib/engine/scaffold.js +185 -18
- package/lib/engine/toolchain-gate.js +0 -4
- package/lib/engine/watch.js +227 -0
- package/lib/index.js +12 -2
- package/lib/skill/stm32-workflow.js +2 -2
- package/lib/tools/assets.js +272 -0
- package/lib/tools/cache.js +8 -0
- package/lib/tools/debug-session.js +41 -6
- package/lib/tools/debug.js +41 -11
- package/lib/tools/doctor.js +65 -4
- package/lib/tools/firmware-install.js +31 -6
- package/lib/tools/flash.js +47 -10
- package/lib/tools/generate.js +25 -0
- package/lib/tools/ioc-apply.js +2 -0
- package/lib/tools/ioc-inspect.js +2 -0
- package/lib/tools/ioc-plan.js +59 -2
- package/lib/tools/ioc-verify.js +237 -0
- package/lib/tools/project-create.js +63 -3
- package/lib/tools/regs.js +453 -61
- package/lib/tools/route-plan.js +3 -0
- package/lib/tools/rtt.js +470 -0
- package/lib/tools/watch.js +256 -0
- package/package.json +5 -4
- package/templates/openocd/stm32c0x.cfg +83 -0
- package/templates/openocd/stm32u0x.cfg +64 -0
- package/templates/register/CMakeLists.txt +8 -2
- package/templates/register/Core/Inc/rtt.h +138 -0
- package/templates/register/Core/Src/main.c +42 -25
- package/templates/register/Core/Src/rtt.c +373 -0
- package/templates/scaffold/RTT.md +90 -0
- package/templates/scaffold/STM32F103XX_FLASH.ld +3 -0
- package/templates/scaffold/cmake/user/CMakeLists.txt +7 -0
- package/templates/scaffold/openocd.cfg +5 -3
- package/templates/scaffold/vscode/launch.json +8 -4
- package/docs/development-notes.md +0 -2116
- package/docs/dsh-stm32-plugin-/350/247/204/346/240/274.md +0 -673
- package/docs/logic-audit.md +0 -607
- package/lib/data/f1-ram.generated.js +0 -34
package/lib/engine/hal-chip.js
CHANGED
|
@@ -20,6 +20,8 @@
|
|
|
20
20
|
* 本文件只做纯计算与纯渲染(不读盘、不依赖 CubeMX 是否装了),这样能单测。
|
|
21
21
|
*/
|
|
22
22
|
import { resolveF1Chip } from "../data/stm32f1.js";
|
|
23
|
+
import { findChipFact } from "../data/device-facts.js";
|
|
24
|
+
import { familyIdOfPart, familyProfileOf } from "../data/family.js";
|
|
23
25
|
/** HAL 路线不给型号时按蓝丸(STM32F103C8T6)建,与历史行为一致。 */
|
|
24
26
|
export const DEFAULT_HAL_MCU = "STM32F103C8T6";
|
|
25
27
|
/**
|
|
@@ -30,31 +32,6 @@ export const LEGACY_LINKER_SCRIPT = "STM32F103XX_FLASH.ld";
|
|
|
30
32
|
/** 模板里写死的 C8T6 事实(渲染时被替换掉;C8T6 本身替换后逐字节不变)。 */
|
|
31
33
|
const TEMPLATE_DEVICE_DEFINE = "STM32F103xB";
|
|
32
34
|
const TEMPLATE_STARTUP = "startup_stm32f103xb.s";
|
|
33
|
-
/** 封装字母 → 引脚数(与 CubeMX db/mcu 的 LQFP48/64/100/144 对应)。 */
|
|
34
|
-
const PIN_COUNT_BY_PACKAGE = { T: 36, C: 48, R: 64, V: 100, Z: 144 };
|
|
35
|
-
/**
|
|
36
|
-
* 型号 → CubeMX db/mcu 分组名用的「容量档分组」表。
|
|
37
|
-
* 键:line(三位数字)→ 封装字母 → 该封装在 db 里真实出现过的分组(升序,靠前的先命中)。
|
|
38
|
-
* 只收 Tx/Ux/Yx 这种带封装后缀的条目;特殊单型号(STM32F103C6Ux、STM32F107VCHx 之类)
|
|
39
|
-
* 走「退回具体型号名」的兜底,不在这里硬编。
|
|
40
|
-
*/
|
|
41
|
-
const MCU_NAME_GROUPS = {
|
|
42
|
-
"100": { C: ["4-6", "8-B"], R: ["4-6", "8-B", "C-D-E"], V: ["8-B", "C-D-E"], Z: ["C-D-E"] },
|
|
43
|
-
"101": { C: ["4-6", "8-B"], R: ["4-6", "8-B", "C-D-E", "F-G"], T: ["4-6", "8-B"], V: ["8-B", "C-D-E", "F-G"], Z: ["C-D-E", "F-G"] },
|
|
44
|
-
"102": { C: ["4-6", "8-B"], R: ["4-6", "8-B"] },
|
|
45
|
-
"103": { C: ["4-6", "8-B"], R: ["4-6", "8-B", "C-D-E", "F-G"], T: ["4-6", "8-B"], V: ["8-B", "C-D-E", "F-G"], Z: ["C-D-E", "F-G"] },
|
|
46
|
-
"105": { R: ["8-B-C"], V: ["8-B-C"] },
|
|
47
|
-
"107": { R: ["B-C"], V: ["B-C"] },
|
|
48
|
-
};
|
|
49
|
-
/** 分组标签 → 它覆盖的容量字母。 */
|
|
50
|
-
const GROUP_LETTERS = {
|
|
51
|
-
"4-6": ["4", "6"],
|
|
52
|
-
"8-B": ["8", "B"],
|
|
53
|
-
"C-D-E": ["C", "D", "E"],
|
|
54
|
-
"F-G": ["F", "G"],
|
|
55
|
-
"B-C": ["B", "C"],
|
|
56
|
-
"8-B-C": ["8", "B", "C"],
|
|
57
|
-
};
|
|
58
35
|
/** 型号拆解:STM32F103RCT6 → line 103 / 封装 R / 容量 C / 后缀 T / 温度 6。 */
|
|
59
36
|
const PART_PATTERN = /^STM32F(\d{3})([A-Z])([0-9A-G])([A-Z])?([0-9])?$/u;
|
|
60
37
|
/**
|
|
@@ -68,6 +45,16 @@ const PART_PATTERN = /^STM32F(\d{3})([A-Z])([0-9A-G])([A-Z])?([0-9])?$/u;
|
|
|
68
45
|
export function resolveHalChip(input) {
|
|
69
46
|
const raw = (input ?? "").trim();
|
|
70
47
|
const mcu = raw.length === 0 ? DEFAULT_HAL_MCU : raw.toUpperCase();
|
|
48
|
+
const familyId = familyIdOfPart(mcu);
|
|
49
|
+
if (familyId === "") {
|
|
50
|
+
return {
|
|
51
|
+
facts: null,
|
|
52
|
+
reason: "认不出 " + mcu + " 属于哪个 STM32 族:型号要以 STM32 开头并带完整封装后缀,例如 STM32F103C8T6 / STM32G431CBT6 / STM32L071CBT6",
|
|
53
|
+
};
|
|
54
|
+
}
|
|
55
|
+
// F1 走原来那条实测过千万次的路径(手写 RAM 表 + db 分组名),其它族走内置资源的芯片表。
|
|
56
|
+
if (familyId !== "STM32F1")
|
|
57
|
+
return resolveFamilyHalChip(mcu, familyId);
|
|
71
58
|
const resolved = resolveF1Chip(mcu);
|
|
72
59
|
if (resolved.chip === null) {
|
|
73
60
|
return {
|
|
@@ -106,22 +93,14 @@ export function resolveHalChip(input) {
|
|
|
106
93
|
};
|
|
107
94
|
}
|
|
108
95
|
const notes = [];
|
|
109
|
-
|
|
96
|
+
// 封装脚数与 db 分组名都从内置资源的 chips.json 来(DeviceFactsChip.pinCount / mcuName):
|
|
97
|
+
// 插件不再自己维护「封装字母 → 脚数」「line → 分组名」两张表 —— 那只是 db 的 Package/RefName 的手抄快照,
|
|
98
|
+
// 换族、换 db 版本就失真(§65 已经为预设表栽过一次)。
|
|
99
|
+
const pinCount = chip.pinCount;
|
|
110
100
|
const deviceId = chip.prefix + packageLetter + chip.densityLetter + suffixLetter + "x";
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
const grouped = suffixLetter === "T" || (suffixLetter === "U" && packageLetter === "T") || (suffixLetter === "Y" && packageLetter === "R");
|
|
115
|
-
let mcuName = deviceId;
|
|
116
|
-
if (grouped) {
|
|
117
|
-
const groups = MCU_NAME_GROUPS[code]?.[packageLetter] ?? [];
|
|
118
|
-
const hit = groups.find((entry) => (GROUP_LETTERS[entry] ?? []).includes(chip.densityLetter));
|
|
119
|
-
if (hit === undefined) {
|
|
120
|
-
notes.push("CubeMX 的 db/mcu 里没有 " + deviceId + " 这一分组名,Mcu.Name 按具体型号名写(CubeMX 打不开 .ioc 的话把型号换成同容量档的常见型号)");
|
|
121
|
-
}
|
|
122
|
-
else {
|
|
123
|
-
mcuName = chip.prefix + packageLetter + "(" + hit + ")" + suffixLetter + "x";
|
|
124
|
-
}
|
|
101
|
+
const mcuName = chip.mcuName !== "" ? chip.mcuName : deviceId;
|
|
102
|
+
if (chip.mcuName === "") {
|
|
103
|
+
notes.push("内置资源里没有 " + deviceId + " 的 db 分组名(Mcu.Name),按具体型号名写(CubeMX 打不开 .ioc 的话把型号换成同容量档的常见型号)");
|
|
125
104
|
}
|
|
126
105
|
const packageKind = suffixLetter === "U" ? "VFQFPN" : suffixLetter === "Y" ? "WLCSP" : "LQFP";
|
|
127
106
|
const packageName = pinCount === null ? packageKind : packageKind + String(pinCount);
|
|
@@ -138,6 +117,8 @@ export function resolveHalChip(input) {
|
|
|
138
117
|
flashBytes,
|
|
139
118
|
ramBytes,
|
|
140
119
|
linkerScript: deviceId + "_FLASH.ld",
|
|
120
|
+
familyId: "STM32F1",
|
|
121
|
+
familyLine: "F1",
|
|
141
122
|
// 旧名只有蓝丸(C8T6 的 64K Flash / 20K RAM)对得上;别的芯片写旧名 = 一份骗人的内存布局。
|
|
142
123
|
keepLegacyLinkerScript: deviceId === "STM32F103C8Tx" && flashBytes === 64 * 1024 && ramBytes === 20 * 1024,
|
|
143
124
|
notes,
|
|
@@ -145,6 +126,56 @@ export function resolveHalChip(input) {
|
|
|
145
126
|
reason: "",
|
|
146
127
|
};
|
|
147
128
|
}
|
|
129
|
+
/**
|
|
130
|
+
* 非 F1 族:事实全部来自内置资源的 device/<族>/chips.json(每个字段都是生成器在固件包里
|
|
131
|
+
* existsSync 验过的文件名),插件不再内置任何分组表。
|
|
132
|
+
*
|
|
133
|
+
* 为什么不在插件里推名字:F4 的 F410/F412 启动文件按**封装**分档(startup_stm32f410cx.s),
|
|
134
|
+
* L4+ 的 line 是 4P5 —— 这些规则只要有一族特殊,猜就是错的;让生成器把实测结果写进表里最省事。
|
|
135
|
+
*/
|
|
136
|
+
function resolveFamilyHalChip(mcu, familyId) {
|
|
137
|
+
const profile = familyProfileOf(familyId);
|
|
138
|
+
const fact = findChipFact(mcu);
|
|
139
|
+
if (fact === null) {
|
|
140
|
+
return {
|
|
141
|
+
facts: null,
|
|
142
|
+
reason: profile.id + " 的芯片表里没有 " + mcu + ":内置资源要含 device/" + profile.line.toLowerCase() +
|
|
143
|
+
"/chips.json(先跑 stm32_assets verify 确认插件安装完整)。芯片表随插件内置,由 scripts/assets/ 的资源脚本按族从 CubeMX db 与固件包生成",
|
|
144
|
+
};
|
|
145
|
+
}
|
|
146
|
+
const notes = [];
|
|
147
|
+
if (fact.flashBytes <= 0 || fact.ramBytes <= 0) {
|
|
148
|
+
return {
|
|
149
|
+
facts: null,
|
|
150
|
+
reason: mcu + " 的 Flash/RAM 在芯片表里是 0(db 里缺 <Flash>/<Ram>):链接脚本的内存长度不能猜,先在资源脚本 scripts/assets/补这一档",
|
|
151
|
+
};
|
|
152
|
+
}
|
|
153
|
+
let mcuName = fact.mcuName;
|
|
154
|
+
if (mcuName === "") {
|
|
155
|
+
mcuName = fact.deviceId;
|
|
156
|
+
notes.push("芯片表里没有 db 分组名(Mcu.Name),按具体型号名写 " + fact.deviceId + "(CubeMX 打不开就换同档常见型号)");
|
|
157
|
+
}
|
|
158
|
+
return {
|
|
159
|
+
facts: {
|
|
160
|
+
mcu,
|
|
161
|
+
deviceId: fact.deviceId,
|
|
162
|
+
mcuName,
|
|
163
|
+
packageName: fact.packageName,
|
|
164
|
+
pinCount: fact.pinCount,
|
|
165
|
+
startup: fact.startup,
|
|
166
|
+
deviceDefine: fact.deviceDefine,
|
|
167
|
+
deviceHeader: fact.deviceHeader,
|
|
168
|
+
flashBytes: fact.flashBytes,
|
|
169
|
+
ramBytes: fact.ramBytes,
|
|
170
|
+
linkerScript: fact.linkerScript === "" ? fact.deviceId + "_FLASH.ld" : fact.linkerScript,
|
|
171
|
+
familyId: profile.id,
|
|
172
|
+
familyLine: profile.line,
|
|
173
|
+
keepLegacyLinkerScript: false,
|
|
174
|
+
notes,
|
|
175
|
+
},
|
|
176
|
+
reason: "",
|
|
177
|
+
};
|
|
178
|
+
}
|
|
148
179
|
/** 一句话说清这款芯片会变成什么(报告/warning 里用)。 */
|
|
149
180
|
export function describeHalChip(facts) {
|
|
150
181
|
return (facts.mcu + "(" + facts.deviceId + "," + facts.packageName + "):启动文件 " + facts.startup +
|
|
@@ -189,13 +220,17 @@ export function renderLinkerScript(template, facts) {
|
|
|
189
220
|
* .ioc 按芯片渲染:只改这五行,引脚/时钟树沿用模板的最小集(PA13/PA14 SWD + 一个 GPIO)。
|
|
190
221
|
* 缺键就抛错——没把握的 .ioc 宁可不写,写一份 CubeMX 认不出的配置更糟。
|
|
191
222
|
*/
|
|
192
|
-
export function renderIoc(template, facts) {
|
|
223
|
+
export function renderIoc(template, facts, projectName = "") {
|
|
193
224
|
const values = [
|
|
194
225
|
["Mcu.CPN", facts.mcu],
|
|
195
226
|
["Mcu.Name", facts.mcuName],
|
|
196
227
|
["Mcu.Package", facts.packageName],
|
|
197
228
|
["Mcu.UserName", facts.deviceId],
|
|
198
229
|
["ProjectManager.DeviceId", facts.deviceId],
|
|
230
|
+
// 工程文件名也要跟着工程走:模板里写的是 demo.ioc,CubeMX 保存时发现"文件名与键不一致"
|
|
231
|
+
// 就会把它改回真实文件名 —— 那是每次 plan→verify 都会出现的假 diff(F4 实测过)。
|
|
232
|
+
// 这条不是必需键(老模板可能没有),所以单独放 optional,不参与缺键检查。
|
|
233
|
+
...(projectName === "" ? [] : [["ProjectManager.ProjectFileName", projectName + ".ioc"]]),
|
|
199
234
|
];
|
|
200
235
|
const eol = template.includes("\r\n") ? "\r\n" : "\n";
|
|
201
236
|
const seen = new Set();
|
|
@@ -221,6 +256,54 @@ export function pointLinkerFlagAt(text, facts) {
|
|
|
221
256
|
}
|
|
222
257
|
return text.split(LEGACY_LINKER_SCRIPT).join(facts.linkerScript);
|
|
223
258
|
}
|
|
259
|
+
/**
|
|
260
|
+
* cmake/stm32cubemx/CMakeLists.txt 按族 + 芯片替换。
|
|
261
|
+
*
|
|
262
|
+
* 这份文件里有三类族相关的字面量(都是 ST 的 CubeMX 用 F1 生成的骨架带来的):
|
|
263
|
+
* - 目录名:Drivers/STM32F1xx_HAL_Driver、CMSIS/Device/ST/STM32F1xx、Core/Inc/stm32f1xx_hal_conf.h
|
|
264
|
+
* - 设备宏:STM32F103xB(只对 C8T6 成立,别的芯片编不过)
|
|
265
|
+
* - 启动文件:startup_stm32f103xb.s
|
|
266
|
+
* 少了第一步,非 F1 工程会去 include 一个不存在的 STM32F1xx 目录(cmake 不报错、编译期才发现)。
|
|
267
|
+
* 驱动源清单(STM32_Drivers_Src)故意不在这里改:它是"这个工程真用到哪些模块"的产物,
|
|
268
|
+
* 由 refreshCubemxCmakeLists 在 CubeMX 生成之后按 hal_conf.h 重算。
|
|
269
|
+
*/
|
|
270
|
+
export function renderCmakeLists(text, facts) {
|
|
271
|
+
const upper = "STM32" + facts.familyLine.replace("+", "") + "xx";
|
|
272
|
+
const lower = "stm32" + facts.familyLine.replace("+", "").toLowerCase() + "xx";
|
|
273
|
+
let out = text;
|
|
274
|
+
// 先换最具体的(设备宏/启动文件),否则 STM32F103xB 会被 "STM32F1xx" 的替换漏掉。
|
|
275
|
+
out = renderStartupAndDefine(out, facts);
|
|
276
|
+
out = out.split("STM32F1xx").join(upper);
|
|
277
|
+
out = out.split("stm32f1xx").join(lower);
|
|
278
|
+
return out;
|
|
279
|
+
}
|
|
280
|
+
/**
|
|
281
|
+
* openocd.cfg / .vscode/launch.json 里的 target 脚本按族替换(模板里写的是 stm32f1x)。
|
|
282
|
+
*
|
|
283
|
+
* 三种情况:
|
|
284
|
+
* - 该族有官方脚本 → `target/stm32c0x.cfg`… 这种相对 openocd scripts 目录的路径;
|
|
285
|
+
* - 该族只有插件内置脚本(C0 / U0)→ 工程内的 `openocd/<name>.cfg`(scaffold 会把文件复制进去),
|
|
286
|
+
* launch.json 里要用 `\${workspaceFolder}/` 前缀,所以两个文件分开处理(variant);
|
|
287
|
+
* - 认不出的族 → 原文返回并给 note:宁可让用户看到"还是 F1 的 target",也不猜一个别的族的脚本
|
|
288
|
+
* ——连错了不是连不上,是能连上但 flash 布局读错。
|
|
289
|
+
*/
|
|
290
|
+
export function renderOpenocdTarget(text, facts, variant = "openocd") {
|
|
291
|
+
const profile = familyProfileOf(facts.familyId);
|
|
292
|
+
if (profile.bundledTarget !== null) {
|
|
293
|
+
const rel = "openocd/" + profile.bundledTarget + ".cfg";
|
|
294
|
+
const replacement = variant === "launch" ? "\${workspaceFolder}/" + rel : rel;
|
|
295
|
+
return { text: text.split("target/stm32f1x.cfg").join(replacement), note: "" };
|
|
296
|
+
}
|
|
297
|
+
const target = profile.openocdTarget;
|
|
298
|
+
if (target === null || target === "") {
|
|
299
|
+
return {
|
|
300
|
+
text,
|
|
301
|
+
note: facts.familyId + " 没有 openocd target 脚本(见 stm32_family 报告的 note):工程里的 openocd.cfg 仍指向 " +
|
|
302
|
+
"target/stm32f1x.cfg,烧录/调试前请自己改成该族的脚本,或把 transport 改成 hla_swd 走 ST-Link",
|
|
303
|
+
};
|
|
304
|
+
}
|
|
305
|
+
return { text: text.split("target/stm32f1x.cfg").join("target/" + target + ".cfg"), note: "" };
|
|
306
|
+
}
|
|
224
307
|
/** cmake/stm32cubemx/CMakeLists.txt 里的设备宏与启动文件名按芯片替换。 */
|
|
225
308
|
export function renderStartupAndDefine(text, facts) {
|
|
226
309
|
if (!text.includes(TEMPLATE_DEVICE_DEFINE) || !text.includes(TEMPLATE_STARTUP)) {
|