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
|
@@ -0,0 +1,515 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* L1:ST 芯片族画像(跨族支持的唯一"族相关"事实表)。
|
|
3
|
+
*
|
|
4
|
+
* 为什么要这一层:插件早期只认 STM32F1——openocd 的 target 脚本名、CubeMX 固件包名、
|
|
5
|
+
* 内置资源里的 SVD 目录、硬件断点/观察点个数、.ioc 预设与时钟表,全都写死成 F1。
|
|
6
|
+
* 这些事实**CubeMX 的 db 里没有**(db 只给族 id/内核/主频/封装/引脚/IP),
|
|
7
|
+
* 所以集中放在这里,按族查一次。
|
|
8
|
+
*
|
|
9
|
+
* 反过来,族 id / 内核 / 最高主频 / Flash / RAM / 引脚数**不进这张表**:它们由
|
|
10
|
+
* engine/cubemx-db.ts 的 parseMcuXml 从本机 db/mcu/<Mcu.Name>.xml 读(Family/Core/
|
|
11
|
+
* Frequency/Flash/Ram/IONb)。db 一升级,那些数字自动跟着走,不用改代码。
|
|
12
|
+
*
|
|
13
|
+
* 证据(2026-11 实测,DB.6.0.150 + openocd 0.12.0,Windows):
|
|
14
|
+
* - db/mcu 共 2019 个 MCU xml,Family 属性恰好 27 个值(另有 3 个老文件没有 Family)。
|
|
15
|
+
* - openocd 的 target 目录(share/openocd/scripts/target)里 stm32 的脚本只有:
|
|
16
|
+
* f0x f1x f2x f3x f4x f7x g0x g4x h7x(+dual_bank) l0(+dual_bank) l1(+dual_bank) l4x
|
|
17
|
+
* l5x mp13x mp15x u5x wbx wlx x5x_common xl w108xx。
|
|
18
|
+
* —— 没有 C0/H5/N6/U0/U3/WBA/WB0/WL3/MP2 的专用脚本,这些族 openocdTarget = null,
|
|
19
|
+
* 烧录/调试时给明确拒绝理由,而不是拿别的族的 target 硬连。
|
|
20
|
+
*
|
|
21
|
+
* 能力闸门(capabilities)是**诚实降级**:值为 false 表示插件这条路线还没按该族实现,
|
|
22
|
+
* 调用方应当直接报"不支持"并说清原因,绝不能悄悄用 F1 的表去凑。
|
|
23
|
+
*/
|
|
24
|
+
import { existsSync, readFileSync, readdirSync } from "node:fs";
|
|
25
|
+
import { join } from "node:path";
|
|
26
|
+
import { fileURLToPath } from "node:url";
|
|
27
|
+
const NO_CAPS = {
|
|
28
|
+
halScaffold: false,
|
|
29
|
+
registerScaffold: false,
|
|
30
|
+
iocPresets: false,
|
|
31
|
+
clockPlan: false,
|
|
32
|
+
svdValidation: false,
|
|
33
|
+
};
|
|
34
|
+
/** F1 是唯一全线跑通的族(第一版目标芯片),五项能力全开。 */
|
|
35
|
+
const F1_CAPS = {
|
|
36
|
+
halScaffold: true,
|
|
37
|
+
registerScaffold: true,
|
|
38
|
+
iocPresets: true,
|
|
39
|
+
clockPlan: true,
|
|
40
|
+
svdValidation: true,
|
|
41
|
+
};
|
|
42
|
+
function profile(init) {
|
|
43
|
+
return {
|
|
44
|
+
id: init.id,
|
|
45
|
+
line: init.line,
|
|
46
|
+
core: init.core,
|
|
47
|
+
openocdTarget: init.target,
|
|
48
|
+
bundledTarget: init.bundled ?? null,
|
|
49
|
+
firmwarePrefix: init.firmware,
|
|
50
|
+
assetSvdDir: init.svd ?? null,
|
|
51
|
+
capabilities: init.caps ?? NO_CAPS,
|
|
52
|
+
note: init.note,
|
|
53
|
+
};
|
|
54
|
+
}
|
|
55
|
+
/**
|
|
56
|
+
* 增量 1 之后:14 个单核族的 HAL 路线已经按族实现(固件包按族找、启动文件/设备宏/链接脚本/
|
|
57
|
+
* .ioc 模板全部从「CubeMX 固件包 + 内置资源芯片表」派生),所以 halScaffold 为 true。
|
|
58
|
+
* 其余能力(寄存器模板 / .ioc 预设 / 时钟规划 / SVD 校验)仍只在 F1 上验过,留给后续增量。
|
|
59
|
+
*/
|
|
60
|
+
const HAL_CAPS = { ...NO_CAPS, halScaffold: true };
|
|
61
|
+
/**
|
|
62
|
+
* 寄存器路线已按族打通:内置资源 device/<族>/chips.json 有启动文件/设备宏/Flash/RAM,
|
|
63
|
+
* CMSIS 头从 cmsis-device-<族> + STM32Cube<族> 下载,GPIO 写法按族生成(register-gpio.ts)。
|
|
64
|
+
* 时钟只留复位默认(不猜 PLL 字段),这是刻意的降级,见 register-clock.ts 的 planGenericClock。
|
|
65
|
+
*/
|
|
66
|
+
const HAL_REG_CAPS = { ...HAL_CAPS, registerScaffold: true };
|
|
67
|
+
/** 还没做 HAL 支持的族(双核 / MPU / 范围外):说明为什么,别让工具悄悄退化。 */
|
|
68
|
+
const PENDING_HAL = "HAL 建工程只支持 22 个单核族(C0/F0/F1/F2/F3/F4/F7/G0/G4/H5/H7/L0/L1/L4/L4+/L5/U0/U3/U5/WBA/WL,另加双核的 WB 只建 M4 核),本族不在其中";
|
|
69
|
+
const PENDING_REG = "寄存器版模板(CMSIS 头 + 启动文件)目前只有 F1 与内置资源已有芯片表的 13 族(C0/F0/F1/F2/F3/F4/F7/G0/G4/L0/L1/L4/U0)";
|
|
70
|
+
const REG_OK = "寄存器版已按族打通(CMSIS 头 + 启动文件 + 按族 GPIO;时钟留复位默认)";
|
|
71
|
+
const PENDING_PRESET = ".ioc 外设预设表目前只有 F1(下一步按族从 db 的 RefParameter 生成)";
|
|
72
|
+
const PENDING_CLOCK = "时钟规划目前只按 F1 的 RCC/PLL 实现";
|
|
73
|
+
const NO_SVD = "内置资源只有 F1 的 SVD(中断名/寄存器名校验暂不可用)";
|
|
74
|
+
/**
|
|
75
|
+
* 每项能力"缺什么"的一句话(给工具报错用,不是给文档用)。
|
|
76
|
+
*
|
|
77
|
+
* 为什么不复用族 note:note 是给人看的整段理由(HAL/寄存器/预设/时钟/SVD 全塞在一条里),
|
|
78
|
+
* 工具拒绝某个参数时只需要那一项的原因。之前直接把 note 拼进 errors,一条报错 300 多字,
|
|
79
|
+
* 用户看不出到底哪一项挡住了他。
|
|
80
|
+
*/
|
|
81
|
+
export const CAPABILITY_GAPS = {
|
|
82
|
+
halScaffold: "HAL 建工程(模板/启动文件/链接脚本/设备宏)按 22 个单核族的固件包实现",
|
|
83
|
+
registerScaffold: "寄存器版模板(CMSIS 头 + 启动文件)只有内置资源已有芯片表的 13 族:C0/F0/F1/F2/F3/F4/F7/G0/G4/L0/L1/L4/U0",
|
|
84
|
+
iocPresets: "手写 .ioc 预设表只有 F1(其它族靠 db 派生 USART/UART/LPUART,TIM/ADC/DMA 仍需手写键)",
|
|
85
|
+
clockPlan: "时钟规划只按 F1 的 RCC/PLL 键实现",
|
|
86
|
+
svdValidation: "中断名/寄存器名校验要该族的 SVD,内置资源目前只有 F1 的",
|
|
87
|
+
};
|
|
88
|
+
/** 某项能力在某个族上缺什么(含族 id),供工具直接拼进告警/拒绝理由。 */
|
|
89
|
+
export function capabilityGap(profile, capability) {
|
|
90
|
+
return profile.id + ":" + CAPABILITY_GAPS[capability];
|
|
91
|
+
}
|
|
92
|
+
/**
|
|
93
|
+
* 27 个族的画像(顺序按 db 里的族字母排,便于比对)。
|
|
94
|
+
*
|
|
95
|
+
* firmwarePrefix 只写**已确认**的固件包名(ST 的命名就是 STM32Cube_FW_<族>,L4+ 零件在 L4 包里);
|
|
96
|
+
* 不确定的(WB0/WL3)写 null 并在 note 里说明,不在运行时猜。
|
|
97
|
+
*/
|
|
98
|
+
const PROFILES = [
|
|
99
|
+
profile({
|
|
100
|
+
id: "STM32C0", line: "C0", core: "Cortex-M0+", target: null, bundled: "stm32c0x", firmware: "STM32Cube_FW_C0", caps: HAL_REG_CAPS,
|
|
101
|
+
note: "openocd 0.12 没有 stm32c0x.cfg(C0 是 2023 年后的产品线):插件内置一份适配 0.12 的脚本(templates/openocd/stm32c0x.cfg)",
|
|
102
|
+
}),
|
|
103
|
+
profile({
|
|
104
|
+
id: "STM32F0", line: "F0", core: "Cortex-M0", target: "stm32f0x", firmware: "STM32Cube_FW_F0", caps: HAL_REG_CAPS,
|
|
105
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
106
|
+
}),
|
|
107
|
+
profile({
|
|
108
|
+
id: "STM32F1", line: "F1", core: "Cortex-M3", target: "stm32f1x", firmware: "STM32Cube_FW_F1",
|
|
109
|
+
svd: "device/f1/svd", caps: F1_CAPS,
|
|
110
|
+
note: "唯一全线跑通的族:HAL/寄存器两条建工程路线、.ioc 预设、时钟规划、SVD 校验都在 F1 上验过(蓝丸 F103C8T6 + RCT6 + F107)",
|
|
111
|
+
}),
|
|
112
|
+
profile({
|
|
113
|
+
id: "STM32F2", line: "F2", core: "Cortex-M3", target: "stm32f2x", firmware: "STM32Cube_FW_F2", caps: HAL_REG_CAPS,
|
|
114
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
115
|
+
}),
|
|
116
|
+
profile({
|
|
117
|
+
id: "STM32F3", line: "F3", core: "Cortex-M4", target: "stm32f3x", firmware: "STM32Cube_FW_F3", caps: HAL_REG_CAPS,
|
|
118
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
119
|
+
}),
|
|
120
|
+
profile({
|
|
121
|
+
id: "STM32F4", line: "F4", core: "Cortex-M4", target: "stm32f4x", firmware: "STM32Cube_FW_F4", caps: HAL_REG_CAPS,
|
|
122
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
123
|
+
}),
|
|
124
|
+
profile({
|
|
125
|
+
id: "STM32F7", line: "F7", core: "Cortex-M7", target: "stm32f7x", firmware: "STM32Cube_FW_F7", caps: HAL_REG_CAPS,
|
|
126
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
127
|
+
}),
|
|
128
|
+
profile({
|
|
129
|
+
id: "STM32G0", line: "G0", core: "Cortex-M0+", target: "stm32g0x", firmware: "STM32Cube_FW_G0", caps: HAL_REG_CAPS,
|
|
130
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
131
|
+
}),
|
|
132
|
+
profile({
|
|
133
|
+
id: "STM32G4", line: "G4", core: "Cortex-M4", target: "stm32g4x", firmware: "STM32Cube_FW_G4", caps: HAL_REG_CAPS,
|
|
134
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
135
|
+
}),
|
|
136
|
+
profile({
|
|
137
|
+
id: "STM32H5", line: "H5", core: "Cortex-M33", target: null, firmware: "STM32Cube_FW_H5", caps: HAL_CAPS,
|
|
138
|
+
note: "openocd 0.12 只有 stm32x5x_common.cfg(公共片段),没有 h5x 目标脚本 —— 不能用 u5x 顶替",
|
|
139
|
+
}),
|
|
140
|
+
profile({
|
|
141
|
+
id: "STM32H7", line: "H7", core: "Cortex-M7", target: "stm32h7x", firmware: "STM32Cube_FW_H7", caps: HAL_CAPS,
|
|
142
|
+
note: "双 bank 器件可用 openocd.cfg 里改 source target/stm32h7x_dual_bank.cfg" + ";" + PENDING_CLOCK,
|
|
143
|
+
}),
|
|
144
|
+
profile({
|
|
145
|
+
id: "STM32L0", line: "L0", core: "Cortex-M0+", target: "stm32l0", firmware: "STM32Cube_FW_L0", caps: HAL_REG_CAPS,
|
|
146
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
147
|
+
}),
|
|
148
|
+
profile({
|
|
149
|
+
id: "STM32L1", line: "L1", core: "Cortex-M3", target: "stm32l1", firmware: "STM32Cube_FW_L1", caps: HAL_REG_CAPS,
|
|
150
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
151
|
+
}),
|
|
152
|
+
profile({
|
|
153
|
+
id: "STM32L4", line: "L4", core: "Cortex-M4", target: "stm32l4x", firmware: "STM32Cube_FW_L4", caps: HAL_REG_CAPS,
|
|
154
|
+
note: REG_OK + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
155
|
+
}),
|
|
156
|
+
profile({
|
|
157
|
+
id: "STM32L4+", line: "L4+", core: "Cortex-M4", target: "stm32l4x", firmware: "STM32Cube_FW_L4", caps: HAL_CAPS,
|
|
158
|
+
note: "L4+ 零件(L4P5/L4Q5/L4R5/L4S5…)共用 STM32Cube_FW_L4 固件包与 openocd 的 stm32l4x.cfg" + ";" + PENDING_CLOCK,
|
|
159
|
+
}),
|
|
160
|
+
profile({
|
|
161
|
+
id: "STM32L5", line: "L5", core: "Cortex-M33", target: "stm32l5x", firmware: "STM32Cube_FW_L5", caps: HAL_CAPS,
|
|
162
|
+
note: PENDING_REG + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
163
|
+
}),
|
|
164
|
+
profile({
|
|
165
|
+
id: "STM32MP1", line: "MP1", core: "Cortex-A7", target: "stm32mp15x", firmware: "STM32Cube_FW_MP1",
|
|
166
|
+
note: "MPU:裸机要跑在 M4 协处理上,A7 侧是 Linux/OpenSTLinux —— 本插件的建工程与调试路线都不适用" + ";" + NO_SVD,
|
|
167
|
+
}),
|
|
168
|
+
profile({
|
|
169
|
+
id: "STM32MP2", line: "MP2", core: "Cortex-A35", target: null, firmware: "STM32Cube_FW_MP2",
|
|
170
|
+
note: "MPU:openocd 0.12 没有 mp2 目标脚本,且本插件的建工程/调试路线不适用于 A35 + M33 的 MPU",
|
|
171
|
+
}),
|
|
172
|
+
profile({
|
|
173
|
+
id: "STM32N6", line: "N6", core: "Cortex-M55", target: null, firmware: "STM32Cube_FW_N6",
|
|
174
|
+
note: "openocd 0.12 没有 n6 目标脚本(NPU 系列,2024 年后产品)",
|
|
175
|
+
}),
|
|
176
|
+
profile({
|
|
177
|
+
id: "STM32U0", line: "U0", core: "Cortex-M0+", target: null, bundled: "stm32u0x", firmware: "STM32Cube_FW_U0", caps: HAL_REG_CAPS,
|
|
178
|
+
note: "openocd 0.12 没有 u0 目标脚本:插件内置一份适配 0.12 的脚本(templates/openocd/stm32u0x.cfg)",
|
|
179
|
+
}),
|
|
180
|
+
profile({
|
|
181
|
+
id: "STM32U3", line: "U3", core: "Cortex-M33", target: null, firmware: "STM32Cube_FW_U3", caps: HAL_CAPS,
|
|
182
|
+
note: "openocd 0.12 没有 u3 目标脚本",
|
|
183
|
+
}),
|
|
184
|
+
profile({
|
|
185
|
+
id: "STM32U5", line: "U5", core: "Cortex-M33", target: "stm32u5x", firmware: "STM32Cube_FW_U5", caps: HAL_CAPS,
|
|
186
|
+
note: PENDING_REG + ";" + PENDING_PRESET + ";" + PENDING_CLOCK + ";" + NO_SVD,
|
|
187
|
+
}),
|
|
188
|
+
profile({
|
|
189
|
+
id: "STM32WB", line: "WB", core: "Cortex-M4", target: "stm32wbx", firmware: "STM32Cube_FW_WB",
|
|
190
|
+
note: "双核(M4 + M0+ 射频核):只对 M4 应用核建工程/调试,射频核不碰" + ";" + PENDING_HAL + ";" + PENDING_CLOCK,
|
|
191
|
+
}),
|
|
192
|
+
profile({
|
|
193
|
+
id: "STM32WB0", line: "WB0", core: "Cortex-M0+", target: null, firmware: null,
|
|
194
|
+
note: "openocd 0.12 没有 wb0 目标脚本;固件包名未确认(STM32CubeWB0 还是并入 WB),运行时不去猜",
|
|
195
|
+
}),
|
|
196
|
+
profile({
|
|
197
|
+
id: "STM32WBA", line: "WBA", core: "Cortex-M33", target: null, firmware: "STM32Cube_FW_WBA", caps: HAL_CAPS,
|
|
198
|
+
note: "openocd 0.12 没有 wba 目标脚本",
|
|
199
|
+
}),
|
|
200
|
+
profile({
|
|
201
|
+
id: "STM32WL", line: "WL", core: "Cortex-M4", target: "stm32wlx", firmware: "STM32Cube_FW_WL", caps: HAL_CAPS,
|
|
202
|
+
note: "Sub-GHz 无线:M4 应用核可建工程/调试,射频部分不碰" + ";" + PENDING_CLOCK,
|
|
203
|
+
}),
|
|
204
|
+
profile({
|
|
205
|
+
id: "STM32WL3", line: "WL3", core: "Cortex-M0+", target: null, firmware: null,
|
|
206
|
+
note: "openocd 0.12 没有 wl3 目标脚本;固件包名未确认",
|
|
207
|
+
}),
|
|
208
|
+
];
|
|
209
|
+
const BY_ID = new Map(PROFILES.map((item) => [item.id.toUpperCase(), item]));
|
|
210
|
+
/** 所有有画像的族(27 条,含 MPU)。 */
|
|
211
|
+
export function familyProfiles() {
|
|
212
|
+
return PROFILES;
|
|
213
|
+
}
|
|
214
|
+
/**
|
|
215
|
+
* 型号 → 族 id。只做字符串判定,不查 db(db 里 MCU xml 的 Family 属性是更权威的来源,
|
|
216
|
+
* 见 engine/cubemx-db.ts 的 parseMcuXml;这里用于没有 db 的场合与 .ioc 缺失时的兜底)。
|
|
217
|
+
*
|
|
218
|
+
* 例:STM32F103C8T6 → STM32F1;STM32L4R5ZIT6 → STM32L4+;STM32WBA55CG → STM32WBA;
|
|
219
|
+
* STM32H563ZI → STM32H5;STM32U575ZI → STM32U5;STM32G071RB → STM32G0。
|
|
220
|
+
*/
|
|
221
|
+
export function familyIdOfPart(part) {
|
|
222
|
+
const raw = part.trim().toUpperCase();
|
|
223
|
+
if (!raw.startsWith("STM32"))
|
|
224
|
+
return "";
|
|
225
|
+
const tail = raw.slice("STM32".length);
|
|
226
|
+
// 族段长度不一(C0/F1/H7 两位,WB/WL 两位无数字,WBA/WB0/WL3/MP1/MP2 三位),
|
|
227
|
+
// 与其写一堆正则特例,不如直接拿族表里的段做前缀匹配、取最长的那个:
|
|
228
|
+
// STM32WBA55CG → WBA(3)胜过 WB;STM32WB55RG → WB;STM32H563ZI → H5。
|
|
229
|
+
// 边界条件:族段后面必须紧跟数字或字符串结束。否则 STM32L4R5ZIT6 会被判成 L4("L4" 后面是字母 R)。
|
|
230
|
+
// L4+ 要先判:L4P5/L4Q5/L4R5/L4S5 的前缀也是 L4,等到循环里就会被 L4 抢走。
|
|
231
|
+
if (/^L4[PQRS]/u.test(tail))
|
|
232
|
+
return "STM32L4+";
|
|
233
|
+
let best = "";
|
|
234
|
+
let bestSegment = 0; // 记住"最长的族段",不能拿族 id 的长度比("STM32WB" 比 "WB0" 长,会选错)
|
|
235
|
+
for (const item of PROFILES) {
|
|
236
|
+
const segment = item.id.slice("STM32".length).toUpperCase();
|
|
237
|
+
// L4+ 不是字面前缀:零件名是 L4P/L4Q/L4R/L4S(族属性写 STM32L4+,不是笔误),走下面单独判。
|
|
238
|
+
if (segment.endsWith("+"))
|
|
239
|
+
continue;
|
|
240
|
+
if (!tail.startsWith(segment))
|
|
241
|
+
continue;
|
|
242
|
+
const next = tail.slice(segment.length, segment.length + 1);
|
|
243
|
+
// 后面跟字母时,只有「字母+数字」这种子族段才算继续(H7A3 的 A3、H7B0 的 B0);
|
|
244
|
+
// 单纯的字母说明这是别的族(L4R5 已在上面按 L4+ 处理,WB55 的 B 后面是 5 但 segment WB 更短、不冲突)。
|
|
245
|
+
const after = tail.slice(segment.length + 1, segment.length + 2);
|
|
246
|
+
if (next !== "" && /[A-Z]/u.test(next) && !/[0-9]/u.test(after))
|
|
247
|
+
continue;
|
|
248
|
+
if (segment.length > bestSegment) {
|
|
249
|
+
best = item.id;
|
|
250
|
+
bestSegment = segment.length;
|
|
251
|
+
}
|
|
252
|
+
}
|
|
253
|
+
return best;
|
|
254
|
+
}
|
|
255
|
+
/** 族 id / 型号 / 族段("F1"、"STM32F1")→ 画像;认不出的族返回一个"全不支持"的画像。 */
|
|
256
|
+
export function familyProfileOf(idOrPart) {
|
|
257
|
+
const raw = idOrPart.trim().toUpperCase();
|
|
258
|
+
if (raw === "")
|
|
259
|
+
return unknownFamilyProfile("");
|
|
260
|
+
const direct = BY_ID.get(raw);
|
|
261
|
+
if (direct !== undefined)
|
|
262
|
+
return direct;
|
|
263
|
+
// "F1" / "L4+" / "WBA" 这种族段
|
|
264
|
+
if (/^[A-Z]{1,2}[0-9]\+?$/u.test(raw)) {
|
|
265
|
+
const byLine = BY_ID.get("STM32" + raw);
|
|
266
|
+
if (byLine !== undefined)
|
|
267
|
+
return byLine;
|
|
268
|
+
}
|
|
269
|
+
const byPart = familyIdOfPart(raw);
|
|
270
|
+
if (byPart !== "") {
|
|
271
|
+
const found = BY_ID.get(byPart.toUpperCase());
|
|
272
|
+
if (found !== undefined)
|
|
273
|
+
return found;
|
|
274
|
+
}
|
|
275
|
+
return unknownFamilyProfile(idOrPart);
|
|
276
|
+
}
|
|
277
|
+
/** 认不出的族:id 原样保留,能力全 false,note 说清"别猜"。 */
|
|
278
|
+
export function unknownFamilyProfile(id) {
|
|
279
|
+
return {
|
|
280
|
+
id: id.trim() === "" ? "未知族" : id.trim(),
|
|
281
|
+
line: "",
|
|
282
|
+
core: "",
|
|
283
|
+
openocdTarget: null,
|
|
284
|
+
bundledTarget: null,
|
|
285
|
+
firmwarePrefix: null,
|
|
286
|
+
assetSvdDir: null,
|
|
287
|
+
capabilities: NO_CAPS,
|
|
288
|
+
note: "没有这个族的画像(不是已知的 27 个 STM32 族之一):所有按族的能力一律不放行,先确认型号拼写",
|
|
289
|
+
};
|
|
290
|
+
}
|
|
291
|
+
/** 该族是否就是 F1(第一版唯一全线支持的族,供调用方做"新旧行为"分支)。 */
|
|
292
|
+
export function isF1(profile) {
|
|
293
|
+
return profile.id.toUpperCase() === "STM32F1";
|
|
294
|
+
}
|
|
295
|
+
/**
|
|
296
|
+
* 按内核的硬件预算(ARM 文档值,不是某个型号的实测值):
|
|
297
|
+
* Cortex-M0 / M0+ → 4 断点 / 2 观察点(FPB 只有 4 个比较器、DWT 2 个)
|
|
298
|
+
* Cortex-M3 / M4 → 6 / 4
|
|
299
|
+
* Cortex-M7 / M33 / M55 → 8 / 4
|
|
300
|
+
* 单型号可以在内置资源 chips.json 里写 breakpoints/watchpoints 覆盖(breakpoints.ts 优先用它)。
|
|
301
|
+
*/
|
|
302
|
+
// 顺序有讲究:M33 里含有 "m3" 子串,所以 M7/M33/M55 必须排在 M3/M4 前面判。
|
|
303
|
+
const CORE_BUDGETS = [
|
|
304
|
+
[/cortex-m0/i, { code: 4, data: 2 }],
|
|
305
|
+
[/cortex-m7|cortex-m33|cortex-m55/i, { code: 8, data: 4 }],
|
|
306
|
+
[/cortex-m3|cortex-m4/i, { code: 6, data: 4 }],
|
|
307
|
+
];
|
|
308
|
+
/** F1(Cortex-M3)的实测值,也是所有查不到内核时的兜底。 */
|
|
309
|
+
export const FALLBACK_DEBUG_BUDGET = { code: 6, data: 4 };
|
|
310
|
+
/** 内核名 → 硬件断点/观察点预算;查不到返回 F1 的 6/4(调用方应在 notes 里说明是兜底)。 */
|
|
311
|
+
export function debugBudgetForCore(core) {
|
|
312
|
+
const raw = core.trim();
|
|
313
|
+
if (raw === "")
|
|
314
|
+
return FALLBACK_DEBUG_BUDGET;
|
|
315
|
+
for (const [pattern, budget] of CORE_BUDGETS) {
|
|
316
|
+
if (pattern.test(raw))
|
|
317
|
+
return budget;
|
|
318
|
+
}
|
|
319
|
+
return FALLBACK_DEBUG_BUDGET;
|
|
320
|
+
}
|
|
321
|
+
/**
|
|
322
|
+
* 族画像 → 预算(MPU 的 A7/A35 不用这个模型,返回 null 让调用方跳过比较器预算)。
|
|
323
|
+
* 内核未知(空串)也返回 null:不知道内核就不该假装算得出一条数值预算,
|
|
324
|
+
* 让调用方退回"按 F1 兜底并说明原因"的老路径。
|
|
325
|
+
*/
|
|
326
|
+
export function debugBudgetOfFamily(profile) {
|
|
327
|
+
const core = profile.core.trim();
|
|
328
|
+
if (core === "")
|
|
329
|
+
return null;
|
|
330
|
+
if (/cortex-a/i.test(core))
|
|
331
|
+
return null;
|
|
332
|
+
return debugBudgetForCore(core);
|
|
333
|
+
}
|
|
334
|
+
/**
|
|
335
|
+
* 插件内置的 target 脚本绝对路径(C0 → templates/openocd/stm32c0x.cfg)。
|
|
336
|
+
*
|
|
337
|
+
* 为什么要内置:openocd 0.12(2023-01 的最后一个正式版)没有 stm32c0x.cfg / stm32u0x.cfg,
|
|
338
|
+
* 而这两族已经在 14 个单核族的支持范围里。上游 master 版脚本只用了 0.13 才有的
|
|
339
|
+
* `dap create ... -tap`,把它换成 0.12 认的 `-chain-position` 就能完整加载(adapter/target/flash bank
|
|
340
|
+
* 全部通过,只有没接探针时 init 会报 CMSIS-DAP CMD_INFO failed)。
|
|
341
|
+
* 文件放在插件模板目录而不是系统 openocd 目录:升级/卸载 openocd 不会把支持弄丢,
|
|
342
|
+
* 也不去改用户机器上的 openocd 安装。
|
|
343
|
+
*/
|
|
344
|
+
export function bundledOpenocdConfig(name) {
|
|
345
|
+
const trimmed = name.trim();
|
|
346
|
+
if (trimmed === "")
|
|
347
|
+
return null;
|
|
348
|
+
const file = fileURLToPath(new URL("../../templates/openocd/" + trimmed + ".cfg", import.meta.url));
|
|
349
|
+
return existsSync(file) ? file : null;
|
|
350
|
+
}
|
|
351
|
+
/**
|
|
352
|
+
* 族 → openocd target 配置。
|
|
353
|
+
*
|
|
354
|
+
* family 传 null 表示"工程里没有 .ioc / 认不出族":保持历史行为回退 stm32f1x,
|
|
355
|
+
* 但在 note 里说明这是兜底(用户可自己在 openocd.cfg 里写 target)。
|
|
356
|
+
*/
|
|
357
|
+
export function chooseOpenocdTarget(family) {
|
|
358
|
+
if (family === null) {
|
|
359
|
+
return {
|
|
360
|
+
targetConfig: "target/stm32f1x.cfg",
|
|
361
|
+
note: "工程里没有可读的 .ioc(认不出芯片族),openocd 回退 target/stm32f1x.cfg;换族请在工程里放 openocd.cfg 写死 target",
|
|
362
|
+
error: "",
|
|
363
|
+
bundled: false,
|
|
364
|
+
};
|
|
365
|
+
}
|
|
366
|
+
if (family.openocdTarget === null) {
|
|
367
|
+
// 没有官方脚本但有内置脚本(C0 / U0):用插件自带的那份,而不是拒绝
|
|
368
|
+
if (family.bundledTarget !== null) {
|
|
369
|
+
const bundled = bundledOpenocdConfig(family.bundledTarget);
|
|
370
|
+
if (bundled !== null) {
|
|
371
|
+
return {
|
|
372
|
+
targetConfig: bundled,
|
|
373
|
+
note: family.id + " 的 target 脚本 openocd 0.12 里没有,改用插件内置的 " + bundled,
|
|
374
|
+
error: "",
|
|
375
|
+
bundled: true,
|
|
376
|
+
};
|
|
377
|
+
}
|
|
378
|
+
return {
|
|
379
|
+
targetConfig: "",
|
|
380
|
+
note: family.note,
|
|
381
|
+
error: family.id + " 要靠插件内置的 target 脚本烧录/调试,但模板里没有 templates/openocd/" + family.bundledTarget +
|
|
382
|
+
".cfg(插件安装不完整):重新安装插件,或在工程根目录放一份 openocd.cfg 写死 target",
|
|
383
|
+
bundled: false,
|
|
384
|
+
};
|
|
385
|
+
}
|
|
386
|
+
return {
|
|
387
|
+
targetConfig: "",
|
|
388
|
+
note: family.note,
|
|
389
|
+
error: "本机 openocd 没有 " + family.id + " 的 target 脚本(" + family.note + "):" +
|
|
390
|
+
"请在工程根目录放一份 openocd.cfg 写死 source [find target/xxx.cfg],或用 openocd 的 -f 显式指定;" +
|
|
391
|
+
"不要拿别的族的 target 硬连(会连不上或读错 flash 布局)",
|
|
392
|
+
bundled: false,
|
|
393
|
+
};
|
|
394
|
+
}
|
|
395
|
+
return {
|
|
396
|
+
targetConfig: "target/" + family.openocdTarget + ".cfg",
|
|
397
|
+
note: "",
|
|
398
|
+
error: "",
|
|
399
|
+
bundled: false,
|
|
400
|
+
};
|
|
401
|
+
}
|
|
402
|
+
// ── 从工程里读族 ────────────────────────────────────────────────────────────
|
|
403
|
+
/**
|
|
404
|
+
* 工程里 .ioc 的 Mcu.Family(例如 STM32F1)。找不到/读不出来返回空串。
|
|
405
|
+
*
|
|
406
|
+
* 多个 .ioc 时按文件名排序取第一个读得出 Mcu.Family 的(与 breakpoints.ts 的 readIocCpn 同规则)。
|
|
407
|
+
*/
|
|
408
|
+
export function readIocFamilyId(projectDir) {
|
|
409
|
+
let names;
|
|
410
|
+
try {
|
|
411
|
+
names = readdirSync(projectDir);
|
|
412
|
+
}
|
|
413
|
+
catch {
|
|
414
|
+
return "";
|
|
415
|
+
}
|
|
416
|
+
const candidates = names.filter((name) => name.toLowerCase().endsWith(".ioc")).sort();
|
|
417
|
+
for (const name of candidates) {
|
|
418
|
+
try {
|
|
419
|
+
const text = readFileSync(join(projectDir, name), "utf8");
|
|
420
|
+
const matched = /^Mcu\.Family=(.+)$/mu.exec(text);
|
|
421
|
+
const family = matched === null ? "" : (matched[1] ?? "").trim();
|
|
422
|
+
if (family !== "")
|
|
423
|
+
return family;
|
|
424
|
+
}
|
|
425
|
+
catch {
|
|
426
|
+
// 读不了就试下一个
|
|
427
|
+
}
|
|
428
|
+
// 没有 Mcu.Family 的老 .ioc:退回按 Mcu.CPN 推族。
|
|
429
|
+
try {
|
|
430
|
+
const text = readFileSync(join(projectDir, name), "utf8");
|
|
431
|
+
const matched = /^Mcu\.CPN=(.+)$/mu.exec(text);
|
|
432
|
+
const cpn = matched === null ? "" : (matched[1] ?? "").trim();
|
|
433
|
+
const id = familyIdOfPart(cpn);
|
|
434
|
+
if (id !== "")
|
|
435
|
+
return id;
|
|
436
|
+
}
|
|
437
|
+
catch {
|
|
438
|
+
// 同上
|
|
439
|
+
}
|
|
440
|
+
}
|
|
441
|
+
return "";
|
|
442
|
+
}
|
|
443
|
+
/** 工程 → 族画像;认不出返回 null(调用方按"没有 .ioc"处理)。 */
|
|
444
|
+
export function readProjectFamily(projectDir) {
|
|
445
|
+
const id = readIocFamilyId(projectDir);
|
|
446
|
+
if (id === "")
|
|
447
|
+
return null;
|
|
448
|
+
const profileOfIoc = familyProfileOf(id);
|
|
449
|
+
// familyProfileOf 认不出时会返回"未知族"画像,这里区分开:真未知也要返回画像(能力全 false),
|
|
450
|
+
// 只是 id 不是空串,所以用 BY_ID 判断是否已知。
|
|
451
|
+
return profileOfIoc;
|
|
452
|
+
}
|
|
453
|
+
/** 该族画像是否来自已知的 27 个族之一。 */
|
|
454
|
+
export function isKnownFamily(profile) {
|
|
455
|
+
return BY_ID.has(profile.id.toUpperCase());
|
|
456
|
+
}
|
|
457
|
+
/**
|
|
458
|
+
* EXTI 分组的机制:Cortex 内核的 NVIC 只有一条 EXTI 线的位图,
|
|
459
|
+
* 「哪几条线共用一个向量」是**硅片厂商在芯片层面**捆的,和内核强相关:
|
|
460
|
+
* M0 / M0+(C0/F0/G0/L0/U0/WB0/WL3)→ EXTI0_1(0-1)、EXTI2_3(2-3)、EXTI4_15(4-15)
|
|
461
|
+
* M3 / M4 / M7(F1/F2/F3/F4/F7/G4/L1/L4/WB/WL/H7)→ EXTI0..EXTI4 逐线、EXTI9_5(5-9)、EXTI15_10(10-15)
|
|
462
|
+
* M33 / M55(H5/L5/U3/U5/N6/WBA)→ 16 条线全部逐线 EXTI0..EXTI15
|
|
463
|
+
* Cortex-A(MP1/MP2)→ 不走 NVIC/EXTI 模型,空表
|
|
464
|
+
*
|
|
465
|
+
* 证据(2026-11,504 份 CubeMX 板级 .ioc 里 NVIC.EXTI*_IRQn 的实测分布):
|
|
466
|
+
* C0 → 只有 EXTI4_15;L0 → EXTI0_1 + EXTI4_15;F1 → EXTI15_10(板级模板没用到 5-9 那一档);
|
|
467
|
+
* F4/G4/L4/WB → EXTI0..EXTI4 + EXTI9_5 + EXTI15_10;U5/WBA → 逐线 EXTI0..EXTI15;N6 → EXTI13。
|
|
468
|
+
* 也就是说:拿 F1 的分组去写 C0/L0/U5,会写出一个该芯片根本不存在的向量名,CubeMX 静默丢弃。
|
|
469
|
+
*/
|
|
470
|
+
const M0_EXTI_VECTORS = [
|
|
471
|
+
{ name: "EXTI0_1", from: 0, to: 1 },
|
|
472
|
+
{ name: "EXTI2_3", from: 2, to: 3 },
|
|
473
|
+
{ name: "EXTI4_15", from: 4, to: 15 },
|
|
474
|
+
];
|
|
475
|
+
const M3M4M7_EXTI_VECTORS = [
|
|
476
|
+
{ name: "EXTI0", from: 0, to: 0 },
|
|
477
|
+
{ name: "EXTI1", from: 1, to: 1 },
|
|
478
|
+
{ name: "EXTI2", from: 2, to: 2 },
|
|
479
|
+
{ name: "EXTI3", from: 3, to: 3 },
|
|
480
|
+
{ name: "EXTI4", from: 4, to: 4 },
|
|
481
|
+
{ name: "EXTI9_5", from: 5, to: 9 },
|
|
482
|
+
{ name: "EXTI15_10", from: 10, to: 15 },
|
|
483
|
+
];
|
|
484
|
+
/** M33/M55:16 条线各一个向量(EXTI0..EXTI15)。 */
|
|
485
|
+
const PER_LINE_EXTI_VECTORS = Array.from({ length: 16 }, (_, line) => ({
|
|
486
|
+
name: "EXTI" + String(line),
|
|
487
|
+
from: line,
|
|
488
|
+
to: line,
|
|
489
|
+
}));
|
|
490
|
+
/** 认不出内核时的兜底:F1 的 M3 分组(保持历史行为,调用方应在 notes 里说明)。 */
|
|
491
|
+
export const FALLBACK_EXTI_VECTORS = M3M4M7_EXTI_VECTORS;
|
|
492
|
+
/**
|
|
493
|
+
* 族 → EXTI 向量分组。profile 为 null(工程里读不到族)时返回 F1 的 M3 分组,
|
|
494
|
+
* 这是历史行为,调用方要自行在报告里说明"分组按 M3 兜底"。
|
|
495
|
+
*/
|
|
496
|
+
export function extiVectorsOf(profile) {
|
|
497
|
+
const core = (profile?.core ?? "").trim();
|
|
498
|
+
if (core === "")
|
|
499
|
+
return FALLBACK_EXTI_VECTORS;
|
|
500
|
+
if (/cortex-m0/i.test(core))
|
|
501
|
+
return M0_EXTI_VECTORS;
|
|
502
|
+
if (/cortex-m33|cortex-m55/i.test(core))
|
|
503
|
+
return PER_LINE_EXTI_VECTORS;
|
|
504
|
+
if (/cortex-a/i.test(core))
|
|
505
|
+
return [];
|
|
506
|
+
return M3M4M7_EXTI_VECTORS;
|
|
507
|
+
}
|
|
508
|
+
/** EXTI 线号 → 该族的 NVIC 中断名(不带 _IRQn);这根线不在任何向量里返回空串。 */
|
|
509
|
+
export function extiVectorNameOf(line, profile) {
|
|
510
|
+
for (const vector of extiVectorsOf(profile)) {
|
|
511
|
+
if (line >= vector.from && line <= vector.to)
|
|
512
|
+
return vector.name;
|
|
513
|
+
}
|
|
514
|
+
return "";
|
|
515
|
+
}
|