Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

jlink-download

Use J-Link debugger to flash firmware (.bin or .hex) to ARM Cortex-M microcontrollers, supporting GD32/STM32 and other chips. Trigger scenarios: (1) Flash firmware to microcontroller, (2) User mentions "flash", "burn", "download firmware", "download", (3) Need to write compiled .bin or .hex file to chip, (4) Program target board via J-Link. Even if user just says "flash it" or "burn the chip", this skill should be used.

In Manus ausführen

Überblick

Installationsbefehl

npx skills add https://github.com/changde-tang/embedded-skills --skill jlink-download

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um den Skill zu installieren

Quelle

changde-tang/embedded-skills

Sterne6

Forks0

Aktualisiert18. April 2026 um 06:55

Datei-Explorer

2 Dateien

SKILL.md

readonly

name

jlink-download

description

J-Link Firmware Flashing

Invoke py_jlink_download.py to flash firmware files to target chips via J-Link debugger, supporting full process of erase, flash, verify, and reset.

Tool Script

Script Path: py_jlink_download.py Dependencies: Python 3.x + pylink library

pip install pylink

Usage

# Basic usage (default chip GD32F103C8)
python py_jlink_download.py firmware.bin

# Specify chip model
python py_jlink_download.py firmware.bin -d STM32F103C8

# Specify flash start address
python py_jlink_download.py firmware.bin -a 0x08001000

# Skip erase and verify (faster)
python py_jlink_download.py firmware.bin --no-erase --no-verify

Parameter Description

Parameter	Short	Description	Default
`firmware`	-	Firmware file path (.bin or .hex)	Required
`--device`	`-d`	Target chip model	`GD32F103C8`
`--addr`	`-a`	Flash start address	`0x08000000`
`--no-erase`	-	Skip chip erase before flashing	Default erase
`--no-verify`	-	Skip flash data verification	Default verify
`--no-run`	-	Do not reset and run after flash	Default reset

Flash Process

Initialize and connect J-Link
Connect to target chip (SWD interface)
Erase chip (optional)
Write firmware file
Read memory to verify data (optional)
Reset and run program (optional)

Common Chip Models

GD32F103C8 / GD32F303RC
STM32F103C8 / STM32F103RET6

If chip model is unknown, run JLinkDevices command to view the complete device list supported by J-Link.

Notes

Ensure J-Link debugger is connected to both computer and target board
Chip model must exactly match the name in J-Link database
For .hex file flashing, verification step errors can be ignored (hex format contains address information)

Mehr aus diesem Repository

gleiches Repository

arm-tools-chain

changde-tang/embedded-skills

ARM MCU development full-process orchestration skill. Must read this file first when performing any ARM/Keil/MDK/STM32/GD32 related development tasks to determine execution order and strategy. Applicable scenarios: using ARM toolchain, developing new features, adding logs, compiling and flashing, debugging and viewing logs, full-process development, etc. Keywords: Keil, MDK, ARM, STM32, GD32, uvprojx, compile, flash, RTT, log, development.

2026-04-226

keil-build

changde-tang/embedded-skills

Compile Keil MDK projects (.uvprojx) via command line using Keil UV4 compiler, supporting incremental build and full rebuild, and parse build results. Trigger scenarios: (1) Compile Keil/MDK ARM project, (2) User mentions "build", "compile", "construct" project, (3) Need to check if project has build errors or warnings, (4) Need to compile before flashing firmware. Even if user just says "compile it for me" or "build this project", this skill should be used.

2026-04-226

agent-log-helper

changde-tang/embedded-skills

A guidance skill for integrating the agent_log logging system into Keil/MDK projects. Triggers: (1) User says "add agent_log", "add logging system", (2) User needs structured logging in Keil project, (3) User wants to add log output but doesn't know where to start, (4) User needs log initialization template or tick function implementation. Even if user just says "add log" or "use RTT logging", this skill should be used.

2026-04-186

jlink-rtt

changde-tang/embedded-skills

Read SEGGER RTT log output in real-time via J-Link debugger, supporting auto-scan of RTT control block addresses, applicable for debugging GD32/STM32 and other ARM Cortex-M microcontrollers. Trigger scenarios: (1) Read RTT debug logs from microcontroller, (2) User mentions "RTT", "view logs", "read serial" (RTT scenario), "real-time logs", (3) Need to view output information when debugging microcontroller programs, (4) Using features similar to SEGGER RTT Viewer. Even if user just says "see what the microcontroller prints" or "read RTT", this skill should be used.

2026-04-186

keil-uvprojx-modifier

changde-tang/embedded-skills

Use this skill to operate Keil MDK's .uvprojx project files. Applicable scenarios: list all Groups and files in project, add source files to specified Group (.c/.cpp/.s/.asm/.lib/.h etc.), remove files from project, create or delete Groups, manage include paths (add/remove/list). Use this skill when user mentions Keil, uvprojx, MDK project file management, or needs batch modification of Keil project structure.

2026-04-186

keil-parser

changde-tang/embedded-skills

Parse Keil MDK project files (.uvprojx), extract macro definitions, include paths, and source file lists. Trigger scenarios: (1) Need to read or analyze Keil project configuration, (2) Query project's macro definitions (defines), header file paths (include paths), source file list, (3) Need to understand project structure before compiling, flashing, etc., (4) User mentions .uvprojx file and wants to know its contents. Even if user just says "check project configuration" or "analyze this Keil project", this skill should be used.

2026-04-186

Quelle

changde-tang

changde-tang/embedded-skills

GitHub-Repository öffnen Creator-Repositorys ansehen

Installationsbefehl

Download

In Manus ausführen

Nützlich fürSOC

SoftwareentwicklerInformatik- und Mathematikberufe15-1252L4

name

jlink-download

description

J-Link Firmware Flashing

Invoke py_jlink_download.py to flash firmware files to target chips via J-Link debugger, supporting full process of erase, flash, verify, and reset.

Tool Script

Script Path: py_jlink_download.py Dependencies: Python 3.x + pylink library

pip install pylink

Usage

# Basic usage (default chip GD32F103C8)
python py_jlink_download.py firmware.bin

# Specify chip model
python py_jlink_download.py firmware.bin -d STM32F103C8

# Specify flash start address
python py_jlink_download.py firmware.bin -a 0x08001000

# Skip erase and verify (faster)
python py_jlink_download.py firmware.bin --no-erase --no-verify

Parameter Description

Parameter	Short	Description	Default
`firmware`	-	Firmware file path (.bin or .hex)	Required
`--device`	`-d`	Target chip model	`GD32F103C8`
`--addr`	`-a`	Flash start address	`0x08000000`
`--no-erase`	-	Skip chip erase before flashing	Default erase
`--no-verify`	-	Skip flash data verification	Default verify
`--no-run`	-	Do not reset and run after flash	Default reset

Flash Process

Initialize and connect J-Link
Connect to target chip (SWD interface)
Erase chip (optional)
Write firmware file
Read memory to verify data (optional)
Reset and run program (optional)

Common Chip Models

GD32F103C8 / GD32F303RC
STM32F103C8 / STM32F103RET6

If chip model is unknown, run JLinkDevices command to view the complete device list supported by J-Link.

Notes

Ensure J-Link debugger is connected to both computer and target board
Chip model must exactly match the name in J-Link database
For .hex file flashing, verification step errors can be ignored (hex format contains address information)