J-Link Firmware Flashing

Applicable Scenarios

A usable firmware artifact exists in the workspace, and the target board is connected to a SEGGER J-Link probe.
Need to use J-Link Commander for flashing and verification instead of OpenOCD.
Need to use J-Link RTT (Real-Time Transfer) for high-speed log capture.
Need to scan
```
.jlink
```
configuration files in the workspace or J-Link settings in
```
.vscode/launch.json
```
.

Firmware artifact path, or a
```
Project Profile
```
containing
```
artifact_path
```
.
The
```
--device
```
parameter to specify the target chip model (e.g.,
```
STM32F407VG
```
), which is required by J-Link Commander.
Optional interface type (SWD or JTAG, default is SWD) and flashing speed.
If the artifact is a BIN file, the
```
--base-address
```
flashing base address is also required.

Select firmware artifacts in the order of
```
ELF > HEX > BIN
```
.
The script automatically searches for JLinkExe in the order of configuration files, PATH, and common installation paths.
```
--scan-configs
```
scans J-Link configurations in workspace
```
.jlink
```
files and
```
.vscode/launch.json
```
.
Does not guess device names; blocks and returns
```
ambiguous-context
```
when
```
--device
```
is missing.

First read references/usage.md to confirm whether this is environment detection, configuration scanning, or flashing execution.
If unsure about the J-Link environment status, first run the built-in script scripts/jlink_flasher.py in
```
--detect
```
mode to confirm.
If unsure about the device model or interface configuration, use
```
--scan-configs
```
to scan for clues in the workspace.
Use
```
--artifact
```
+
```
--device
```
to execute flashing, with optional
```
--interface
```
and
```
--speed
```
.
For BIN files,
```
--base-address
```
must be provided at the same time.
When RTT logs are needed, use
```
--rtt
```
to start RTT capture.
Read the flashing result report output by the script, focusing on verification status and failure categories.

Returns
```
environment-missing
```
when JLinkExe is unavailable.
Returns
```
artifact-missing
```
when the artifact cannot be safely resolved or the BIN file lacks a flashing base address.
Returns
```
connection-failure
```
when J-Link cannot detect the probe or target.
Returns
```
project-config-error
```
when the configuration file is invalid or the device name is not recognized by J-Link.
Returns
```
target-response-abnormal
```
when flashing starts but verification or reset fails.
Returns
```
ambiguous-context
```
when
```
--device
```
is missing and cannot be inferred from the workspace.

JLinkExe is
```
JLinkExe
```
on Linux/macOS, and
```
JLink.exe
```
on Windows.
Default SEGGER installation paths:
```
/opt/SEGGER/JLink/
```
for Linux,
```
C:\Program Files\SEGGER\JLink\
```
for Windows.
The built-in script uses Python standard libraries and subprocess to call JLinkExe, which is cross-platform compatible.
The RTT function is exclusive to J-Link, does not occupy UART, and is suitable for scenarios without a serial port.

Outputs JLinkExe command, device name, interface type, artifact path, and verification result.

Retains or updates

artifact_path

artifact_kind

jlink_device

jlink_interface

in the

Project Profile

When needing to view runtime logs next, pass the successful flashing result to
```
serial-monitor
```
.
When the user needs GDB debugging, pass the result to
```
debug-jlink
```
.
When RTT logs are needed instead of serial ports, the
```
--rtt
```
mode of this skill can be used directly.