新的S32K144无法烧录


新的板子来了,但是这次无法烧录了,下面是日志
SEGGER J-Link GDB Server V9.72 Command Line Version

JLinkARM.dll V9.72 (DLL compiled Aug 26 2026 14:38:37)

WARNING: Unknown command line parameter -RestoreRAMOnDownload found.
WARNING: Unknown command line parameter 0 found.
Command line: -if swd -device S32K144 -endian little -speed 500 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -timeout 0 -nogui -RestoreRAMOnDownload 0
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: on
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: S32K144
Target device parameters: none
Target interface: SWD
Target interface speed: 500kHz
Target endian: little

Connecting to J-Link…
J-Link is connected.
Firmware: J-Link LPCXpresso V2 compiled May 2 2023 17:39:56
Hardware: V1.00
S/N: 724304970
Checking target voltage…
Target voltage: 3.30 V
Listening on TCP/IP port 2331
Connecting to target…
ERROR: J-Link script file function InitTarget() returned with error code -1

ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed…Restoring target state and closing J-Link connection…
Shutting down…
Could not connect to target.
Please check power, connection and settings.

芯片也连接不上,RESET对地0V

SEGGER J-Link Commander V9.72 (Compiled Aug 26 2026 14:39:38)
DLL version V9.72, compiled Aug 26 2026 14:38:37

Connecting to J-Link …O.K.
Firmware: J-Link LPCXpresso V2 compiled May 2 2023 17:39:56
Hardware version: V1.00
J-Link uptime (since boot): 0d 00h 20m 46s
S/N: 724304970
VTref=3.300V

Type “connect” to establish a target connection, ‘?’ for help
J-Link>connect
Please specify device / core. : S32K144
Type ‘?’ for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>S
Specify target interface speed [kHz]. : 4000 kHz
Speed>
Device “S32K144” selected.

Connecting to target via SWD
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 15us
InitTarget() start
SWD selected. Executing JTAG → SWD switching sequence.
Connect Under Reset
SWD selected. Executing JTAG → SWD switching sequence.
Communication error while accessing MDM-AP.
Connect Under Reset
InitTarget() end - Took 409ms
Connect failed. Resetting via Reset pin and trying again.
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 13us
InitTarget() start
SWD selected. Executing JTAG → SWD switching sequence.
Connect Under Reset
SWD selected. Executing JTAG → SWD switching sequence.
Communication error while accessing MDM-AP.
Connect Under Reset
InitTarget() end - Took 406ms

****** Error: J-Link script file function InitTarget() returned with error code -1

Error occurred: Could not connect to the target device.
For troubleshooting steps visit: https://kb.segger.com/J-Link_Troubleshooting

先说这次的日志和前两帖相比质变了——前两帖还能通信、寄存器能读出来,这次是直接 MDM-AP 都访问不到,调试器在芯片门口就被挡住了。

逐条解读:

  1. Communication error while accessing MDM-AP —— S32K1 系列的 SWD 调试协议通过 MDM-AP(Memory Debug Access Port)握手,访问这个 AP 是调试通信的第一步。MDM-AP 访问失败 = 芯片完全没在 SWD 总线上应答,要么芯片死锁、要么物理链路不通、要么调试口时序错乱。

  2. Connect Under Reset 两次都失败 —— J-Link 已经尝试在复位状态下连接,避开运行代码的干扰,仍然失败。说明问题不是"程序跑飞导致调试器失去控制",是芯片和调试器之间物理/协议层根本不通

  3. RESET 对地 0V —— 这次和 411 帖的 1V 不一样。1V 是分压异常,0V 是 RESET 被外部电路拉到了地。你原理图里 TP65 NTRST 走的是 R86 100Ω + C76 0.22μF + R85 4.7k 上拉到 D3V3_MCU 的复位路径。J-Link 在 Connect Under Reset 时会把 NTRST 拉低,如果你板子的 NTRST 和 RESET 在 PCB 上是连到同一个点(或者芯片内部有 NTRST→RESET 路径),那 RESET 现在被拉低就说得通。

  4. J-Link LPCXpresso V2 —— 注意你用的不是标准 J-Link,是 LPCXpresso 板载的 V2 固件。LPCXpresso 对 NXP 自己芯片的兼容性最好,但 S32K144 不在它的"原生支持"列表里,调试脚本可能不完整。

建议排查顺序:

  1. 拔掉调试器 USB,单独给板子上电,量 RESET 电压(应该是 3.3V,不是 0V)。如果还是 0V,看复位按钮 / R86 / C76 那一带

  2. 量 SWDIO/SWCLK 走线到 MCU 引脚的通断(特别是 ESD 二极管 D11-D15 有没有焊反——JEB240P0603 反焊会直接短路)

  3. 用 J-Link Commander 降到 100kHz 试

  4. unlock Kinetis + mass erase(如果还能进 connect)