All authors
Claude Skills by nxp-agentic-ai
github.com/nxp-agentic-ai122 skills0 installs126 views
- Gcc Benchmark OptimizationCompare assembly output and final binary size across GCC optimization levels (-O0, -O1, -O2, -O3, -Os) for embedded ARM targets using S32Compiler GCC (10.2/11.4). Produces realistic size measurements using linked ELF binaries and explains performance vs size trade-offs. Use when the user asks "which optimization level should I use", "compare -O2 vs -Os", or "why is my binary too large".Votes: 0GitHub stars: 5
- Gcc Binary AnalysisAnalyze compiled ELF binaries produced by GCC (S32Compiler 10.2/11.4). Identifies code size contributors, section layout, and symbol-level breakdown to diagnose large firmware and unexpected binary growth. Use when the user asks "why is my firmware so large", "which function takes the most flash", or "why did my binary grow".Votes: 0GitHub stars: 5
- Gcc Compiler ExplorerInteractive compile-and-inspect workflow using local GCC toolchains (S32Compiler GCC 10.2/11.4). Compiles C/C++ code, produces real assembly, and explains how the compiler transforms source into instructions for embedded ARM Cortex-M/R/A targets. Use when the user asks "what assembly does GCC generate", "how does -O2 optimize this loop", or wants to inspect ARM code generation.Votes: 0GitHub stars: 5
- Gcc Linker ExplorerAnalyze linking behavior for embedded GCC (S32Compiler 10.2/11.4). Explains how object files, libraries, and linker options produce the final ELF. Use when the user asks "why is this function still being linked", "why isn't dead code being removed", "why does printf pull in so much code", or "how are my sections laid out".Votes: 0GitHub stars: 5
- Lax Benchmark OptimizationCompare assembly output and linked .eld size across LAX optimization levels (-O0 to -O4, -Os) for the NXP LAX vector signal processor using laxcc. Use when the user asks "which optimization level should I use for LAX", "why is my LAX binary too large", or wants to see how vectorization and hardware-loop generation change with -O level.Votes: 0GitHub stars: 5
- Lax Binary AnalysisAnalyze linked LAX .eld binaries produced by the laxcc toolchain. Identifies per-function code size contributors, section layout, and hardware-loop / vectorization patterns to diagnose oversized LAX images. Use when the user asks "why is my LAX .eld so large", "which LAX function is the largest", or "why did my LAX binary grow".Votes: 0GitHub stars: 5
- Lax Compiler ExplorerInteractive compile-and-inspect workflow using the local LAX C/C++ toolchain (laxcc, it3a-ds). Compiles C/C++ code for the NXP LAX vector signal processor, produces real assembly (.sl) or disassembly of the linked .eld, and explains VLIW/vector instructions. Use when the user asks "what assembly does LAX generate", "how does -O3 optimize this loop on LAX", or "is this code vectorized on LAX".Votes: 0GitHub stars: 5
- Lax Linker ExplorerAnalyze linking behavior of the NXP LAX toolchain (laxcc + .lcf linker command file). Explains how .eln object files, the EWL runtime, and the .lcf script combine into a final .eld image. Use when the user asks "why is my LAX firmware large", "why is this function still linked", "how do my LAX sections lay out", or "how do I use a custom startup on LAX".Votes: 0GitHub stars: 5
- Lax Simulator RunRun compiled LAX VSP programs on the local runsim simulator (S32DS/tools/LAX_Simulator/runsim). Executes an .eld file on a chosen VSPA3 device model (2AU / 16AU / 64AU), prints cycle counts, program flow, or redirected stdout, and forwards simulator-level flags before the .eld and program-level flags after the .eld. Use when the user asks to "simulate a LAX program", "run this .eld on runsim", "get the cycle count on VSPA3 16AU", or similar.Votes: 0GitHub stars: 5
- Spt Assembler ExplorerInteractive assemble-and-inspect workflow for the SPT3.8 toolchain (as-spt, objdump-spt). Assembles SPT3.8 source (.spt files), adds the correct .include directives and -I path for predefined memory symbols, and disassembles the ELF to show real SPT encoding. Use when the user asks "assemble this SPT snippet", "how does SPT encode this instruction", or "which address does OR_2_5_3 map to".Votes: 0GitHub stars: 5
- Spt Binary AnalysisAnalyze SPT3.8 ELF binaries using objdump-spt. Identifies section layout, per-function code size contributors, and diagnoses oversized SPT images. Use when the user asks "why is my SPT image so large", "which SPT function is biggest", or "why did my SPT ELF grow".Votes: 0GitHub stars: 5
- Freemaster Driver IntegrationIntegrates the FreeMASTER Driver as a standalone library into an embedded application project. Use whenever the user wants to add FreeMASTER Driver support to a third-party IDE, custom build system, or non-standard embedded project: discovering the installed library, adding include/source paths, creating freemaster_cfg.h, choosing the transport header, configuring interrupt mode, setting the comm base address, calling FMSTR_Init() and FMSTR_Poll(). Triggers on "integrate FreeMASTER driver", "...Votes: 0GitHub stars: 5
- Freemaster Lite Command Line ArgumentsCovers FreeMASTER Lite command-line options for fmlite.exe / fmlite.bin. Use whenever the user asks how to start FreeMASTER Lite from the command line, needs CLI flags such as --port, --host, --mock_api, --web_root, or --no-open_path, wants headless startup options, or needs to understand how named options interact with a .fmcfg configuration file.Votes: 0GitHub stars: 5
- Freemaster Lite Configuration FileCreates, edits, validates, and explains FreeMASTER Lite .fmcfg configuration files. Use whenever the user wants to define target connections, load ELF symbols, declare variables, configure file-system access rules, set up SSL, or enable mock API in a reusable project file. Triggers on "create .fmcfg", "edit fmcfg", "fmcfg format", "FreeMASTER connection string", "RS232 port speed", "add ELF to FreeMASTER", "FreeMASTER variables", "mock_api config".Votes: 0GitHub stars: 5
- Freemaster Lite Jsonrpc ApiDrives a running FreeMASTER Lite instance over its WebSocket JSON-RPC interface. Use whenever the user wants to connect to FreeMASTER Lite, start or stop target communication, load ELF or TSA symbols, define variables dynamically, validate variable definitions, read variables, write variables, or handle JSON-RPC errors. Triggers on "ReadVariable", "WriteVariable", "DefineVariable", "StartComm", "ReadELF", "GetAppVersion".Votes: 0GitHub stars: 5
- Freemaster Lite Start ServerLaunches the FreeMASTER Lite service (fmlite.exe / fmlite.bin) and verifies it is reachable. Use whenever the user wants to start FreeMASTER Lite, find fmlite.exe, start the service from a .fmcfg file, or troubleshoot startup readiness before using the JSON-RPC API or a web client. Triggers on "launch FreeMASTER Lite", "start fmlite", "FreeMASTER Lite not running", "fmlite.exe path", "start service from .fmcfg".Votes: 0GitHub stars: 5
- Freemaster Lite Stop ServerStops a running FreeMASTER Lite instance. Use whenever the user wants to stop fmlite.exe, restart it with a different configuration, release the server port, or recover from a stuck or unresponsive FreeMASTER Lite service. Triggers on "stop FreeMASTER Lite", "kill fmlite", "restart with new config", "fmlite stuck", "shut down FreeMASTER Lite".Votes: 0GitHub stars: 5
- Freemaster Lite Web ApplicationBuilds browser-based or Node.js applications that talk to FreeMASTER Lite through freemaster-client.js and the PCM API. Use whenever the user wants to create an HTML or JavaScript client, load client libraries, create a PCM instance, check board connection, load ELF or TSA symbols, and read or write variables from a web page. Triggers on "freemaster-client.js", "PCM object", "browser FreeMASTER", "Node.js FreeMASTER", "web app PCM", "StartComm from browser", "IsBoardDetected", "ReadVariable f...Votes: 0GitHub stars: 5
- S32ct CliGeneric dispatcher wrapper around the S32 Configuration Tools headless CLI. Fronts all 9 S32CT tools (Pins, Clocks, Peripherals, DCD, IVT, eFUSE, GTM, QuadSPI, FFC) behind the unified `nxp_s32ct_execute_action(action_name="s32ct.configure_cli", params={...})` entry point. Trigger phrases include "run S32CT headless", "call -SetValue", "-GetValue", "-ImportBin", "-ImportBlob", "-ExportBlob", "-ExportMEX", "-ExportAB", "-ValidateConfiguration", "apply use-case then tweak", "modify a .mex progra...Votes: 0GitHub stars: 5
- S32ct Clocks FacadeHeadless facade that fronts the Clocks tool of NXP S32 Configuration Tools via `nxp_s32ct_execute_action(action_name="s32ct.configure_clocks", params={...})`. Triggers when users ask to regenerate a clock tree, drive S32CT Clocks headlessly, export clock source code / HTML / registers / MEX from a `.mex` project, apply `custom_copyright` or `output_path_overrides`, or bootstrap clocks from an `-EmptyConfig` with `mcu` + `sdk_version`. Delegates shared launcher and plumbing details (workspace ...Votes: 0GitHub stars: 5
- S32ct Clocks Graft MexModifies the Clocks tool of an S32 Configuration Tools .mex for any S32-family MCU and any installed RTD version: changes clock frequencies, adds a McuClockReferencePoint, switches power modes, retargets AIPS_PLAT_CLK / CORE_CLK / CAN_PE_CLK / EMIOS_CLK, enables a PLL, configures SXOSC, sets up CLKOUT. Every trigger must name the Clocks tool, a `.mex` project, or a concrete S32 clock identifier. Triggers on "configure the Clocks tool in my .mex", "change CORE_CLK in the .mex clock tree", "set...Votes: 0GitHub stars: 5
- S32ct Clocks InfoLooks up what clocks, oscillators, PLLs, dividers, selectors, gates, peripheral clock outputs and power modes are configurable on a given MCU/RTD/package combination, and how each is configured in the S32 Configuration Tools Clocks tool. Triggers on questions about clock configuration, clock tree, oscillator setup (FXOSC/SXOSC/FIRC/SIRC), PLL setup, peripheral clock frequencies, clock dividers, clock selectors, gating, clock outputs, power modes (DRUN/STANDBY/...), or anything visible inside ...Votes: 0GitHub stars: 5
- S32ct Dca FacadeHeadless facade that fronts the DCA (Device Configuration Area) tool of NXP S32 Configuration Tools via `nxp_s32ct_configure(action="dca", ...)`. Triggers when users ask to import a binary DCA image, validate a DCA configuration, or export DCA artifacts as binary or C source from a `.mex` project on a DCA-capable SoC. Also handles bootstrapping DCA from `-EmptyConfig` with `mcu` + `sdk_version`. DCA is not a separate headless tool: it shares the DCD tool's `CmdApplication`, so the `dca` actio...Votes: 0GitHub stars: 5
- S32ct Dcd FacadeHeadless facade that fronts the DCD (Device Configuration Data) tool of NXP S32 Configuration Tools via `nxp_s32ct_execute_action(action_name="s32ct.configure_dcd", params={...})`. Triggers when users ask to import a binary DCD image, validate a DCD configuration, or export DCD artifacts as binary, C source, or MEX from a `.mex` project. Also handles bootstrapping DCD from `-EmptyConfig` with `mcu` + `sdk_version`. Delegates shared launcher and plumbing (workspace `-data`, `s32ct_launcher`, `...Votes: 0GitHub stars: 5
- S32ct Dcf FacadeHeadless facade that fronts the DCF (Device Configuration Format) tool of NXP S32 Configuration Tools via `nxp_s32ct_configure(action="dcf", ...)`. Triggers when users ask to import a binary DCF image, validate a DCF configuration, or export DCF artifacts as binary or C source from a `.mex` project on a DCF-capable SoC. Also handles bootstrapping DCF from `-EmptyConfig` with `mcu` + `sdk_version`. DCF is not a separate headless tool: it shares the DCD tool's `CmdApplication`, so the `dcf` act...Votes: 0GitHub stars: 5
- S32ct DistributionsExplains how S32 Configuration Tools ships on a host (standalone desktop vs. S32DS-integrated), what the MCP auto-discovers at startup, and how each distribution's headless CLI prefix differs. Use when the user asks "which S32CT is installed", "why does the command hang on -data", "toolsc.exe vs s32dsc.exe", or when hand-building a raw command line. Every other s32ct-* skill assumes this reference.Votes: 0GitHub stars: 5
- S32ct Efuse FacadeHeadless facade that fronts the eFUSE tool of NXP S32 Configuration Tools via `nxp_s32ct_execute_action(action_name="s32ct.configure_efuse", params={...})`. Triggers when users ask to export an eFUSE configuration as binary, ELF, or MEX, optionally including a serial-boot header (`-IncludeSerialBootHeader`), or bootstrap eFUSE from `-EmptyConfig` with `mcu` + `sdk_version`. Delegates shared launcher and plumbing (workspace `-data`, `s32ct_launcher`, `launcher_ini`, `timeout_s`, retry-on-`Ille...Votes: 0GitHub stars: 5
- S32ct Ffc FacadeHeadless facade that fronts the FFC tool of NXP S32 Configuration Tools via `nxp_s32ct_execute_action(action_name="s32ct.configure_ffc", params={...})`. Triggers when users ask to import AUTOSAR ARXML (`.ecvd`) files or JSON, restrict the FFC `-FileType` to `all|Fss_Rem_Pm|Fss_Btm`, fill default containers, validate the configuration, or export ARXML / JSON / MEX from a `.mex` project. Delegates shared launcher and plumbing (workspace `-data`, `s32ct_launcher`, `launcher_ini`, `timeout_s`, re...Votes: 0GitHub stars: 5
- S32ct Generate CodeTriggers headless code generation in S32 Configuration Tools for a single specific tool (Pins, Clocks, Peripherals, DCD, IVT, eFUSE, GTM, QuadSPI, or FFC) of an existing .mex project and exports the regenerated files to a target folder. Use when the user says "regenerate the pin mux", "refresh the clocks code", "export the peripherals HTML report", or wants to apply .mex edits to disk in a scoped way. Fronts nxp_s32ct_execute_action(action_name="s32ct.generate_code", params={...})Votes: 0GitHub stars: 5
- S32ct Generate Mex ConfigGenerates a starter S32 Configuration Tools `.mex` project file for any supported NXP S32 MCU / package / RTD combination by cloning a bundled `<MCU>_default.mex` reference template and applying a structured JSON patch (peripheral instance add / remove / patch, tool enable / disable, pin patches, clock patches). Use when the user asks to "generate a starter .mex", "clone .mex template", "create S32 Configuration Tools project file", "scaffold .mex for MCU X", "bootstrap .mex with peripheral a...Votes: 0GitHub stars: 5
- S32ct Get VersionRetrieves the installed S32 Configuration Tools identity - product name, framework version, installation path, launcher binary presence - via the `s32ct.env_version` action. Passive, read-only diagnostic. Trigger phrases: "which S32CT version is installed", "S32 Configuration Tools version", "is S32CT reachable", "S32CT installation path", "verify S32CT install", "check S32CT before generating code".Votes: 0GitHub stars: 5
- S32ct Gtm Create From UsecaseBootstraps a brand-new S32 Configuration Tools configuration for a given MCU and Platform SDK version, applies a predefined GTM use-case shipped with the MCU data package, and generates / exports the resulting GTM source code in one headless invocation. Use when the user says "apply the ATOM inverted PWM use-case for S32E288", "generate code for the TIM edge counter", "bootstrap a GTM project from a use-case template". Fronts nxp_s32ct_execute_action(action_name="s32ct.gtm_create_from_usecase...Votes: 0GitHub stars: 5
- S32ct Gtm FacadeHeadless facade that fronts the GTM (Generic Timer Module) tool of NXP S32 Configuration Tools via `nxp_s32ct_execute_action(action_name="s32ct.gtm_edit", params={...})`. Triggers when users ask to apply a GTM use-case template to an existing `.mex`, tweak GTM data-model values via `-SetValue`, query values via `-GetValue`, list available GTM use-cases for an MCU (the separate `s32ct.gtm_list_usecases` action), create from a use-case (the separate `s32ct.gtm_create_from_usecase` action), or e...Votes: 0GitHub stars: 5
- S32ct Ivt Build BlobBuilds a bootable IVT blob image with S32 Configuration Tools from one or more raw application binaries, for any NXP S32 family MCU (S32K1, S32K3, S32G, S32R, S32M, S32Z, S32E, S32S, S32N) and any installed Platform SDK / RTD version. Trigger phrases: "build a blob", "create a blob image", "make a boot image", "bundle CM7 cores into one image", "wrap application binaries into the IVT", "export -ExportBlob", or otherwise produce a single bootable image the boot ROM (BAF / BootROM / SBAF) can f...Votes: 0GitHub stars: 5
- S32ct Ivt FacadeHeadless facade that fronts the IVT (Image Vector Table) tool of NXP S32 Configuration Tools via `nxp_s32ct_execute_action(action_name="s32ct.configure_ivt", params={...})`. Triggers when users ask to import binary IVT images, blobs (`-ImportBlob`), application bootloader (`-ImportAB`), DDRC init app (`-ImportDDRC`), auto-align segments (`-AutoAlign`), set RAM start/entry pointers, and export IVT artifacts (Bin, C, Blob, AB, Pointers, DDRC, FssFw, MEX) from a `.mex` project. Also handles `-Cu...Votes: 0GitHub stars: 5
- S32ct Mcu Sdk LookupDiscovers which MCU parts and which PlatformSDK / RTD versions the installed NXP S32 Configuration Tools MCU data package actually supports, so the `mcu`, `sdk_version` and `platform_sdk` arguments required by configure, GTM and the other lookup actions can be resolved instead of guessed. Triggers on "which MCUs are available", "what parts does S32CT support", "list installed MCUs", "which SDK / RTD / PlatformSDK versions for S32K344", "what sdk_version should I use", "is S32G274A installed",...Votes: 0GitHub stars: 5
- S32ct Peripherals Author MexAuthors a fully-validated S32 Configuration Tools Peripherals-tool block on top of an existing Pins-tool routing for any S32 MCU (S32K1/K3, S32G2/G3, S32Z2, S32M, S32N, S32R, S32V, S32E, ...) and any installed RTD version, using the 5-source rule (`.component` schema plus `resource_tables/*.xml` plus `quick_selection` plus RTD example `.mex` plus existing `.mex`). Use when the user asks to "configure Peripherals tool in .mex", "add Spi/Uart/Can/Lin/Adc/Pwm instance", "author AUTOSAR driver co...Votes: 0GitHub stars: 5
- S32ct Peripherals FacadeHeadless facade that fronts the Peripherals tool of NXP S32 Configuration Tools via `nxp_s32ct_execute_action(action_name="s32ct.configure_peripherals", params={...})`. Triggers when users ask to import existing `.c` peripheral files (`-ImportC`), import a toolchain project (`-importProject`), point to an SDK manifest (`-sdkPath`), overwrite with SDK sources (`-overwriteWithSdkSources`), migrate components to a specific toolchain version or the highest available version, apply `custom_copyrig...Votes: 0GitHub stars: 5
- S32ct Peripherals Graft MexGrafts one or more Peripherals-tool driver instances (`Spi`, `Uart`, `Can_43_FLEXCAN`, `Lin_43_LPUART_FLEXIO`, `Adc`, `Pwm`, `Wdg_43_*`, `Icu`, `Gpt`, `Mcl`, `Eth_43_GMAC`, `I2c`, ...) into an existing S32 Configuration Tools `.mex` by lifting the `<instance>` block from the matching RTD example `.mex` and surgically adapting hw-channel selectors and cross-references. Use for any S32 family MCU with any RTD / Platform SDK version. Trigger phrases: "configure Peripherals tool", "add Spi/Uart/C...Votes: 0GitHub stars: 5
- S32ct Peripherals InfoRead-only inspector for the S32 Configuration Tools Peripherals tool. Answers what and how a peripheral (driver component) can be configured for any S32 family MCU (S32K1, S32K3, S32G, S32R, S32M, S32Z, S32E, S32S, S32N) and any installed RTD / Platform SDK, by parsing the on-disk `.component` descriptors and per-package `resource_tables/*.xml` enumerations shipped with S32 Design Studio. Trigger phrases: "peripheral configuration", "driver configuration", "RTD component settings", "configure...Votes: 0GitHub stars: 5
- S32ct Pins Author MexProduces a S32 Configuration Tools Pins-tool .mex from a board description (schematic PDF or explicit routings list) plus an MCU/RTD/package triple. Triggers on "configure pins for board X", "generate Pins .mex from schematic", "route SPI/UART/CAN/LIN/ADC/PWM for evaluation board", "S32CT Pins .mex bring-up", "board-tailored pin routing", "auto-route peripherals from this schematic". Canonical entry point when the inputs are (a board) + (a peripheral wish-list or routings) + (MCU/RTD/package)...Votes: 0GitHub stars: 5
- S32ct Pins FacadeHeadless facade that fronts the Pins tool of NXP S32 Configuration Tools via `nxp_s32ct_execute_action(action_name="s32ct.configure_pins", params={...})`. Triggers when users ask to regenerate pin-mux source code, import existing `.c` pin definitions via `-ImportC`, apply `custom_copyright` or `output_path_overrides`, or export pin artifacts as source, CSV, HTML, registers, or MEX from a `.mex` project. Also handles bootstrapping Pins from `-EmptyConfig` with `mcu` + `sdk_version`. Delegates ...Votes: 0GitHub stars: 5
- S32ct Pins InfoLooks up what pins, pads, signals, signal routings, pin multiplexing, pin properties and package pinouts are available in the S32 Configuration Tools Pins-tool data model for any NXP S32-family MCU (S32K1, S32K3, S32G2/G3, S32M, S32R, S32E, S32Z, S32S, ...) on any installed RTD / Platform SDK and any package variant. Triggers on "pin configuration", "pin info", "which pins exist on package X", "which pins can carry signal Y", "where can LPUART2_TX / LPSPI0_SCK / CAN0_TX / eMIOS_0_CH3 / ADC1_P...Votes: 0GitHub stars: 5
- S32ct Quadspi FacadeHeadless facade that fronts the QuadSPI tool of NXP S32 Configuration Tools via `nxp_s32ct_execute_action(action_name="s32ct.configure_quadspi", params={...})`. Triggers when users ask to import a binary QuadSPI image via `-ImportBin` and export QuadSPI artifacts as binary, C source, or MEX from a `.mex` project. Also handles bootstrapping QuadSPI from `-EmptyConfig` with `mcu` + `sdk_version`. Delegates shared launcher plumbing (workspace `-data`, `s32ct_launcher`, `launcher_ini`, `timeout_s...Votes: 0GitHub stars: 5
- S32debugger Adapt Existing ScriptAdapt an existing standalone S32Debugger script, launcher, startup helper, working flow, or previously generated automation with the smallest correct change set while preserving proven startup, init, bridge, connect, load, breakpoint, and reporting structure. Use this skill when the user says 'adapt this script', 'same flow but...', 'keep the working launcher and change...', 'reuse this example but modify it', or wants to retarget an existing Python, shell wrapper (`.sh` on Linux, `.bat`/`.cm...Votes: 0GitHub stars: 5
- S32debugger Ccs Execution RouterRoute CCS execution requests to the correct standalone CCS Tcl workflow. Use this whenever the user mentions CCS, the CCS executable (`ccs` / `ccs.exe`), CCS Tcl, probe connection, target identification, get_target_info, debug lock status, core status, attach-ready targets, bring-up from reset, CCS as a fallback after failed GDB startup, or a family-specific CCS attach/core-status sanity check. This skill classifies the goal as generic discovery, attach-ready attach/control, needs initializat...Votes: 0GitHub stars: 5
- S32debugger Ccs Generate Self Contained TclGenerate a self-contained CCS Tcl script for execution by the CCS executable (`ccs` on Linux, `ccs.exe` on Windows). Use this whenever the user asks for a CCS script to connect to a probe, identify a target, get target info, check debug lock state, attach to an already initialized SoC, inspect target/core status, do a bring-up-from-reset flow, run a minimal CCS sanity check after failed GDB startup, or run a family-specific attach/core-status sanity test. Generate the script from the confirme...Votes: 0GitHub stars: 5
- S32debugger Ccs Run Tcl ScriptExecute or validate a CCS Tcl script with the CCS executable (`ccs` on Linux, `ccs.exe` on Windows). Use this whenever the user wants to start CCS, run a CCS Tcl script headlessly or with a visible CCS workflow, prove whether a target-discovery or attach script actually ran, troubleshoot why CCS succeeded at probe setup but failed later at generic chain, family-specific chain, attach, or initialization steps, or run a family-specific attach/core-status sanity test. Use this for evidence-based...Votes: 0GitHub stars: 5
- S32debugger Connect Gdb To S32 Debug ProbeExecute the low-level GDB CLI procedure to connect to an S32 Debug Probe. Use this whenever the user wants raw GDB probe-connection steps, needs to know which Python globals must be set, needs the correct init script for bareboard versus attach scenarios, wants the exact `board_init()` / `core_init()` ordering, or asks about `load` versus `symbol-file` behavior outside the higher-level standalone session workflows.Votes: 0GitHub stars: 5
- S32debugger Convert Ltb Cmm To PythonTranslate Lauterbach TRACE32 `.cmm` init sequences into Python suitable for later incorporation into an S32Debugger pipeline. Use this whenever the user wants a TRACE32 bring-up or init script converted to reusable Python, normalized into helpers such as `partition_init()` or `sram_init()`, compared against shipped S32Debugger family scripts, or optionally wrapped in a fuller connect/attach/load flow. Keep the translation family-neutral unless the CMM or the user explicitly confirms SoC ident...Votes: 0GitHub stars: 5