S32CT eFUSE - Headless Facade

Thin per-tool facade over the generic s32ct-cli skill that exposes only the flags relevant to the eFUSE tool of S32 Configuration Tools. This skill fronts the nxp_s32ct_execute_action MCP tool with action_name="s32ct.configure_efuse" (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 export an eFUSE configuration in binary / ELF / MEX form.
• You need to include a serial-boot header via -IncludeSerialBootHeader.
• You need to bootstrap eFUSE from -EmptyConfig (requires mcu + sdk_version).

Migration note: The standalone efuse MCP tool no longer exists - it has been replaced by the standardized action surface: run it as s32ct.configure_efuse 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).
• Programming eFUSEs on real hardware - this only exports configuration artifacts.

Available Capabilities

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

Quickstart

1. Load or bootstrap a .mex

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

2. Apply eFUSE-specific modifications and export

nxp_s32ct_execute_action(
    action_name="s32ct.configure_efuse",
    params={
        "project_path": "<path>.mex",
        "include_serial_boot_header": True,   # -IncludeSerialBootHeader
        "export_kind": "ExportConfig",        # or ExportAll|ExportELF|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

• include_serial_boot_header - -IncludeSerialBootHeader.

Export

• export_kind in {ExportAll, ExportConfig, ExportELF, 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 efuse action of nxp_s32ct_execute_action. For cross-tool workflows use s32ct-cli (s32ct.configure_cli) instead.
• Does not program hardware - exports files only.

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 include_serial_boot_header=True, confirm the header bytes appear in the exported binary.

Out of scope

• Interactive GUI operations - use S32 Configuration Tools directly.
• Cross-tool operations combining multiple tools' flags - use s32ct-cli.
• Actually blowing eFUSEs on silicon - out of scope.
• Distribution portability handled transparently; see s32ct-distributions.

See Also

• s32ct-cli - generic dispatcher with the full ~50-parameter surface.
• s32ct-distributions - launcher selection.
• s32ct-ivt-facade - related boot-image tool facade.