What problem does it solve? When debugging embedded firmware, you often need quick answers about the connected chip—its core, series, UID, flash size, debugger transport, voltage, or CPU state—without manually launching OpenOCD or writing probe scripts. This Skill reads exactly the MCU fields you ask for through the EmberProbe bridge, including a vendor fingerprint that distinguishes genuine ST chips from compatible clones like APM32, GD32, or AT32. ## Core Features & Use Cases - Selective field reading: Request grouped sections (identity, debug, runtime) or individual fields such as core, series, deviceId, flashSize, voltage, or CPU registers, so you only fetch what the question needs. - Vendor authenticity detection: Decodes the CoreSight ROM table to report the JEP106 designer and an authenticity verdict (genuine vs compatible clone with vendor/brand names). - Structured failure diagnostics: On error, returns JSON with error.code, likelyCause, suggestedActions, and the OpenOCD log tail for precise troubleshooting. - Use Case: A user asks "Is this board a real STM32 or a GD32 clone, and how much flash does it have?" The agent runs the read script with the relevant fields and returns the authenticity verdict and flash size in one step. ## Quick Start Ask the agent to read the connected chip's identity information, for example: "Tell me the core, series, UID, and flash size of the MCU currently attached to my debug probe."
