All authors
Claude Skills by nxp-agentic-ai
github.com/nxp-agentic-ai122 skills0 installs126 views
- S32debugger Debug From FlashExecute the S32Debugger workflow that programs an image and then continues debugging from flash in the same GDB session. Use this whenever the user wants to flash an ELF or image and keep the session alive for symbolic debug afterward, continue in the same GDB session after programming, or apply the post-flash reset/register-cache/PC/symbol sequence instead of ending the flow with `fl_close`.Votes: 0GitHub stars: 5
- S32debugger Discover InstallationResolve the correct S32Debugger installation root for MCP use. Use this whenever the user wants to find S32Debugger on disk, set or confirm the installation path, gives a path under `S32Debugger` or `S32DS/tools`, mentions an NXP install under `C:/NXP`, or needs the path normalized before template lookup, config generation, standalone debug startup, or CCS sanity-check execution.Votes: 0GitHub stars: 5
- S32debugger Error ResolutionDiagnose standalone S32Debugger startup, bridge, probe, CCS, symbol, and live-session failures and turn vague debugger problems into a concrete recovery plan. Use this whenever a startup/connect/load/breakpoint flow fails, when the user pastes an error snippet or transcript, when an interactive session opens but does not behave correctly, or even when the user only says "it doesn't work" and the failing workflow stage still needs to be identified. Distinguish lower-layer probe and target-visi...Votes: 0GitHub stars: 5
- S32debugger Flash Only OperationsExecute S32Debugger flash-programmer operations that end after the flash action completes. Use this whenever the user wants to flash, program, write, erase, verify, dump, read, or inspect flash contents without continuing into debug-from-flash in the same GDB session, and when the flash session must be closed correctly with `fl_close`.Votes: 0GitHub stars: 5
- S32debugger Flash ProgrammingRoute S32Debugger flash requests to the correct specialized workflow. Use this whenever the user wants to flash, program, write, erase, verify, dump, or inspect flash contents, or wants to program an image and then continue debugging from flash in the same session, even if the user does not explicitly ask to choose between flash-only and debug-from-flash behavior.Votes: 0GitHub stars: 5
- S32debugger Generate Automation ScriptGenerate standalone S32Debugger automation scripts from grounded existing flows rather than inventing them from scratch. Use this whenever the user wants a new automation script or script set for standalone S32Debugger, such as Python, shell launch wrappers (`.sh` on Linux, `.bat`/`.cmd` on Windows), in-GDB Python, launch wrappers, data-collection helpers, or mixed deliverables that automate config generation, GTA/GDB startup, ELF load, breakpoints, repeated capture, and report/log creation. ...Votes: 0GitHub stars: 5
- S32debugger Generate Gdb Config FileGenerate a real S32Debugger GDB config `.txt` artifact from an S32Debugger Python example template by using the dedicated MCP tool. Use this whenever the user wants a base config file before later startup, asks to generate a config from a `SingleCore`, `MultiCore`, or `FlashProgrammer` example, provides `soc_family` / `script_type` / `template_name` plus probe/core/ELF overrides, or needs a config artifact that will later be passed into `control.start_gdb` or a standalone live-debug flow.Votes: 0GitHub stars: 5
- S32debugger Lookup For Soc Init SequenceIdentify, inspect, explain, and family-consistently adapt S32Debugger SoC init sequences by starting from the existing family generic and init scripts and preserving dispatcher compatibility. Use this whenever the user asks which init sequence a family uses, wants the bring-up path explained, needs the real helper or dispatcher entry point, or wants an existing family init sequence adapted for a derivative, core, or mode.Votes: 0GitHub stars: 5
- S32debugger Navigate InstallationNavigate a known S32Debugger installation root to find the right examples, scripts, templates, and config-generation inputs. Use this whenever the installation root is already known and the user wants to locate a `SingleCore`, `MultiCore`, or `FlashProgrammer` example, find an internal debugger script, choose between `S32Debugger/Examples` and `S32Debugger/Debugger/scripts`, or identify the best matching file by `soc_family`, `script_type`, or `core_name`.Votes: 0GitHub stars: 5
- S32debugger Resolve Core Name From ContextResolve the authoritative `_CORE_NAME`, `_SOC_NAME`, and related family-context values from `<family>_context.py`. Use this whenever an S32Debugger flow needs exact family-script values before init-sequence execution, config generation, core-sensitive tool parameters, or validation of derivative-specific startup behavior, especially when the user only knows the SoC or family and the flow must not guess or construct `_CORE_NAME` manually.Votes: 0GitHub stars: 5
- S32debugger Resolve Gdb VariantResolve the correct S32Debugger GDB variant from a target core or core instance. Use this whenever a flow needs to choose between `arm32` and `arm64` before starting GTA/GDB, generating or validating a config, checking a single-core or multicore startup path, adapting an existing debugger flow, or normalizing an explicit core instance such as `M7_0` or `A53_0_0` without losing the original instance identity.Votes: 0GitHub stars: 5
- S32debugger Start Multicore Standalone Live Debug SessionExecute the dedicated standalone S32Debugger multicore live-debug workflow. Use this whenever the user wants a multicore standalone session, names multiple cores or GDB clients, needs boot-core-first startup, wants separate bridge/control per core, or wants a multicore session kept open for follow-up commands after startup and per-client validation.Votes: 0GitHub stars: 5
- S32debugger Start Singlecore Standalone Live Debug SessionExecute the dedicated standalone S32Debugger live-debug workflow for one explicit core instance. Use this whenever the user wants a single-core standalone debug session, names one core such as `M7_0` or `A53_0_0`, wants to load one ELF, asks for an interactive or keep-open session, or wants breakpoint validation and follow-up control for exactly one target core.Votes: 0GitHub stars: 5
- S32debugger Start Standalone Live SessionRoute standalone S32Debugger requests to the best matching workflow. Use this whenever the user mentions standalone S32Debugger, a live or interactive standalone debug session, keeping a standalone session open for follow-up commands, multicore standalone debug, flash programming, or flash-then-debug behavior, even if the user does not explicitly ask for routing.Votes: 0GitHub stars: 5
- S32ds Analyze ProjectComprehensive read-only analysis of an S32DS project. Lists workspace projects, retrieves project info (build configs and MCU/core/target), finds the installed SDKs that match the target, reports build problems, and lists debug/launch configurations to map structure, toolchain, and debug capability. Use this whenever the user asks "what is this project?", needs to understand an unfamiliar S32DS project, wants to know the target MCU/SDK/toolchain, is diagnosing why a project behaves unexpected...Votes: 0GitHub stars: 5
- S32ds Build And DebugFull build-and-debug workflow for S32DS projects. Checks whether the project contains .mex files (requiring code regeneration), selects the project, triggers either 'Update Code and Build' or a plain incremental build, waits for jobs to finish, verifies zero build errors, then launches a debug session via S32 Debug Probe. Covers the complete path from source code to halted-at-main on target hardware.Votes: 0GitHub stars: 5
- S32ds Check Sdk CompatibilityVerify that a project's attached SDK is compatible with its target MCU. Retrieves the project's SDK descriptors, lists all installed SDKs, compares version/platform/device information, and checks that required peripherals and drivers are available for the specific target device. Useful when importing projects from other machines or upgrading SDK versions.Votes: 0GitHub stars: 5
- S32ds Clean And RebuildClean all build artifacts and perform a full rebuild from scratch. Triggers project clean, waits for the clean job to finish, then starts an incremental build and waits for completion. Finally verifies that no errors remain. Use when incremental builds produce stale-object errors or inconsistent state.Votes: 0GitHub stars: 5
- S32ds Configure PreferencesBrowse and open S32DS IDE preference/settings pages. Lists all available preference pages with their IDs, then opens a specific page by ID so the user can adjust IDE settings (compiler paths, code style, debugger options, etc.). Useful when the user needs to change toolchain settings or IDE behavior.Votes: 0GitHub stars: 5
- S32ds Create Project From ScratchCreate a new S32DS project from scratch - either fully headless via the New Project Wizard backend (createProject + listNpwOptions, no GUI interaction needed) or from an NXP example/Application Code Hub template. Discovers valid processors, toolchains, debuggers, cores and SDKs, then creates a ready-to-build workspace entry. Use this skill whenever the user wants to start, create, scaffold, or bootstrap a new S32DS/S32K/S32G/S32Z project, begin development for a specific MCU, generate a blank...Votes: 0GitHub stars: 5
- S32ds Find DocumentationSearch the indexed documentation corpus for information about MCU features, peripherals, configuration procedures, register maps, and S32DS usage. Supports both semantic (natural language) and keyword/regex search across 'lite' (general) and 'driver' (peripheral-specific) corpora. Can also retrieve full document pages for deep reading. Use this whenever you need reference information from NXP docs.Votes: 0GitHub stars: 5
- S32ds Fix Build ErrorsSystematically diagnose and resolve build errors. Retrieves all errors from the Problems view, categorizes them (compiler errors, linker errors, configuration issues, missing generated code), reads the offending source files for context, applies targeted fixes, and rebuilds iteratively until zero errors remain. Includes an error catalog mapping common error patterns to root causes and solutions.Votes: 0GitHub stars: 5
- S32ds Flash TargetProgram the target MCU's flash memory via S32 Debug Probe and verify success. Confirms the project is built without errors, locates the debug/launch configuration, launches the debug session (which internally programs flash), waits for completion, and verifies the target is halted at the entry point using GDB. Supports both 'flash and debug' and 'flash only (disconnect after programming)' patterns.Votes: 0GitHub stars: 5
- S32ds Import Ach ProjectImport a project from NXP's Application Code Hub (ACH) into the S32DS workspace. Covers browsing available ACH projects, filtering by keyword, cloning the repository, and setting up the project for building. This is the primary flow for getting started with NXP reference applications and demos.Votes: 0GitHub stars: 5
- S32ds Mi Debug CommandsGuide for using execute_action(action_name="runMiDebugCommand", ...) to execute raw GDB Machine Interface (MI) and CLI commands on active debug sessions. Covers when to use MI commands vs the dedicated Debugger MCP server, available MI command categories (breakpoints, execution, memory, registers, stack, variables), S32Debugger-specific commands, and error handling. The Debugger MCP server should be the primary tool - MI commands are the fallback for S32Debugger launches or when the debugger ...Votes: 0GitHub stars: 5
- S32ds Multicore DebugDebug multicore S32 MCUs (S32K3, S32G, S32E/S32Z, S32R) with multiple cores running simultaneously. Covers GDB thread-per-core model, attaching to specific cores, setting per-core breakpoints, synchronized halt/resume, cross-core memory inspection, and inter-core communication debugging (shared memory, hardware semaphores). Includes decision tree for core selection and error catalog for common multicore issues (core not halting, thread ID mismatch, XRDC faults).Votes: 0GitHub stars: 5
- S32ds Open Extensions And UpdatesOpen the S32DS Extensions and Updates dialog to install, update, or manage IDE components, SDKs, and plugins. Executes the specific command ID that launches the modular installer UI. Use when the user needs to add new SDK packages, update existing components, or check for available extensions.Votes: 0GitHub stars: 5
- S32ds Open S32ctOpen S32 Configuration Tools perspectives (Pins, Clocks, Peripherals, DCD, DDR, eFUSE, GTM, ICE, IVT, QuadSPI, SERDES) in the S32DS IDE. Each configuration tool has a dedicated Eclipse perspective ID. Use this skill to switch to the appropriate perspective when the user needs to configure MCU peripherals, pin muxing, clock trees, or other hardware settings visually.Votes: 0GitHub stars: 5
- S32ds Resolve Rtd Addon CompatibilityResolve RTD and add-on (TCPIP, Crypto, etc.) version compatibility by directing users to the NXP Automotive Software Package Manager website (web only - S32DS does NOT have a built-in Package Manager). Bundles group mutually compatible components that are regression-tested together. Use when users ask which middleware versions work with their RTD. This skill must be applied whenever compatibility is requested, even if the model believes it knows the answer.Votes: 0GitHub stars: 5
- S32ds Safe Code RegenSafely regenerate driver code from .mex configuration files and build the project in one atomic operation. This is the ONLY correct way to build projects that use S32 Configuration Tools. Selects the project, triggers 'Update Code and Build' (which regenerates all driver code from .mex files then compiles), waits for both code generation and build jobs, and verifies results. Prevents stale/missing generated code errors that occur when using plain build on .mex projects.Votes: 0GitHub stars: 5
- S32ds Search Peripheral DocsFind driver-level documentation for specific peripherals (LPSPI, LINFlexD, FlexCAN, eMIOS, ADC, etc.). Searches the 'driver' corpus for initialization sequences, API function references, register-level details, configuration examples, and usage patterns. Use this when you need to understand how to configure or use a specific peripheral driver in code.Votes: 0GitHub stars: 5
- S32ds Setup Debug ConfigFind, verify, and prepare debug/launch configurations for a project. Lists all existing debug launch configurations, filters by project name, verifies the project builds successfully, checks SDK and project info for probe compatibility, and identifies the correct configuration to use. Prerequisite step before launching any debug or flash session.Votes: 0GitHub stars: 5
- S32ds Workspace Health CheckPerform a comprehensive health check of the entire S32DS workspace. Lists all projects, retrieves global problems (errors/warnings across all projects), performs per-project analysis (build state, SDK attachments, .mex presence), verifies SDK compatibility, and generates a summary health report. Use this for an overview of workspace state or to diagnose systemic issues affecting multiple projects.Votes: 0GitHub stars: 5
- S32flashtool Agent Rules MinimalMinimal shared rules that apply across all S32FlashTool workflows.Votes: 0GitHub stars: 5
- S32flashtool Basic UseHuman-oriented onboarding and baseline workflow for installing, inspecting, and safely beginning to use S32FlashTool. For agentic routing, prefer s32flashtool-workflow-index.Votes: 0GitHub stars: 5
- S32flashtool Compute Crc And Compare To FlashCompute CRC on a binary file and compare it against the corresponding flash memory region on an NXP S32 device using S32FlashTool.Votes: 0GitHub stars: 5
- S32flashtool Discover Hardware SetupUse this skill to discover the likely S32FlashTool hardware setup for a connected target - interface, candidate port, target binary, flash algorithm, and the safest next identification step, without guessing missing hardware details.Votes: 0GitHub stars: 5
- S32flashtool Erase FlashErase a range of supported flash memory on an NXP S32 device using either S32FlashTool CLI or S32FlashTool GUI via RPC.Votes: 0GitHub stars: 5
- S32flashtool Evidence Disciplined Technical ValidationUse for technical investigations where documentation, static analysis, inferred context, package contents, or example assets must not be confused with live verification.Votes: 0GitHub stars: 5
- S32flashtool Get Flash IdRead the flash memory identification from a supported NXP S32 device using either S32FlashTool CLI or S32FlashTool GUI via RPC.Votes: 0GitHub stars: 5
- S32flashtool Get VersionSafely retrieve the version or identification string of the installed S32FlashTool and of the MCP server.Votes: 0GitHub stars: 5
- S32flashtool Identify User BoardIdentify an S32 Flash Tool user board by exact name, partial name, image, or other hardware clues, and route to the correct support-details workflow.Votes: 0GitHub stars: 5
- S32flashtool List Available Serial Communication InterfacesEnumerate available UART/CAN/Ethernet ports that S32FlashTool command-line application (CLI) can use for communication.Votes: 0GitHub stars: 5
- S32flashtool Read Command Line ArgumentsRetrieve the command line arguments exposed by an installed S32FlashTool command-line application (CLI) and use them as the version-specific source of truth.Votes: 0GitHub stars: 5
- S32flashtool Read FlashRead a region of flash memory from a supported NXP S32 device using either S32FlashTool CLI or S32FlashTool GUI via RPC.Votes: 0GitHub stars: 5
- S32flashtool Read McuidRead the MCU identification from a supported NXP S32 device using S32FlashTool command-line application (CLI) over a supported communication interface.Votes: 0GitHub stars: 5
- S32flashtool Read RconRead the RCON/EEPROM region from a supported NXP S32 device using either S32FlashTool CLI or S32FlashTool GUI via RPC.Votes: 0GitHub stars: 5
- S32flashtool Rest ApiOperate the S32FlashTool GUI through its REST API using documented session, model, and action patterns.Votes: 0GitHub stars: 5
- S32flashtool Rpc ApiOperate the S32FlashTool GUI through its RPC API using documented session, model, and action patterns.Votes: 0GitHub stars: 5
- S32flashtool SramLoad a binary into SRAM and execute it on a supported NXP S32 device using either S32FlashTool CLI or S32FlashTool GUI via RPC.Votes: 0GitHub stars: 5