Competitive landscape · 5 vendors
Who else wants this socket.
77 AURIX devices against 7 competitor families from 5 vendors, on 13 dimensions. Pick a device and the table narrows to the rivals that contest the same applications; the application matrix closes the page.
Competitor pages read 2026-09-21. 5 of 13 dimensions are gaps for every vendor, including AURIX.
AURIX devices
77 public devices · pick one to narrow the field to its rivals
- TC322LP1-core · 160 MHz · 1 MB flash · ASIL-D
- TC323LP1-core · 160 MHz · 1 MB flash · ASIL-D
- TC324LP1-core · 160 MHz · 1 MB flash · ASIL-D
- TC327LP1-core · 160 MHz · 1 MB flash · ASIL-D
- TC332LP1-core · 300 MHz · 2 MB flash · ASIL-D
- TC333LP1-core · 300 MHz · 2 MB flash · ASIL-D
- TC334LP1-core · 300 MHz · 2 MB flash · ASIL-D
- TC336DA2-core · 300 MHz · 2 MB flash · ASIL-D
- TC336LP1-core · 300 MHz · 2 MB flash · ASIL-D
- TC337DA2-core · 300 MHz · 2 MB flash · ASIL-D
- TC337LP1-core · 300 MHz · 2 MB flash · ASIL-D
- TC356TA3-core · 300 MHz · 4 MB flash · ASIL-D
- TC356TH3-core · 300 MHz · 4 MB flash · ASIL-D
- TC357TA3-core · 300 MHz · 4 MB flash · ASIL-D
- TC357TH3-core · 300 MHz · 4 MB flash · ASIL-D
- TC364DP2-core · 300 MHz · 4 MB flash · ASIL-D
- TC365DP2-core · 300 MHz · 4 MB flash · ASIL-D
- TC366DP2-core · 300 MHz · 4 MB flash · ASIL-D
- TC367DP2-core · 300 MHz · 4 MB flash · ASIL-D
- TC375TP3-core · 300 MHz · 6 MB flash · ASIL-D
- TC377TP3-core · 300 MHz · 6 MB flash · ASIL-D
- TC377TX3-core · 300 MHz · 6 MB flash · ASIL-D
- TC387QP4-core · 300 MHz · 10 MB flash · ASIL-D
- TC389QP4-core · 300 MHz · 10 MB flash · ASIL-D
- TC397QA4-core · 300 MHz · 16 MB flash · ASIL-D
- TC397XA6-core · 300 MHz · 16 MB flash · ASIL-D
- TC397XM6-core · 300 MHz · 16 MB flash · ASIL-D
- TC397XP6-core · 300 MHz · 16 MB flash · ASIL-D
- TC397XX6-core · 300 MHz · 16 MB flash · ASIL-D
- TC399XP6-core · 300 MHz · 16 MB flash · ASIL-D
- TC399XX6-core · 300 MHz · 16 MB flash · ASIL-D
- TC3E7QF4-core · 300 MHz · 12 MB flash · ASIL-D
- TC3E7QG4-core · 300 MHz · 10 MB flash · ASIL-D
- TC3E7QX4-core · 300 MHz · 12 MB flash · ASIL-D
- TC212L1-core · 133 MHz · 0.5 MB flash · ASIL-D
- TC212S1-core · 133 MHz · 0.5 MB flash · ASIL-B
- TC213L1-core · 133 MHz · 0.5 MB flash · ASIL-D
- TC213S1-core · 133 MHz · 0.5 MB flash · ASIL-B
- TC214L1-core · 133 MHz · 0.5 MB flash · ASIL-D
- TC214S1-core · 133 MHz · 0.5 MB flash · ASIL-B
- TC222L1-core · 133 MHz · 1 MB flash · ASIL-D
- TC222S1-core · 133 MHz · 1 MB flash · ASIL-B
- TC223L1-core · 133 MHz · 1 MB flash · ASIL-D
- TC223S1-core · 133 MHz · 1 MB flash · ASIL-B
- TC224L1-core · 133 MHz · 1 MB flash · ASIL-D
- TC224S1-core · 133 MHz · 1 MB flash · ASIL-B
- TC233L1-core · 200 MHz · 2 MB flash · ASIL-D
- TC233LP1-core · 200 MHz · 2 MB flash · ASIL-D
- TC234L1-core · 200 MHz · 2 MB flash · ASIL-D
- TC234LA1-core · 200 MHz · 2 MB flash · ASIL-D
- TC234LP1-core · 200 MHz · 2 MB flash · ASIL-D
- TC234LX1-core · 200 MHz · 2 MB flash · ASIL-D
- TC237LP1-core · 200 MHz · 2 MB flash · ASIL-D
- TC264D2-core · 200 MHz · 2.5 MB flash · ASIL-D
- TC264DA2-core · 200 MHz · 2.5 MB flash · ASIL-D
- TC265D2-core · 200 MHz · 2.5 MB flash · ASIL-D
- TC267D2-core · 200 MHz · 2.5 MB flash · ASIL-D
- TC275T3-core · 200 MHz · 4 MB flash · ASIL-D
- TC275TP3-core · 200 MHz · 4 MB flash · ASIL-D
- TC277T3-core · 200 MHz · 4 MB flash · ASIL-D
- TC277TP3-core · 200 MHz · 4 MB flash · ASIL-D
- TC297T3-core · 300 MHz · 8 MB flash · ASIL-D
- TC297TA3-core · 300 MHz · 8 MB flash · ASIL-D
- TC297TB3-core · 300 MHz · 8 MB flash · ASIL-D
- TC297TP3-core · 300 MHz · 8 MB flash · ASIL-D
- TC297TX3-core · 300 MHz · 8 MB flash · ASIL-D
- TC297TY3-core · 300 MHz · 8 MB flash · ASIL-D
- TC298TP3-core · 300 MHz · 8 MB flash · ASIL-D
- TC299TP3-core · 300 MHz · 8 MB flash · ASIL-D
- TC299TX3-core · 300 MHz · 8 MB flash · ASIL-D
- TC299TY3-core · 300 MHz · 8 MB flash · ASIL-D
- TC21xSC1-core · 133 MHz · 0.5 MB flash · ASIL-D
- TC29xTT3-core · 300 MHz · 8 MB flash · ASIL-D
TC49x against the field
Positioned for Powertrain / EV, so it is compared against the 5 competitor families that name at least one of those.
| Dimension | TC49xAURIX | S32K3NXP | RH850/U2BRenesas | Stellar P6 (SR6 P6)ST | AM263x (AM2634)TI | E3SemiDrive |
|---|---|---|---|---|---|---|
| PerformanceHow much compute, at what clock, with how much memory behind it? | 5 TriCore · 400 MHz · 20 MB flashCompute class very-high (our own relative proxy). Lockstep published. | 4 cores · 320 MHz · 12 MB NVMSingle, multiple or lockstep Arm Cortex-M7 with FPU | 4 cores · 400 MHz · 10 MB NVMUp to 4x 400 MHz CPU cores plus up to 3x dual-core lockstep, 28 nm | 6 cores · 16 MB NVMUp to 6x Arm Cortex-R52+, lockstep and split-lock, 28 nm FD-SOI | 4 cores · 400 MHzQuad-core Arm Cortex-R5F, lockstep or dual-core capable clusters | 6 cores · 800 MHz · 16 MB NVMArm Cortex-R5F and Cortex-R52+, up to 6 cores, 4 configurable as dual-core lockstep |
| SafetyWhat ASIL does the vendor claim, and is lockstep published? | ASIL-DLockstep cores published on the series page. | ASIL-DLockstep published. | ASIL-DLockstep published. | ASIL-DLockstep published. | ASIL-DLockstep published. | ASIL-DLockstep published. |
| SecurityIs there a named hardware security block, and what standard does it claim? | HSM + post-quantumPost-quantum cryptography stated on the series page. | HSEHSE (Hardware Security Engine) | Security module with EVITA Full supportSecurity module with EVITA Full support | Embedded HSMEmbedded HSM | HSM with Auto SHE 1.1 / EVITA supportHSM with Auto SHE 1.1 / EVITA support | EVITA Full / ISO 21434 compliant securityEVITA Full / ISO 21434 compliant security |
| AIIs there a hardware accelerator for neural or parallel workloads? | PPUParallel Processing Unit stated for this series. | None listedderivedNo AI accelerator on the vendor's product page. | None listedderivedNo AI accelerator on the vendor's product page. | None listedderivedNo AI accelerator on the vendor's product page. | None listedderivedNo AI accelerator on the vendor's product page. | None listedderivedNo AI accelerator on the vendor's product page. |
| ConnectivityWhat in-vehicle networks does it terminate, and how fast? | CAN-XL · CAN-FD · LIN4 network interfaces listed. | 1 Gbps Ethernet · CAN-FDAs published on the vendor's product page. | 100 Mbps Ethernet · CAN-FDAs published on the vendor's product page. | CAN-FDAs published on the vendor's product page. | 1 Gbps Ethernet · CAN-FDAs published on the vendor's product page. | CAN-FDAs published on the vendor's product page. |
| SoftwareWhat toolchain and AUTOSAR support does the vendor publish? | AURIX Development Studio · AUTOSAR MCALderivedToolchain is common to the AURIX portfolio; it is not a per-series differentiator. | S32 Design Studio, AUTOSAR MCAL, Real-Time DriversNamed by the vendor. | e² studio, AUTOSAR MCAL, RH850 software packagesNamed by the vendor. | ST AutoDevKit, AUTOSAR MCALNamed by the vendor. | MCU+ SDK, Code Composer Studio, AUTOSAR MCALNamed by the vendor. | SemiDrive SDK, AUTOSARNamed by the vendor. |
| PriceWhat does it cost at programme volume? | no published figureNo vendor publishes automotive MCU pricing; it is quoted per programme at volume. Fill from your own quote history. | no published figureNo vendor publishes automotive MCU pricing; it is quoted per programme at volume. Fill from your own quote history. | no published figureNo vendor publishes automotive MCU pricing; it is quoted per programme at volume. Fill from your own quote history. | no published figureNo vendor publishes automotive MCU pricing; it is quoted per programme at volume. Fill from your own quote history. | no published figureNo vendor publishes automotive MCU pricing; it is quoted per programme at volume. Fill from your own quote history. | no published figureNo vendor publishes automotive MCU pricing; it is quoted per programme at volume. Fill from your own quote history. |
| Power consumptionWhat does it draw under a comparable workload? | no published figurePower figures are published per operating mode in datasheets that are not comparable across vendors without matching the workload, clock tree and temperature. | no published figurePower figures are published per operating mode in datasheets that are not comparable across vendors without matching the workload, clock tree and temperature. | no published figurePower figures are published per operating mode in datasheets that are not comparable across vendors without matching the workload, clock tree and temperature. | no published figurePower figures are published per operating mode in datasheets that are not comparable across vendors without matching the workload, clock tree and temperature. | no published figurePower figures are published per operating mode in datasheets that are not comparable across vendors without matching the workload, clock tree and temperature. | no published figurePower figures are published per operating mode in datasheets that are not comparable across vendors without matching the workload, clock tree and temperature. |
| AvailabilityWhat is the lead time and allocation status? | no published figureLead times and allocation status are commercial information, not published by any vendor on a product page. | no published figureLead times and allocation status are commercial information, not published by any vendor on a product page. | no published figureLead times and allocation status are commercial information, not published by any vendor on a product page. | no published figureLead times and allocation status are commercial information, not published by any vendor on a product page. | no published figureLead times and allocation status are commercial information, not published by any vendor on a product page. | no published figureLead times and allocation status are commercial information, not published by any vendor on a product page. |
| EcosystemWhat development hardware and partner support exists? | AURIX Development Studio, evaluation boards, AUTOSAR partnersderivedNamed on the vendor's own pages. Depth of partner support is not published in a comparable form. | S32 Design StudioderivedRead from the toolchain the vendor names. Partner depth is not published comparably. | e² studioderivedRead from the toolchain the vendor names. Partner depth is not published comparably. | ST AutoDevKitderivedRead from the toolchain the vendor names. Partner depth is not published comparably. | MCU+ SDKderivedRead from the toolchain the vendor names. Partner depth is not published comparably. | SemiDrive SDKderivedRead from the toolchain the vendor names. Partner depth is not published comparably. |
| Customer baseWho has already designed it in? | no published figureDesign wins and named customers are confidential. This project never names a customer without an authoritative source. | no published figureDesign wins and named customers are confidential. This project never names a customer without an authoritative source. | no published figureDesign wins and named customers are confidential. This project never names a customer without an authoritative source. | no published figureDesign wins and named customers are confidential. This project never names a customer without an authoritative source. | no published figureDesign wins and named customers are confidential. This project never names a customer without an authoritative source. | no published figureDesign wins and named customers are confidential. This project never names a customer without an authoritative source. |
| MigrationHow much room is there to scale a design up or down within the family? | 4 devices in TC4xderivedBreadth of the published generation. Pin-compatibility is not published per device, so this is room to choose, not a drop-in path. | no published figureS32K3 does not publish a device-by-device breakdown of the family on this page, so there is no like-for-like count to compare. | no published figureRH850/U2B does not publish a device-by-device breakdown of the family on this page, so there is no like-for-like count to compare. | no published figureStellar P6 (SR6 P6) does not publish a device-by-device breakdown of the family on this page, so there is no like-for-like count to compare. | no published figureAM263x (AM2634) does not publish a device-by-device breakdown of the family on this page, so there is no like-for-like count to compare. | no published figureE3 does not publish a device-by-device breakdown of the family on this page, so there is no like-for-like count to compare. |
| Time-to-marketHow long from kick-off to a running prototype? | no published figureTime-to-market depends on your team's existing platform, toolchain and safety artefacts far more than on the part. It is a programme estimate, not a device spec. | no published figureTime-to-market depends on your team's existing platform, toolchain and safety artefacts far more than on the part. It is a programme estimate, not a device spec. | no published figureTime-to-market depends on your team's existing platform, toolchain and safety artefacts far more than on the part. It is a programme estimate, not a device spec. | no published figureTime-to-market depends on your team's existing platform, toolchain and safety artefacts far more than on the part. It is a programme estimate, not a device spec. | no published figureTime-to-market depends on your team's existing platform, toolchain and safety artefacts far more than on the part. It is a programme estimate, not a device spec. | no published figureTime-to-market depends on your team's existing platform, toolchain and safety artefacts far more than on the part. It is a programme estimate, not a device spec. |
5 of 13 dimensions are empty for every vendor. Price, Power consumption, Availability, Customer base, Time-to-market — no vendor publishes these on a product page, so this table shows the hole rather than filling it. They come from your own quote history, bench measurements and CRM.
Competitor matrix
Which vendors position a part for each application, in their own words.
An empty cell means that vendor’s public page does not name this application — it is absence of a published claim, not proof they do not compete.
| Application | AURIX | NXP | Renesas | ST | TI | SemiDrive |
|---|---|---|---|---|---|---|
| ADAS | TC2x · TC3x · TC4x | — | — | — | — | E3 |
| Radar | TC2x · TC3x · TC4x | — | — | — | — | — |
| Chassis | TC3x · TC4x | S32K3 | RH850/U2B | — | AM263x (AM2634) | E3 |
| Braking | TC3x · TC4x | — | RH850/U2B | — | — | — |
| Steering | TC3x · TC4x | — | — | — | — | — |
| Zonal | TC4x | S32K3 · S32G | RH850/U2B | Stellar P6 (SR6 P6) · Stellar G6 (SR6 G6) | — | E3 |
| Gateway | TC3x · TC4x | S32G | — | — | — | — |
| Domain control | TC3x · TC4x | S32G | RH850/U2B | Stellar P6 (SR6 P6) · Stellar G6 (SR6 G6) | — | E3 |
| Powertrain / EV | TC2x · TC3x · TC4x | S32K3 | RH850/U2B | Stellar P6 (SR6 P6) | AM263x (AM2634) | E3 |
| Body & comfort | TC2x · TC3x | S32K3 | — | Stellar G6 (SR6 G6) | AM263x (AM2634) | — |
Sources · 7 vendor pages, read 2026-09-21
- NXP S32K3 — General-purpose automotive MCU family spanning body, zonal and vehicle control, with scalable Cortex-M7 configurations. vendor page · read 2026-09-21
- NXP S32G — Vehicle network processors for service-oriented gateways and domain controllers, with the LLCE network accelerator and PFE packet-forwarding engine. vendor page · read 2026-09-21
- Renesas RH850/U2B — Zone, domain and vehicle-motion controller, with per-core virtualization and QoS for integrating multiple ASIL-D partitions into one ECU. vendor page · read 2026-09-21
- ST Stellar P6 (SR6 P6) — Integration MCU for software-defined vehicles and EV platform system integration, with phase-change memory sized for over-the-air updates. vendor page · read 2026-09-21
- ST Stellar G6 (SR6 G6) — General-purpose integration MCU with the largest xMemory in the Stellar line, for consolidating multiple ECUs behind one controller. vendor page · read 2026-09-21
- TI AM263x (AM2634) — Real-time control MCU with an integrated two-port Ethernet switch, aimed at motor control and real-time deterministic communication. vendor page · read 2026-09-21
- SemiDrive E3 — High-performance automotive MCU for ADAS, intelligent cockpit, zone controllers, e-powertrain and intelligent chassis. vendor page · read 2026-09-21
Competitor figures are transcribed from each vendor's own public product pages on the date shown, and each cell links to the page it came from. Nothing here is benchmarked, measured or estimated by this project. A dimension no vendor publishes — price, power, availability, customer base, time-to-market — is shown as a gap for every column including AURIX, because the honest answer to those is that no product page states them.