S32ct Dcd Facade

---
name: s32ct-dcd-facade
description: >
  Headless 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`, `launcher_ini`, `timeout_s`,
  retry-on-`IllegalStateException`) to the generic `s32ct-cli` skill.
  Keywords: DCD, `-ImportBin`, `-ValidateConfiguration`, ExportBin, ExportC, ExportMEX,
  `.bin`, `.mex`.
license: LA_OPT_Online Code Hosting NXP_Software_License
metadata:
  author: NXP
  version: "1.0.0"
  product: s32ct
  depends_on: '[s32ct-cli]'
  tags: '[s32ct, headless, configuration-tools, facade, dcd, code-generation]'
---

# S32CT DCD - Headless Facade

Thin per-tool facade over the generic `s32ct-cli` skill that exposes only the
flags relevant to the **DCD** tool of S32 Configuration Tools. This skill
fronts the `nxp_s32ct_execute_action` MCP tool with `action_name="s32ct.configure_dcd"` (the
`tool_name` is pre-filled from the action). All shared launcher plumbing,
validation, and auto-retry behavior is inherited from `s32ct-cli`.

## When to use

Use this skill when:
- You need to import a binary DCD image into a `.mex` via `-ImportBin`.
- You need to validate a DCD configuration with `-ValidateConfiguration`.
- You need to export DCD artifacts: binary, C source, or MEX.

**Migration note:** The standalone `dcd` MCP tool no longer exists - it has
been replaced by the standardized action surface: run it as `s32ct.configure_dcd` through `nxp_s32ct_execute_action`.
Existing inputs are unchanged.

Do **not** use this skill for:
- Cross-tool operations combining flags from multiple tools -> use
  `s32ct-cli` (s32ct.configure_cli).
- QuadSPI / IVT binary handling - use the matching facade.

## Available Capabilities

| Type | Name | Invocation |
|------|------|------------|
| MCP tool | `nxp_s32ct_execute_action` | `nxp_s32ct_execute_action(action_name="s32ct.configure_dcd", params={...})` |
| Resource | `skill://nxp_s32ct/s32ct-dcd-facade` | Auto-loaded on trigger |

## Quickstart

### 1. Load or bootstrap a `.mex`

```
Tool:    nxp_s32ct_execute_action
Action:  s32ct.configure_dcd
Input:   project_path="<path>.mex"   # OR empty_config=True + mcu + sdk_version
Output:  {exit_code, command, stdout_tail, stderr_tail, values, summary}
```

### 2. Apply DCD-specific modifications and export

```python
nxp_s32ct_execute_action(
    action_name="s32ct.configure_dcd",
    params={
        "project_path": "<path>.mex",
        "import_bin": "<dcd>.bin",        # -ImportBin
        "validate": True,                 # -ValidateConfiguration
        "export_kind": "ExportBin",       # or ExportAll|ExportC|ExportMEX
        "output_dir": "<output-dir>",
    },
)
```

### 3. Verify the export

Check that `output_dir` contains the expected artifacts and `exit_code == 0`.

## Inputs

### Mode (mutually exclusive)
- `project_path` - existing `.mex` to load via `-Load`.
- `empty_config` - if `True`, `-EmptyConfig`; requires `mcu` + `sdk_version`.
- `config_name` - `-ConfigName <...>`.

### Tool-specific
- `import_bin` - DCD binary via `-ImportBin`.
- `validate` - run `-ValidateConfiguration` on the configuration.

### Export
- `export_kind` in {`ExportAll, ExportBin, ExportC, ExportMEX`}.
- `output_dir` - required when `export_kind` is set.

### Launcher / plumbing (shared with `s32ct-cli`)
- `data_dir` (`-data <workspace>`), `extra_args`, `s32ct_launcher`,
  `launcher_ini`, `timeout_s` (default 600).

## Output

Same as `s32ct-cli`:
`{ exit_code, command, stdout_tail, stderr_tail, values, summary }`.

## Guardrails

**Scope**
- Only drives the **dcd** action of `nxp_s32ct_execute_action`. For cross-tool
  workflows use `s32ct-cli` (s32ct.configure_cli) instead.
- Does not modify hardware or program devices.

**Destructive actions**
- Exports overwrite files in `output_dir`. Confirm the target directory
  is safe or empty before invoking with `export_kind` set.

**Refuse-and-escalate**
- Missing `project_path` AND missing `empty_config`/`mcu`/`sdk_version`
  combination -> ask the user which mode they want.
- Unknown `export_kind` value -> list the allowed enum values and ask.
- Retryable `IllegalStateException` -> auto-retry once, then escalate.

## Validation loop

1. `exit_code == 0`.
2. `output_dir` contains the expected artifacts for the chosen `export_kind`.
3. If `validate=True`, check `stdout_tail` / `summary` for validation OK.

## Out of scope

- Interactive GUI operations - use S32 Configuration Tools directly.
- Cross-tool operations combining multiple tools' flags - use `s32ct-cli`.
- Distribution portability (`desktop` vs `integrated_s32ds`) - handled
  transparently by the MCP; see `s32ct-distributions`.

## See Also

- `s32ct-cli` - generic dispatcher with the full ~50-parameter surface.
- `s32ct-dca-facade`, `s32ct-dcf-facade` - sibling Device-Configuration tool
  facades that share this same DCD `CmdApplication` and CLI grammar.
- `s32ct-distributions` - launcher selection.
- `s32ct-ivt-facade`, `s32ct-quadspi-facade` - related binary-import tool
  facades.