mcu-config

Read and update EmberProbe workspace configuration for ELF, debugger, MCU, SVD, and sampling settings.

5|1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/BakeSheep/EmberProbe-MCU-Flash-Debug --skill mcu-config-bakesheep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mcu-config
Source: https://github.com/BakeSheep/EmberProbe-MCU-Flash-Debug/tree/main/skills/mcu-config
Command: npx skills add https://github.com/BakeSheep/EmberProbe-MCU-Flash-Debug --skill mcu-config-bakesheep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Embedded developers need to inspect and adjust EmberProbe workspace settings—such as the target ELF file, debug probe, MCU configuration, SVD file, and sampling parameters—without manually editing VS Code storage or risking invalid values. ## Core Features & Use Cases - Configuration Read: Retrieve the normalized workspace configuration including ELF, debugger, MCU, SVD, selected .ioc, sampling interval, Tcl port, and sample history limit. - Configuration Write: Change only explicitly requested keys via a validated --set interface that immediately synchronizes the EmberProbe sidebar. - IOC Selection: Select or clear a workspace CubeMX .ioc project file, with validation that the file exists inside the workspace. - Use Case: An agent needs to switch the debug probe and MCU target before flashing; it reads the current config, sets debugger=cmsis-dap.cfg,mcu=stm32f4x.cfg, and reports the normalized result returned by the extension. ## Quick Start Ask the agent to read the current EmberProbe workspace configuration and then set the debugger and MCU values you want changed.

Frequently Asked Questions about mcu-config

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change the MCU target and debugger in EmberProbe?▼

Run the config script with --set using comma-separated key=value pairs, for example debugger=cmsis-dap.cfg,mcu=stm32f4x.cfg. The extension validates the values and synchronizes the sidebar immediately, returning the normalized configuration.

How to select a CubeMX .ioc project file in the workspace?▼

Use --set "iocPath=path/to/project.ioc" to select an existing .ioc file inside the workspace, or --set "iocPath=" to clear it. Selection validates the file exists but does not edit its contents or verify CubeMX version.

Can I change the OpenOCD or CubeMX executable path through this skill?▼

No, openocdPath and cubemxPath are read-only through the Agent Bridge and return CONFIG_KEY_FORBIDDEN if set. Change executable paths in VS Code settings or the EmberProbe sidebar instead.

What configuration keys does the EmberProbe config script support?▼

Supported writable keys are elf, debugger, mcu, svd, iocPath, sampleIntervalMs, tclPort, and maxSamples. There is no writable firmwarePackage, firmwareVersion, or repository key; firmware package installation is handled through the sidebar.

Why does a config write fail with a validation error?▼

The extension validates paths, configuration names, and numeric ranges, rejecting invalid values. On failure, parse the stderr JSON diagnostic and report its error.code, likelyCause, and suggestedActions rather than guessing a hardware cause.