Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    fw analyzer

    1

    Binary-level firmware analyzer for crash resolution, stack depth estimation, and memory layout inspection.

    Free

    Security scanned
    fw analyzer

    fw analyzer

    Example session with this skill installed

    Analyze the crash at 0x080015AC in firmware.axf and show me the memory layout of the 'SystemConfig' struct.

    • Read your context and instructions
    • Compiled the fw analyzer

    I have analyzed the provided address and struct definition from firmware.axf. The crash address maps to an inlined function within the UART interrupt handler.

    Firmware Analysis Report

    Crash Address Resolution
    0x080015AC: drivers/uart.c:142
    └─ inlined from: include/buffer.h:22 (fifo_push)
    └─ inlined from: src/main.c:88 (UART_IRQ_Handler)

    Struct Layout: SystemConfig

    MemberTypeOffsetSizePadding
    device_iduint32_t0x040
    status_flagsuint8_t0x413
    buffer_ptrvoid*0x840
    modeuint16_t0xC22
    Total Size16 bytes

    Next steps

    1. Check drivers/uart.c at line 142 for potential null pointer dereferences in the fifo_push call.
    2. Review SystemConfig alignment; there are 5 bytes of padding that could be optimized by reordering members.
    3. Run --disasm UART_IRQ_Handler --mixed to see the exact instructions leading to the fault.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Embedded systems development often hits a wall when the source code says one thing, but the binary behaves differently. This skill provides a read-only firmware analyzer that inspects .axf and ELF files to reveal exactly what the compiler produced, how memory is allocated, and why a crash occurred at a specific address.

    What it does

    • Crash resolution maps raw PC/LR addresses to source lines and full inline chains.
    • Binary disassembly extracts machine code for specific functions with optional mixed source interleaving.
    • Memory profiling ranks the largest functions and data objects by Flash and RAM usage.
    • Struct inspection details the in-memory layout of C structs, including padding, bitfields, and member offsets.
    • Stack analysis estimates stack frame sizes and calculates the deepest call-chain depth from any entry point.
    • Dead code detection identifies static objects and functions that appear unreferenced in the linked binary.

    How it works

    1. Load image by providing the path to a built .axf or ELF file with DWARF debug info.
    2. Query facts using specific flags for addresses, symbols, or struct names to extract post-link data.
    3. Analyze stacks by specifying entry points to walk the call tree and accumulate frame sizes.
    4. Audit budgets by supplying an optional JSON manifest to compare modeled usage against allocated limits.

    Frameworks & tools

    Works with ELF32/ELF64 files generated by ARMCC, ARMClang, or GCC. It requires Python 3.10 and pyelftools, with optional capstone support for disassembly.

    Why this beats prompting it yourself

    Generic AI models cannot see inside your binary artifacts or understand DWARF debug information. This skill acts as a bridge, pulling hard facts from the linked output that source-level analysis would miss, such as compiler-inserted padding or actual stack usage.

    Use cases

    • Debugging HardFault exceptions by resolving register values to specific source lines.
    • Trimming firmware size by identifying large, unused, or redundant data objects.
    • Verifying ABI and FPU configurations to ensure the build matches hardware capabilities.
    • Estimating task stack requirements during RTOS integration or bare-metal development.

    Known limitations

    Does not support source-level semantics like macro expansion, include dependencies, or data flow. Requires DWARF debug info for high-level features like struct layout and stack analysis.

    Requires ELF/DWARF input. Cannot analyze source-only semantics like macros or cyclomatic complexity. Stack analysis is a model, not a guaranteed runtime peak.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 10 days ago

    • Free with an Agensi account

    Requires

    Python

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Environment Variables
    Listed10 days ago

    What's inside

    Frequently Asked Questions

    Binary-level firmware analyzer for crash resolution, stack depth estimation, and memory layout inspection.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use fw analyzer on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.