Building Keil MDK Projects

Applicable Scenarios

```
build_system: keil
```
is specified in the
```
Project Profile
```
, or
```
.uvprojx
```
/
```
.uvproj
```
files exist in the workspace.
Users want to compile, recompile, or confirm firmware artifacts for Keil MDK projects.
New
```
AXF
```
(ELF),
```
HEX
```
, or
```
BIN
```
files are required for programming or debugging processes.
Need to verify if the Keil MDK environment is ready before compilation (UV4.exe, ARMCC/ARMCLANG).

Required Inputs

Workspace path, path to
```
.uvprojx
```
/
```
.uvproj
```
project file, or an existing
```
Project Profile
```
.
Optional build target name, UV4.exe path, and log output path.

Auto-Detection

The script automatically searches common Keil MDK installation paths and environment variables (
```
KEIL_ROOT
```
,
```
MDK_ROOT
```
) to locate UV4.exe.
Parses the Target list in
```
.uvprojx
```
project files, extracts chip model, output directory, and toolchain (ARMCC/ARMCLANG).
If no target is specified, the first Target in the project is used by default.
Searches for AXF, HEX, BIN artifacts in the output directory, sorted by
```
ELF > HEX > BIN
```
.
If multiple equally valid project files or targets exist, lists candidates instead of making silent guesses.

Execution Steps

First read references/usage.md to confirm whether this is environment detection, project scanning, target listing, or compilation execution.
For common scenarios with a single project and single target, prioritize completing detection + compilation in one call:
bash
```
python scripts/keil_builder.py --detect --project <project file> --target <target name>
```
This starts only one Python process, avoiding the overhead of three serial calls:
```
--detect
```
→
```
--list-targets
```
→
```
--build
```
.
Only execute
```
--scan
```
and
```
--list-targets
```
step-by-step when interactive selection is required (multiple project files or targets need user confirmation).
Read the build results and artifact scan report output by the script, focusing on preferred artifacts (AXF/ELF > HEX > BIN), error/warning statistics, and failure classification.
Write the build target, artifact path, chip model, and toolchain information back to the
```
Project Profile
```
, and pass it to downstream skills when needed.

Failure Diversion

Returns
```
environment-missing
```
when Keil MDK is not installed or UV4.exe is unavailable.
Returns
```
project-config-error
```
when the project file is corrupted, the target name is invalid, or compilation fails due to configuration issues.
Returns
```
artifact-missing
```
when compilation appears successful but no programmable or debuggable artifacts are found.
Returns
```
ambiguous-context
```
when multiple equally valid project files or targets exist and arbitrary selection is unsafe.

Platform Notes

Keil MDK runs natively only on Windows; UV4.exe command-line compilation requires a Windows environment.
The built-in scripts can still execute project parsing (
```
--list-targets
```
), project scanning (
```
--scan
```
), and artifact scanning (
```
--scan-artifacts
```
) on non-Windows platforms, but actual compilation will be blocked.
Compilation logs may contain Chinese characters in GBK encoding; the script will automatically try multiple encodings.
Artifact paths in the output should remain absolute paths for direct reuse by downstream programming and debugging skills.

Output Conventions

After script execution, the following key information must be extracted and presented to the user:

Compilation status (success/failure)
Project file and target name
Chip model and toolchain (e.g., STM32F103RC [ARMCC])
Firmware size details (Code, RO-data, RW-data, ZI-data) and Flash/RAM summary
Compilation time
Artifact list (AXF/HEX/BIN and file sizes)
Error/warning statistics
If failed: failure classification and log evidence

Sample output format:

Build Successful ✅
  Project: Demo02.uvprojx → Target: Demo02
  Chip: STM32F103RC | Toolchain: ARMCC
  Firmware Size: Flash ≈ 3.2 KB  RAM ≈ 1.6 KB
  Artifacts: Demo02.axf (518.9 KB), Demo02.hex (9.0 KB)
  Compilation Time: 00:00:05

Update the

Project Profile

with

artifact_path

artifact_kind

target_mcu

, and

toolchain

After success, recommend

flash-keil

flash-openocd

, or

debug-gdb-openocd

Handover Relationships

When the next step is to program hardware, pass the successful build result to
```
flash-keil
```
(using Keil's built-in debugger) or
```
flash-openocd
```
(using OpenOCD).
When symbol information or a debugging session is needed next, pass the successful build result to
```
debug-gdb-openocd
```
.

build-keil

NPX Install

Tags

SKILL.md Content (Chinese)

Building Keil MDK Projects

Applicable Scenarios

Required Inputs

Auto-Detection

Execution Steps

Failure Diversion

Platform Notes

Output Conventions

Handover Relationships