dsh-stm32 0.1.0 → 0.1.2
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 +127 -29
- package/README_EN.md +125 -29
- package/client/client.js +682 -0
- package/docs/development-notes.md +1385 -5
- package/docs/logic-audit.md +607 -0
- package/docs/reading-guide.md +738 -0
- package/lib/client.js +682 -0
- package/lib/commands/register.js +214 -12
- package/lib/data/chips.js +134 -4
- package/lib/data/clock-f1.js +158 -0
- package/lib/data/cmsis-sources.js +316 -0
- package/lib/data/f1-ram.generated.js +34 -0
- package/lib/data/firmware-packages.js +352 -0
- package/lib/data/install-guides.js +190 -0
- package/lib/data/search-roots.js +135 -15
- package/lib/data/stm32f1.js +186 -0
- package/lib/data/toolchain-config.js +310 -0
- package/lib/engine/build.js +121 -16
- package/lib/engine/cache.js +336 -0
- package/lib/engine/clock-plan.js +608 -0
- package/lib/engine/cmake-sources.js +428 -0
- package/lib/engine/code-patch.js +18 -6
- package/lib/engine/debug-session.js +163 -4
- package/lib/engine/debug.js +84 -19
- package/lib/engine/doctor.js +395 -4
- package/lib/engine/fetch.js +287 -0
- package/lib/engine/firmware-install.js +668 -0
- package/lib/engine/flash.js +145 -15
- package/lib/engine/fs-longpath.js +107 -0
- package/lib/engine/generate-cache.js +118 -0
- package/lib/engine/generate-script.js +30 -8
- package/lib/engine/generate.js +296 -14
- package/lib/engine/hal-chip.js +230 -0
- package/lib/engine/ioc-plan.js +47 -8
- package/lib/engine/msys2-install.js +1870 -0
- package/lib/engine/probe.js +57 -6
- package/lib/engine/project-export.js +129 -0
- package/lib/engine/register-clock.js +132 -0
- package/lib/engine/register-linker.js +129 -0
- package/lib/engine/register-template.js +449 -0
- package/lib/engine/regs.js +18 -4
- package/lib/engine/route-plan.js +553 -0
- package/lib/engine/scaffold.js +303 -72
- package/lib/engine/subprocess-runner.js +2 -0
- package/lib/engine/tar.js +250 -0
- package/lib/engine/text-file.js +150 -0
- package/lib/engine/thirdparty.js +243 -0
- package/lib/engine/tool-env.js +51 -0
- package/lib/engine/toolchain-gate.js +386 -0
- package/lib/engine/vscode-config.js +99 -0
- package/lib/engine/web-api.js +375 -0
- package/lib/engine/web-routes.js +100 -0
- package/lib/engine/xcube-catalog.js +102 -0
- package/lib/engine/xcube.js +254 -0
- package/lib/engine/zip.js +142 -0
- package/lib/index.js +44 -2
- package/lib/skill/stm32-workflow.js +3 -3
- package/lib/tools/build.js +55 -3
- package/lib/tools/cache.js +250 -0
- package/lib/tools/code-patch.js +29 -2
- package/lib/tools/debug-session.js +56 -14
- package/lib/tools/debug.js +43 -2
- package/lib/tools/doctor.js +16 -3
- package/lib/tools/env-install.js +472 -0
- package/lib/tools/env-probe.js +6 -2
- package/lib/tools/firmware-install.js +255 -0
- package/lib/tools/flash.js +41 -2
- package/lib/tools/generate.js +96 -10
- package/lib/tools/ioc-apply.js +27 -11
- package/lib/tools/ioc-inspect.js +4 -2
- package/lib/tools/ioc-plan.js +209 -11
- package/lib/tools/project-create.js +229 -21
- package/lib/tools/project-dir.js +95 -0
- package/lib/tools/project-export.js +100 -0
- package/lib/tools/regs.js +82 -7
- package/lib/tools/route-plan.js +467 -0
- package/package.json +11 -4
- package/templates/register/CMakeLists.txt +52 -0
- package/templates/register/Core/Src/main.c +72 -0
- package/templates/scaffold/openocd.cfg +8 -0
- package/templates/scaffold/vscode/launch.json +8 -6
- package/templates/scaffold/vscode/settings.json +5 -11
package/lib/data/search-roots.js
CHANGED
|
@@ -1,25 +1,33 @@
|
|
|
1
1
|
/**
|
|
2
2
|
* 工具链搜索配置。
|
|
3
3
|
*
|
|
4
|
-
*
|
|
4
|
+
* 设计约定:路径是数据,不是逻辑。候选按优先级来自四处:
|
|
5
5
|
* 1. 工具参数(binDirs / cubeMxRoots)—— 调用方显式指定,最高优先;
|
|
6
|
-
* 2. 环境变量(STM32_BIN_DIRS / STM32_CUBEMX_ROOT)——
|
|
7
|
-
* 3.
|
|
6
|
+
* 2. 环境变量(STM32_BIN_DIRS / STM32_CUBEMX_ROOT)—— **整份替换**下面的值,不合并;
|
|
7
|
+
* 3. 用户配置文件(toolchain-config:stm32_env_install 装好后自己写的,见下)——
|
|
8
|
+
* 也整份替换默认值,但排在环境变量之后(环境变量是临时/脚本场景的活开关);
|
|
9
|
+
* 4. 默认候选表(DEFAULT_BIN_DIRS / DEFAULT_CUBEMX_ROOTS,本机常见安装位置)。
|
|
8
10
|
* 之后再把**自动发现到的**安装目录追加到尾部:只做兜底,不覆盖上面任何一处,
|
|
9
11
|
* 这样别人把 MSYS2 装在 E:\\msys64、CubeMX 装在 F:\\tools 也能直接跑。
|
|
10
|
-
* 设 STM32_NO_DISCOVER=1 可关掉自动发现(CI /
|
|
12
|
+
* 设 STM32_NO_DISCOVER=1 可关掉自动发现(CI / 单测里避免扫盘);
|
|
13
|
+
* 设 DSH_STM32_NO_CONFIG=1 可让第 3 档失效(单测里保证不读本机配置)。
|
|
11
14
|
*/
|
|
12
15
|
import { execFileSync } from "node:child_process";
|
|
13
16
|
import { existsSync, readdirSync } from "node:fs";
|
|
14
|
-
|
|
17
|
+
import { binDirsFromConfig, configReadingDisabled, cubeMxRootsFromConfig, readToolchainConfig } from "./toolchain-config.js";
|
|
18
|
+
/**
|
|
19
|
+
* 默认二进制目录:只放**任何 Windows 机器上都可能存在**的位置。
|
|
20
|
+
*
|
|
21
|
+
* 这里绝不能出现开发机专属路径(D:/app/msys64 之类):插件是给别人下载的,
|
|
22
|
+
* 那些路径在别人机器上必然搜不到,还会把「查过哪些地方」的文案污染成别人看不懂的样子。
|
|
23
|
+
* 装在别处的情况由自动发现兜底(扫盘符 msys64/app/msys64/tools 等常见布局)。
|
|
24
|
+
*/
|
|
15
25
|
export const DEFAULT_BIN_DIRS = [
|
|
16
|
-
"D:/app/msys64/ucrt64/bin",
|
|
17
26
|
"C:/msys64/ucrt64/bin",
|
|
18
27
|
"C:/msys64/mingw64/bin",
|
|
19
28
|
];
|
|
20
|
-
/** 默认 CubeMX 安装根目录候选(6.x
|
|
29
|
+
/** 默认 CubeMX 安装根目录候选(6.x 的 Windows 默认安装位置)。 */
|
|
21
30
|
export const DEFAULT_CUBEMX_ROOTS = [
|
|
22
|
-
"D:/app/STM32CubeMX",
|
|
23
31
|
"C:/Program Files/STMicroelectronics/STM32Cube/STM32CubeMX",
|
|
24
32
|
];
|
|
25
33
|
/**
|
|
@@ -121,6 +129,61 @@ export function discoverCubeMxRoots(probe) {
|
|
|
121
129
|
}
|
|
122
130
|
return dedupePaths(found);
|
|
123
131
|
}
|
|
132
|
+
/** 解码失败的痕迹:非法字节被换成 U+FFFD。 */
|
|
133
|
+
const REPLACEMENT_CHAR = "\u{FFFD}";
|
|
134
|
+
/**
|
|
135
|
+
* 把 reg.exe 的输出(原始字节,或已经被宿主解码过的字符串)变成可用文本。
|
|
136
|
+
*
|
|
137
|
+
* 为什么必须有这一步:reg.exe 是控制台程序,输出到管道/文件时用的是系统 ANSI 代码页
|
|
138
|
+
* (中文 Windows 是 936/GBK),而宿主按 UTF-8 解码子进程 stdout。中文用户名下的安装路径
|
|
139
|
+
* 于是变成一串 U+FFFD:existsSync 必然失败(CubeMX 发现退化成目录扫描),更糟的是这串乱码
|
|
140
|
+
* 会被当成"用户原来的 PATH 旧值"原样写回注册表,把用户原有的中文条目永久写坏。
|
|
141
|
+
*
|
|
142
|
+
* 为什么按顺序探测而不是先读代码页:零依赖下拿不到 GetConsoleOutputCP / GetACP,而
|
|
143
|
+
* "UTF-8 严格解码失败才回落 GB18030"对纯 ASCII 输出永远成立(两种编码对 ASCII 等价),
|
|
144
|
+
* 只有真的有非 ASCII 字节时才需要判断,判断依据也就只有"解不解得出来"。
|
|
145
|
+
* 两种都解不出来就返回 ok:false —— 宁可让用户手写一条,也不把乱码写进注册表。
|
|
146
|
+
*
|
|
147
|
+
* 备选方案(没采用):用 powershell 先把 [Console]::OutputEncoding 设成 UTF8 再调 reg.exe。
|
|
148
|
+
* 不用的原因:多一层 PowerShell 启动开销与引号转义,而且字节其实已经拿到了,直接探测更短。
|
|
149
|
+
*/
|
|
150
|
+
export function decodeRegistryText(value, label = "reg.exe 输出") {
|
|
151
|
+
if (value === null || value === undefined) {
|
|
152
|
+
return { ok: false, text: "", encoding: "", error: label + "是空的(什么都没读到)" };
|
|
153
|
+
}
|
|
154
|
+
if (typeof value === "string") {
|
|
155
|
+
// 宿主已经用 UTF-8 解过一遍:真乱码在这里就已经变成 U+FFFD 了,原始字节救不回来。
|
|
156
|
+
if (value.includes(REPLACEMENT_CHAR)) {
|
|
157
|
+
return {
|
|
158
|
+
ok: false,
|
|
159
|
+
text: "",
|
|
160
|
+
encoding: "",
|
|
161
|
+
error: label + "里有无法解码的字节(已被替换成乱码字符),系统代码页可能不是 UTF-8",
|
|
162
|
+
};
|
|
163
|
+
}
|
|
164
|
+
return { ok: true, text: value, encoding: "utf-8", error: "" };
|
|
165
|
+
}
|
|
166
|
+
if (value.length === 0) {
|
|
167
|
+
return { ok: false, text: "", encoding: "", error: label + "是空的(什么都没读到)" };
|
|
168
|
+
}
|
|
169
|
+
for (const encoding of ["utf-8", "gb18030"]) {
|
|
170
|
+
try {
|
|
171
|
+
const text = new TextDecoder(encoding, { fatal: true }).decode(value);
|
|
172
|
+
if (text.includes(REPLACEMENT_CHAR))
|
|
173
|
+
continue;
|
|
174
|
+
return { ok: true, text, encoding, error: "" };
|
|
175
|
+
}
|
|
176
|
+
catch {
|
|
177
|
+
// 这个编码解不出来,试下一个
|
|
178
|
+
}
|
|
179
|
+
}
|
|
180
|
+
return {
|
|
181
|
+
ok: false,
|
|
182
|
+
text: "",
|
|
183
|
+
encoding: "",
|
|
184
|
+
error: label + "既不是合法 UTF-8 也不是合法 GB18030(系统代码页可能不是中文/英文)",
|
|
185
|
+
};
|
|
186
|
+
}
|
|
124
187
|
/** 读注册表里 ST 记下的安装位置;没有这些键是最常见的情况,不算错误。 */
|
|
125
188
|
function readRegistryInstallDirs() {
|
|
126
189
|
if (process.platform !== "win32")
|
|
@@ -134,14 +197,20 @@ function readRegistryInstallDirs() {
|
|
|
134
197
|
const out = [];
|
|
135
198
|
for (const entry of keys) {
|
|
136
199
|
try {
|
|
137
|
-
|
|
138
|
-
|
|
200
|
+
// 按 buffer 收:reg.exe 写的是系统代码页的字节(中文系统是 GBK),交给宿主按 UTF-8
|
|
201
|
+
// 解会把中文安装路径变成乱码,existsSync 随后必然失败。
|
|
202
|
+
const raw = execFileSync("reg.exe", ["query", entry.key, "/v", entry.value], {
|
|
203
|
+
encoding: "buffer",
|
|
139
204
|
timeout: 4000,
|
|
140
205
|
windowsHide: true,
|
|
141
206
|
// 键不存在时 reg 会往 stderr 写字;默认继承会让这堆噪音漏到调用方终端里。
|
|
142
207
|
stdio: ["ignore", "pipe", "pipe"],
|
|
143
208
|
});
|
|
144
|
-
|
|
209
|
+
const decoded = decodeRegistryText(raw, "reg query " + entry.key + " /v " + entry.value);
|
|
210
|
+
// 解不出来就当这条没读到:一串乱码路径交给 existsSync 只是污染"查过哪些地方"的说明。
|
|
211
|
+
if (!decoded.ok)
|
|
212
|
+
continue;
|
|
213
|
+
for (const line of decoded.text.split(/\r?\n/u)) {
|
|
145
214
|
const trimmed = line.trim();
|
|
146
215
|
if (!trimmed.startsWith(entry.value))
|
|
147
216
|
continue;
|
|
@@ -217,22 +286,73 @@ export function describeSearchScope(paths, tail) {
|
|
|
217
286
|
return tail === undefined ? list : list + ",以及 " + tail;
|
|
218
287
|
}
|
|
219
288
|
/**
|
|
220
|
-
*
|
|
289
|
+
* 只读检查:配置/环境变量里点名的目录在这台机器上到底有没有。
|
|
290
|
+
*
|
|
291
|
+
* 为什么需要这一层:插件是给别人下载的,配置也可能从别的机器拷过来(D:/app/msys64 这种
|
|
292
|
+
* 开发机专属路径)。这种路径不会让程序崩,但会让用户以为"我明明配了却没生效"。
|
|
293
|
+
* 这里**只报告、不删条目**:路径可能是还没装(装完就存在),删掉反而抹掉用户意图。
|
|
294
|
+
*/
|
|
295
|
+
export function searchConfigWarnings(env = process.env, exists = existsSync) {
|
|
296
|
+
const warnings = [];
|
|
297
|
+
const seen = new Set();
|
|
298
|
+
const push = (source, raw) => {
|
|
299
|
+
const path = normalizePathEntry(raw);
|
|
300
|
+
if (path === "" || seen.has(path.toLowerCase()) || exists(path))
|
|
301
|
+
return;
|
|
302
|
+
seen.add(path.toLowerCase());
|
|
303
|
+
warnings.push({
|
|
304
|
+
source,
|
|
305
|
+
path,
|
|
306
|
+
message: (source === "config" ? "配置文件里的 " : "环境变量里的 ") +
|
|
307
|
+
path +
|
|
308
|
+
" 在本机不存在(配置可能是从别的机器拷来的),这一条搜不到工具;换机器后重跑 stm32_env_install,或手改 " +
|
|
309
|
+
(source === "config" ? "~/.dsh-stm32/config.json(DSH_STM32_CONFIG 可改位置)" : "STM32_BIN_DIRS / STM32_CUBEMX_ROOT"),
|
|
310
|
+
});
|
|
311
|
+
};
|
|
312
|
+
for (const dir of splitList(env["STM32_BIN_DIRS"]))
|
|
313
|
+
push("env", dir);
|
|
314
|
+
for (const dir of splitList(env["STM32_CUBEMX_ROOT"]))
|
|
315
|
+
push("env", dir);
|
|
316
|
+
const config = configReadingDisabled(env) ? null : readToolchainConfig(env).config;
|
|
317
|
+
if (config !== null) {
|
|
318
|
+
if (config.msys64 !== "")
|
|
319
|
+
push("config", config.msys64);
|
|
320
|
+
for (const dir of config.binDirs)
|
|
321
|
+
push("config", dir);
|
|
322
|
+
if (config.cubeMxRoot !== "")
|
|
323
|
+
push("config", config.cubeMxRoot);
|
|
324
|
+
}
|
|
325
|
+
return warnings;
|
|
326
|
+
}
|
|
327
|
+
/**
|
|
328
|
+
* 显式参数 / 环境变量 / 用户配置覆盖默认搜索配置。
|
|
221
329
|
*
|
|
222
|
-
* 优先级:显式参数 > 环境变量(整份替换,分号分隔)> 默认常量。
|
|
330
|
+
* 优先级:显式参数 > 环境变量(整份替换,分号分隔)> 用户配置文件(整份替换)> 默认常量。
|
|
223
331
|
* 自动发现的安装只追加在"没给显式参数"的那一档尾部:用参数点名目录时说明调用方
|
|
224
332
|
* 心里有确切位置,再混进别处的同名工具会让"我明明指定了"变成假的。
|
|
333
|
+
*
|
|
334
|
+
* 用户配置文件在这里读,是因为**这一层是唯一的汇聚点**:所有工具/引擎都经过它,
|
|
335
|
+
* 装完工具链后不必改任何调用方就能立即生效(不需要重启 DSH:路径是我们自己读的)。
|
|
225
336
|
*/
|
|
226
337
|
export function resolveSearchConfig(env = process.env, overrides = {},
|
|
227
338
|
/** 单测注入用;生产代码不要传。 */
|
|
228
339
|
discoveredOverride) {
|
|
229
340
|
const binFromEnv = splitList(env["STM32_BIN_DIRS"]);
|
|
230
341
|
const rootsFromEnv = splitList(env["STM32_CUBEMX_ROOT"]);
|
|
342
|
+
const userConfig = configReadingDisabled(env) ? null : readToolchainConfig(env).config;
|
|
343
|
+
const binFromConfig = binDirsFromConfig(userConfig);
|
|
344
|
+
const rootsFromConfig = cubeMxRootsFromConfig(userConfig);
|
|
231
345
|
const discovered = discoveryDisabled(env)
|
|
232
346
|
? { binDirs: [], cubeMxRoots: [] }
|
|
233
347
|
: (discoveredOverride ?? discoverInstalls());
|
|
234
|
-
const binBase = overrides.binDirs
|
|
235
|
-
|
|
348
|
+
const binBase = overrides.binDirs
|
|
349
|
+
?? (binFromEnv.length > 0
|
|
350
|
+
? binFromEnv
|
|
351
|
+
: (binFromConfig.length > 0 ? binFromConfig : [...DEFAULT_BIN_DIRS]));
|
|
352
|
+
const rootsBase = overrides.cubeMxRoots
|
|
353
|
+
?? (rootsFromEnv.length > 0
|
|
354
|
+
? rootsFromEnv
|
|
355
|
+
: (rootsFromConfig.length > 0 ? rootsFromConfig : [...DEFAULT_CUBEMX_ROOTS]));
|
|
236
356
|
return {
|
|
237
357
|
binDirs: dedupePaths([...binBase, ...(overrides.binDirs === undefined ? discovered.binDirs : [])]),
|
|
238
358
|
cubeMxRoots: dedupePaths([...rootsBase, ...(overrides.cubeMxRoots === undefined ? discovered.cubeMxRoots : [])]),
|
|
@@ -0,0 +1,186 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* L1:STM32F1 全系的芯片事实表(型号 → 容量档 / 启动文件 / 设备宏 / Flash / RAM)。
|
|
3
|
+
*
|
|
4
|
+
* 为什么单独一个文件:容量字母 → 上游启动文件的映射是事实,不是逻辑。
|
|
5
|
+
* 加一款芯片只改这里,不动引擎。
|
|
6
|
+
*
|
|
7
|
+
* 取数优先级(写进 docs/development-notes.md):
|
|
8
|
+
* 1. 固件包 `Drivers/CMSIS/Device/ST/STM32F1xx/Source/Templates/gcc` 里真实存在的启动文件
|
|
9
|
+
* —— 实测 F1 有 14 个(100 xb/xe、101 x6/xb/xe/xg、102 x6/xb、103 x6/xb/xe/xg、105 xc、107 xc)。
|
|
10
|
+
* 2. 本机 CubeMX 的 `db/mcu/*.xml`(Flash/RAM/引脚数,将来用作校验)。
|
|
11
|
+
* 3. 本文件内置的容量字母表。
|
|
12
|
+
*
|
|
13
|
+
* 关键坑:容量字母 → 容量档不是全局映射。字母 C 在 F103 上是 xE(startup_stm32f103xe.s),
|
|
14
|
+
* 在 F105/F107 上却是 xC(startup_stm32f105xc.s)——先按「line 真有这一档」匹配,再退回全局表。
|
|
15
|
+
*/
|
|
16
|
+
import { F1_RAM_FROM_DB } from "./f1-ram.generated.js";
|
|
17
|
+
/** 容量字母 → 上游容量档的兜底映射(当 line 没有「x + 字母」这个档时用它)。 */
|
|
18
|
+
const GROUP_BY_LETTER = {
|
|
19
|
+
"4": "x6",
|
|
20
|
+
"6": "x6",
|
|
21
|
+
"8": "xb",
|
|
22
|
+
B: "xb",
|
|
23
|
+
C: "xe",
|
|
24
|
+
D: "xe",
|
|
25
|
+
E: "xe",
|
|
26
|
+
F: "xg",
|
|
27
|
+
G: "xg",
|
|
28
|
+
};
|
|
29
|
+
/** 容量字母 → Flash 字节(ST 的容量字母就是 Flash 档)。 */
|
|
30
|
+
const FLASH_BY_LETTER = {
|
|
31
|
+
"4": 16 * 1024,
|
|
32
|
+
"6": 32 * 1024,
|
|
33
|
+
"8": 64 * 1024,
|
|
34
|
+
B: 128 * 1024,
|
|
35
|
+
C: 256 * 1024,
|
|
36
|
+
D: 384 * 1024,
|
|
37
|
+
E: 512 * 1024,
|
|
38
|
+
F: 768 * 1024,
|
|
39
|
+
G: 1024 * 1024,
|
|
40
|
+
};
|
|
41
|
+
/**
|
|
42
|
+
* RAM 字节。键是「line:容量字母」——一个容量档会跨多个字母,而它们的 RAM 并不相同
|
|
43
|
+
* (F103xC 是 48 KiB,F103xE 是 64 KiB),所以不能按档查。
|
|
44
|
+
* 只收有把握的组合;查不到返回 null 并在 notes 里说清楚,绝不猜。
|
|
45
|
+
*/
|
|
46
|
+
const RAM_BY_LINE_LETTER = {
|
|
47
|
+
"103:6": 10 * 1024,
|
|
48
|
+
"103:8": 20 * 1024,
|
|
49
|
+
"103:B": 20 * 1024,
|
|
50
|
+
"103:C": 48 * 1024,
|
|
51
|
+
"103:D": 64 * 1024,
|
|
52
|
+
"103:E": 64 * 1024,
|
|
53
|
+
"105:C": 64 * 1024,
|
|
54
|
+
"107:C": 64 * 1024,
|
|
55
|
+
};
|
|
56
|
+
/** F1 各 line 在上游真实存在的容量档(由固件包 gcc 启动文件实测得出;F106 不是独立产品线)。 */
|
|
57
|
+
export const F1_LINES = [
|
|
58
|
+
{ code: "100", prefix: "STM32F100", groups: ["xb", "xe"], familyDir: "STM32F1xx" },
|
|
59
|
+
{ code: "101", prefix: "STM32F101", groups: ["x6", "xb", "xe", "xg"], familyDir: "STM32F1xx" },
|
|
60
|
+
{ code: "102", prefix: "STM32F102", groups: ["x6", "xb"], familyDir: "STM32F1xx" },
|
|
61
|
+
{ code: "103", prefix: "STM32F103", groups: ["x6", "xb", "xe", "xg"], familyDir: "STM32F1xx" },
|
|
62
|
+
{ code: "105", prefix: "STM32F105", groups: ["xc"], familyDir: "STM32F1xx" },
|
|
63
|
+
{ code: "107", prefix: "STM32F107", groups: ["xc"], familyDir: "STM32F1xx" },
|
|
64
|
+
];
|
|
65
|
+
/** 封装字母(型号第 4 位)→ 引脚数。 */
|
|
66
|
+
const PINS_BY_PACKAGE = {
|
|
67
|
+
T: 36,
|
|
68
|
+
C: 48,
|
|
69
|
+
R: 64,
|
|
70
|
+
V: 100,
|
|
71
|
+
Z: 144,
|
|
72
|
+
};
|
|
73
|
+
/**
|
|
74
|
+
* 型号 → 芯片事实。认不出返回 chip: null + 原因,绝不编一个不存在的启动文件。
|
|
75
|
+
*
|
|
76
|
+
* 支持三种输入:
|
|
77
|
+
* - 完整型号:STM32F103C8T6 / STM32F103RCT6 / STM32F107VCT6
|
|
78
|
+
* - 去掉温度后缀:STM32F103C8
|
|
79
|
+
* - 显式容量档:F103:xb(脚本与测试用)
|
|
80
|
+
*/
|
|
81
|
+
export function resolveF1Chip(input) {
|
|
82
|
+
const text = input.trim().toUpperCase();
|
|
83
|
+
if (text.length === 0)
|
|
84
|
+
return { chip: null, reason: "没有给型号" };
|
|
85
|
+
const loose = /^F(\d{2,3}):(X[0-9A-Z]{1,2})$/u.exec(text);
|
|
86
|
+
if (loose !== null) {
|
|
87
|
+
const code = loose[1] ?? "";
|
|
88
|
+
const group = (loose[2] ?? "").toLowerCase();
|
|
89
|
+
const line = F1_LINES.find((item) => item.code === code);
|
|
90
|
+
if (line === undefined)
|
|
91
|
+
return { chip: null, reason: lineMissing(code) };
|
|
92
|
+
return fromGroup(line, group, "F" + code);
|
|
93
|
+
}
|
|
94
|
+
const m = /^STM32F(\d{3})([A-Z])([0-9A-G])([A-Z])?([0-9])?$/u.exec(text);
|
|
95
|
+
if (m === null)
|
|
96
|
+
return { chip: null, reason: "不是 F1 的型号格式:" + input };
|
|
97
|
+
const code = m[1] ?? "";
|
|
98
|
+
const packageLetter = m[2] ?? "";
|
|
99
|
+
const densityLetter = m[3] ?? "";
|
|
100
|
+
const suffix = m[4] ?? "";
|
|
101
|
+
const extra = m[5] ?? "";
|
|
102
|
+
if (suffix.length > 0 && !"TXUYK".includes(suffix)) {
|
|
103
|
+
return { chip: null, reason: "认不出封装后缀 " + suffix + "(期望 T/U/Y 之一):" + input };
|
|
104
|
+
}
|
|
105
|
+
if (extra.length > 0 && !"67".includes(extra)) {
|
|
106
|
+
return { chip: null, reason: "认不出温度档 " + extra + "(期望 6 或 7):" + input };
|
|
107
|
+
}
|
|
108
|
+
const line = F1_LINES.find((item) => item.code === code);
|
|
109
|
+
if (line === undefined)
|
|
110
|
+
return { chip: null, reason: lineMissing(code) };
|
|
111
|
+
const group = chooseGroup(line, densityLetter);
|
|
112
|
+
if (group === null) {
|
|
113
|
+
const fallback = GROUP_BY_LETTER[densityLetter];
|
|
114
|
+
if (fallback === undefined) {
|
|
115
|
+
return { chip: null, reason: "认不出容量字母 " + densityLetter + ":" + input };
|
|
116
|
+
}
|
|
117
|
+
return {
|
|
118
|
+
chip: null,
|
|
119
|
+
reason: line.prefix + " 没有 " + fallback + " 这一容量档(上游真实档位:" + line.groups.join("/") + ")",
|
|
120
|
+
};
|
|
121
|
+
}
|
|
122
|
+
return fromGroup(line, group, text, packageLetter, densityLetter);
|
|
123
|
+
}
|
|
124
|
+
function lineMissing(code) {
|
|
125
|
+
return "F1 里没有 F" + code + " 这一 line(已知:" + F1_LINES.map((x) => x.code).join("/") + ")";
|
|
126
|
+
}
|
|
127
|
+
/** 先认「line 真有 x+字母」,再退回全局表;都不行返回 null。 */
|
|
128
|
+
function chooseGroup(line, letter) {
|
|
129
|
+
const direct = "x" + letter.toLowerCase();
|
|
130
|
+
if (line.groups.includes(direct))
|
|
131
|
+
return direct;
|
|
132
|
+
const fallback = GROUP_BY_LETTER[letter];
|
|
133
|
+
if (fallback === undefined)
|
|
134
|
+
return null;
|
|
135
|
+
return line.groups.includes(fallback) ? fallback : null;
|
|
136
|
+
}
|
|
137
|
+
function fromGroup(line, group, cpn, packageLetter = "", densityLetter = "") {
|
|
138
|
+
const notes = [];
|
|
139
|
+
if (!line.groups.includes(group)) {
|
|
140
|
+
return {
|
|
141
|
+
chip: null,
|
|
142
|
+
reason: line.prefix + " 没有 " + group + " 这一容量档(上游真实档位:" + line.groups.join("/") + ")",
|
|
143
|
+
};
|
|
144
|
+
}
|
|
145
|
+
const letter = densityLetter.length > 0 ? densityLetter : letterForGroup(group);
|
|
146
|
+
const stem = line.prefix.toLowerCase() + group;
|
|
147
|
+
// 先用手写表(有把握的组合),再用生成表(CubeMX db 里「容量字母与 RAM 唯一对应」的条目)。
|
|
148
|
+
// db 给区间的分组(例如 F103R(C-D-E) 的 [48,64])不进生成表——字母对不上号时宁可不收。
|
|
149
|
+
const handRam = RAM_BY_LINE_LETTER[line.code + ":" + letter];
|
|
150
|
+
const dbRam = F1_RAM_FROM_DB[line.code + ":" + letter];
|
|
151
|
+
const ramBytes = handRam ?? dbRam ?? null;
|
|
152
|
+
if (handRam === undefined && dbRam !== undefined) {
|
|
153
|
+
notes.push("RAM 取自 CubeMX db 的容量档值(" + line.prefix + letter + " = " + String(dbRam / 1024) + " KiB)");
|
|
154
|
+
}
|
|
155
|
+
if (ramBytes === null) {
|
|
156
|
+
notes.push("RAM 大小未收录:" + line.prefix + letter + "(用 CubeMX 的 db/mcu 确认后再补表)");
|
|
157
|
+
}
|
|
158
|
+
if (packageLetter.length > 0 && PINS_BY_PACKAGE[packageLetter] === undefined) {
|
|
159
|
+
notes.push("认不出封装字母 " + packageLetter + ",引脚数未知");
|
|
160
|
+
}
|
|
161
|
+
return {
|
|
162
|
+
chip: {
|
|
163
|
+
cpn,
|
|
164
|
+
prefix: line.prefix,
|
|
165
|
+
densityLetter: letter,
|
|
166
|
+
group,
|
|
167
|
+
startup: "startup_" + stem + ".s",
|
|
168
|
+
deviceDefine: line.prefix + "x" + group.slice(1).toUpperCase(),
|
|
169
|
+
deviceHeader: stem + ".h",
|
|
170
|
+
pinCount: packageLetter.length > 0 ? (PINS_BY_PACKAGE[packageLetter] ?? null) : null,
|
|
171
|
+
flashBytes: FLASH_BY_LETTER[letter] ?? null,
|
|
172
|
+
ramBytes,
|
|
173
|
+
notes,
|
|
174
|
+
},
|
|
175
|
+
reason: "",
|
|
176
|
+
};
|
|
177
|
+
}
|
|
178
|
+
function letterForGroup(group) {
|
|
179
|
+
const found = Object.entries(GROUP_BY_LETTER).find(([, value]) => value === group);
|
|
180
|
+
return found === undefined ? "" : found[0];
|
|
181
|
+
}
|
|
182
|
+
/** 该 line 的全部容量档(给「这个型号能选哪些档」的报告用)。 */
|
|
183
|
+
export function f1GroupsFor(code) {
|
|
184
|
+
const line = F1_LINES.find((item) => item.code === code);
|
|
185
|
+
return line === undefined ? [] : line.groups;
|
|
186
|
+
}
|