# Stm32cubemx

> Use when Codex needs to operate STM32CubeMX from the command line to validate or load .ioc files, generate STM32CubeMX projects, create Keil/MDK-ARM project files, run Keil UV4 command-line builds, inspect CubeMX/Keil logs, or diagnose STM32CubeMX generation and STM32 HAL project build failures.

- **Type:** Skill
- **Install:** `agentstack add skill-54xkeee-agent-diansai-skill-stm32cubemx`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [54xkeee](https://agentstack.voostack.com/s/54xkeee)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [54xkeee](https://github.com/54xkeee)
- **Source:** https://github.com/54xkeee/agent-diansai-skill/tree/main/skills/stm32cubemx

## Install

```sh
agentstack add skill-54xkeee-agent-diansai-skill-stm32cubemx
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# STM32CubeMX

Use this skill to turn `.ioc` validation into an actual STM32CubeMX and Keil build check, not just text parsing.

## Workflow

1. Start with an existing `.ioc` file. If the user only has a desired STM32 configuration, first create or obtain the `.ioc` using the relevant STM32 configuration skill or local tooling.
2. Prefer the bundled script:

```powershell
python "$env:USERPROFILE\.codex\skills\stm32cubemx\scripts\cubemx_generate_build.py" --ioc "D:\path\project.ioc" --build-keil --clean-keil-output
```

3. If CubeMX or Keil is not found, rerun with explicit paths:

```powershell
python "$env:USERPROFILE\.codex\skills\stm32cubemx\scripts\cubemx_generate_build.py" --ioc "D:\path\project.ioc" --cubemx "D:\STM32CubeMX" --uv4 "C:\Keil_v5\UV4\UV4.exe" --build-keil
```

4. Report the generated project directory, CubeMX log, Keil log, and whether the build produced `0 Error(s), 0 Warning(s)`.

## CubeMX Command Mode

Use STM32CubeMX quiet script mode for real validation:

```text
config load ""
project name 
project toolchain "MDK-ARM"
project path ""
project generate
exit
```

Run it on Windows as:

```powershell
& "\jre\bin\java.exe" -jar "\STM32CubeMX.exe" -q ""
```

Treat `config load` followed by `OK`, `project generate` followed by `OK`, and generated `Core/Src/main.c` as the baseline CubeMX success criteria.

## Keil Build Mode

Use `UV4.exe -b  -j0 -o ` for build verification. In this environment ARMCC V5 builds the CubeMX project reliably with Keil's default parallel setting.

Set `TEMP` and `TMP` to a writable folder before running Keil. ARMCC can fail with `cannot open embedded assembler output file "C:\WINDOWS\TEMP\..."` when the process cannot write to the default temp directory. This is an environment problem, not an `.ioc` problem.

The bundled script handles this by creating a local `keil_temp` folder and overriding `TEMP/TMP` for the build subprocess.

## Diagnosis Rules

- If CubeMX cannot load the `.ioc`, inspect the CubeMX log around `config load` first.
- If CubeMX loads but cannot generate, inspect the log around `project generate`.
- If Keil fails before compiling user files and mentions `C:\WINDOWS\TEMP`, rerun with a writable temp directory.
- If Keil reports `I/O error writing file ... .o`, retry with `--jobs 0 --clean-keil-output` and a writable local `TEMP/TMP`.
- If Keil compiles but links fail because object files are missing, read earlier compile errors; the link error is usually downstream.
- Ignore CubeMX update, advertisement image, and SQLite temp cleanup warnings unless they occur before `config load` or block `project generate`.
- Do not claim the firmware is hardware-tested unless flashing and board-level runtime checks were actually performed.

## Outputs

Keep validation artifacts near the `.ioc` unless the user requests a different destination:

```text
/cubemx_project//
/cubemx_verify_script.txt
/cubemx_generate.log
/keil_build.log
```

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [54xkeee](https://github.com/54xkeee)
- **Source:** [54xkeee/agent-diansai-skill](https://github.com/54xkeee/agent-diansai-skill)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** yes
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-54xkeee-agent-diansai-skill-stm32cubemx
- Seller: https://agentstack.voostack.com/s/54xkeee
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.