BakeSheep
Community@BakeSheep
BakeSheep provides EmberProbe-based embedded skills for STM32 Cortex-M firmware flashing, debugging, fault diagnosis, and memory analysis.
Agent Skills by BakeSheep
Showing 9 vetted skills indexed across 1 GitHub repositories.
BakeSheepmcu-cubemx
Modifies STM32 .ioc configurations and regenerates initialization code via STM32CubeMX on Windows.
BakeSheepmcu-flash
Program or verify MCU firmware against workspace ELF files through OpenOCD.
BakeSheepmcu-debug-control
Controls Cortex-Debug sessions and manages source-line or function breakpoints in VS Code.
BakeSheepmcu-fault-analyzer
Decode Cortex-M fault registers and symbolize PC/LR against the ELF.
BakeSheepmcu-chip-info
Reads MCU identity, debug-link, and runtime information from connected Cortex-M targets via OpenOCD.
BakeSheepmcu-elf-analyze
Analyzes firmware ELF files to report Flash and RAM usage per section plus largest symbols.
BakeSheepmcu-variables
Read, trend, export, and write Cortex-M MCU variables resolved from ELF and DWARF data.
BakeSheepmcu-peripheral-debug
Inspect and modify MCU peripheral registers and bit fields from workspace SVD files.
BakeSheepmcu-config
Read and update EmberProbe workspace configuration for ELF, debugger, MCU, SVD, and sampling settings.
Frequently Asked Questions About BakeSheep
FAQPage SchemaWhat tasks can I perform with BakeSheep's MCU skills?▼
You can flash and verify firmware via OpenOCD, control Cortex-Debug sessions with breakpoints, decode Cortex-M fault registers, analyze ELF Flash/RAM usage, read and tune live variables, inspect SVD peripheral registers, query chip identity, and regenerate STM32CubeMX initialization code.
Who are these EmberProbe MCU skills designed for?▼
Embedded firmware engineers working on STM32 Cortex-M projects who need in-workspace debugging, fault diagnosis, memory footprint reporting, and peripheral register inspection without leaving their EmberProbe environment.
What hardware or setup is required to use these skills?▼
Most skills require an attached debug probe and a configured EmberProbe workspace with ELF, SVD, and probe settings. Peripheral register access needs a paused Cortex-Debug session, while ELF memory analysis runs statically with no hardware connected.
Can these skills detect non-genuine STM32 chips?▼
Yes. The mcu-chip-info skill reads the connected chip's identity, UID, flash size, and vendor fingerprint, distinguishing genuine ST parts from compatible clones such as APM32, GD32, and AT32, along with debugger, transport, and voltage details.
How do I track firmware variables over time?▼
The mcu-variables skill resolves variables from ELF and DWARF data to read live values, structs, and arrays, monitor runtime trends, export CSV history, and start or stop shared sidebar sampling, with explicit support for requested variable tuning.