@h2loop/autosar — AUTOSAR Classic pack for Hydron
Deterministic tools for AUTOSAR Classic integration work, so the agent never hand-writes ARXML:
| Tool | What it does | Runs |
|---|---|---|
ecuc_read | ECUC configuration as compact ECUC JSON; def summaries (schema) | local (Python engine) |
ecuc_edit | set / add / remove by AUTOSAR path; in-place byte patches; all-or-nothing; schema check | local |
ecuc_validate | multiplicity, mandatory, range, enum, type, string, ref target/dest, dangling, duplicates → LSP-like diagnostics | local |
ecuc_find | structured queries over the ECUC (conditions, references to/from) | local |
ecuc_crosscheck | per-module cross-check table (extract, gateway, NvM sizeof, capacity, packing, handles) | local |
arxml_edit | structured edits of System extract / SWC ARXML, incl. new_file (DEST inferred, schema-ordered, missing packages created) | local |
autosar_add_like | add a new X like an existing Y (message, port, runnable+event, Dem event, NvM block, ...): clones the whole named chain across ECUC + System ARXML, renamed; links, handle IDs, values; validates or rolls back | local |
autosar_add_signal | add a signal end to end (ECUC + extract chain + DBC), validate or roll back | local |
arxml_diff | semantic diff by AUTOSAR path (ignores UUIDs, order, whitespace, file splits) | local |
autosar_trace | config ↔ generated C symbol ↔ in-house callers, via the H2Loop code graph | H2Loop backend |
autosar_config_lookup | element + children + refs in/out + links from the code graph | H2Loop backend |
autosar_spec_id_check | check requirement IDs (SWS_/TPS_/ECUC_…) against your own spec text exports: DEFINED + text / MENTIONED-ONLY / NOT-FOUND | local (specDocs) |
autosar_audit | integration review of C code: BSW API handles, direction, widths, NvM NULL_PTR vs ECUC | local |
autosar_generate / autosar_build | run the project's configured generator / build command (asks permission) | local |
Plus the autosar skill (ECUC model, symbolic-name rule, config classes, project layout, the
edit → validate → generate → build → trace loop), the autosar-integrator subagent, and the
/autosar-validate and /autosar-trace commands.
Install
hydron plugin add @h2loop/autosar # or a local path / --project
Requirements: uv (preferred; adds the strict ARXML schema check via
autosar-data) or Python ≥ 3.10 on PATH (AUTOSAR_PYTHON overrides). The backend tools use the
Hydron login and selected H2Loop project (or workspace_id); KILO_API_URL overrides the backend.
Project configuration
Param definitions are not bundled. The engine finds them in this order: .hydron/autosar.json
paramDefs globs → any project .arxml containing ECUC-MODULE-DEF (vendor BSWMD) →
$AUTOSAR_PARAMDEFS (path list). Without defs, values are readable but not validated.
{
"paramDefs": ["SIP/**/bswmd/*.arxml"],
"config": ["Config/**/*.arxml"],
"input": ["Input/**/*.arxml"],
"generate": {"command": "<vendor-cli> --project Config/Ecu.dpa --generate {module}", "timeoutSec": 3600},
"build": "make -C Build all",
"specDocs": ["~/autosar/R25-11/txt/*.txt"]
}
ecuc_read / ecuc_find give every value with "@at:<Param>" (file:line of its VALUE element) and integers with
"@hex:<Param>"; autosar_trace / autosar_config_lookup add the same per value for elements in the local
checkout. specDocs (or $AUTOSAR_SPEC_DOCS) points autosar_spec_id_check at text exports of the AUTOSAR
specifications you are licensed to use; the pack bundles no spec text and no requirement-ID index.
Engine CLI
cd python && uv run --no-project --with autosar-data==0.17.0 python -m ecuc_engine --root <project> \
<info|read [path] [--depth N] [--schema]|edit --ops '<json>' [--dry-run]|validate [--module M] [--file F]|diff A B> --json
Develop
bun install && bun run build && bun run typecheck
bun run test:py # pytest; R25-11 integration tests run when AUTOSAR_R25_DEFS (or the eval_work copy) exists
hydron plugin validate .