# NXP S32K3 at Eindhoven: deployment

Canonical ID: `959b593d-bcab-4dcf-aa07-db7f7776539f`

Aggregate deployment of NXP S32K3 across automotive ECUs and safety-critical robotics.

**Trust tier:** Catalog entry · 1 source · not yet field-verified

_Last updated: 2026-06-08_

- **Slug:** nxp-s32k3-hq-aggregate
- **Status:** operational
- **Model:** [NXP S32K3](/models/nxp-s32k3.md) (id: `fe707376-3406-4261-8029-f0be7419e516`)
- **Company:** [NXP Semiconductors](/companies/nxp-semiconductors.md) (id: `c00ceec0-ce09-4808-b3b3-13e9dfa776e9`)
- **Location:** [Eindhoven](/locations/eindhoven-netherlands.md) (id: `6c6d48b1-81cf-4802-92ab-0ca74a8ba9fd`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://www.nxp.com/

## Common questions

### What is the NXP S32K3 deployment at Eindhoven?

NXP S32K3, built by NXP Semiconductors, is recorded as a deployment at Eindhoven on the DEPLOY registry. NXP Semiconductors operates the deployment directly.

### Who operates NXP S32K3 at Eindhoven?

NXP Semiconductors, the manufacturer of NXP S32K3, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the NXP S32K3 deployment at Eindhoven?

No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.


_API: GET /v1/robots/959b593d-bcab-4dcf-aa07-db7f7776539f · feeds: GET /v1/feeds?deploymentId=959b593d-bcab-4dcf-aa07-db7f7776539f · canonical URL: /deployments/nxp-s32k3-hq-aggregate_