build-iar

Original：🇨🇳 Chinese

Translated

1 scriptsChecked / no sensitive code detected

Used when you need to compile embedded projects via the IAR Embedded Workbench command line, call built-in scripts to parse project files, execute builds, and locate firmware artifacts.

3installs

Sourceleokemp223/embed-ai-tool

Added on2026-05-16

NPX Install

npx skill4agent add leokemp223/embed-ai-tool build-iar

SKILL.md Content (Chinese)

View Translation Comparison →

Building IAR Embedded Workbench Projects

Applicable Scenarios

```
Project Profile
```
indicates
```
build_system: iar
```
or there are
```
.ewp
```
/
```
.eww
```
files in the workspace.
Users want to compile, recompile, or confirm firmware artifacts for IAR EWARM projects.
New
```
.out
```
(ELF),
```
HEX
```
, or
```
BIN
```
files are required for programming or debugging processes.
Need to confirm if the IAR environment is ready (iarbuild.exe, toolchain) before compilation.

Required Inputs

Workspace path or
```
.ewp
```
project file path, or an existing
```
Project Profile
```
.
Optional configuration name and IAR installation path.

Auto Detection

The script automatically searches common IAR installation paths and environment variables (
```
IAR_ROOT
```
,
```
EWARM_ROOT
```
) to locate iarbuild.exe.
Parses the configuration list in the
```
.ewp
```
project file to extract toolchain (ARM/RISCV), chip model, output directory, and output file name.
If no configuration is specified, the first configuration in the project is used by default.
Searches for .out (ELF), HEX, BIN artifacts in the output directory, sorted by
```
ELF > HEX > BIN
```
.
If multiple equally valid project files or configurations exist, lists candidates instead of making silent guesses.

Execution Steps

First read references/usage.md to confirm whether this is environment detection, project scanning, listing configurations, or executing compilation.
If unsure whether the environment is ready, first run the
```
--detect
```
mode of the built-in script scripts/iar_builder.py to confirm.
If unsure of the project file location, use
```
--scan
```
to search the workspace.
Use
```
--list-configs --project X.ewp
```
to confirm available configurations, then use
```
--project
```
+
```
--config
```
to execute compilation.
Read the build results and artifact scan report output by the script, focusing on the preferred artifacts (.out/ELF > HEX > BIN), error/warning statistics, and failure categories.
Write the build configuration, artifact path, chip model, and toolchain information back to
```
Project Profile
```
, and pass it to downstream skills when needed.

Failure Diversion

Returns
```
environment-missing
```
when IAR is not installed or iarbuild.exe is unavailable.
Returns
```
project-config-error
```
when the project file is corrupted, the configuration 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 configurations exist and any selection is unsafe.

Platform Notes

IAR Embedded Workbench runs natively only on Windows, and iarbuild.exe command-line compilation requires a Windows environment.
The built-in script can still perform project parsing (
```
--list-configs
```
), project scanning (
```
--scan
```
), and artifact scanning (
```
--scan-artifacts
```
) on non-Windows platforms, but actual compilation will be blocked.
Artifact paths in the output should remain absolute paths for direct reuse by downstream programming and debugging skills.

Output Conventions

Output compilation commands, project files, configuration names, chip models, toolchains, and preferred artifact paths.
Output error and warning statistics, as well as key compilation log evidence.

Update

Project Profile

with

artifact_path

,

artifact_kind

,

target_mcu

, and

toolchain

.

Recommend
```
flash-openocd
```
or
```
debug-gdb-openocd
```
after success.

Handover Relationships

When the next step is to program hardware, pass the successful build result to
```
flash-openocd
```
.
When the next step requires symbol information or a debugging session, pass the successful build result to
```
debug-gdb-openocd
```
.