Key Takeaways
- Joint offering: Elektrobit (EB) and Microchip combine EB tresos AUTOSAR tools with Microchip’s automotive‑grade MCUs to deliver a pre‑integrated software stack.
- Speed to market: The solution cuts classic AUTOSAR integration time by up to 30 % and reduces project‑risk through reusable “integration‑as‑code” assets.
- Hardware coverage: Supports Microchip’s PIC32MZ, SAM V71, and AVR‑XMEGA families, each meeting ISO 26262 ASIL‑B or higher.
- Automation focus: EB’s workflow engine automates MCAL generation, configuration, and validation, laying the groundwork for AI‑assisted code synthesis.
- Target audience: OEMs and Tier‑1 suppliers developing software‑defined vehicles that need a production‑ready AUTOSAR baseline quickly.
Elektrobit + Microchip: A Streamlined Path to AUTOSAR‑Based ECUs
Why the Automotive Software Landscape Demands Faster Integration
The shift toward software‑defined vehicles forces original equipment manufacturers (OEMs) and Tier‑1 suppliers to compress development cycles while preserving functional safety (ISO 26262) and quality standards. Traditional Classic AUTOSAR projects can consume 12–18 months of integration effort before any application code is written. The EB‑Microchip partnership tackles this bottleneck by delivering a ready‑made AUTOSAR Microcontroller Abstraction Layer (MCAL) that plugs directly into Microchip’s automotive microcontrollers.
Core Components of the Joint Solution
EB tresos AUTOSAR Portfolio
- EB tresos Studio: Graphical configuration of BSW modules, automatic generation of C‑code compliant with AUTOSAR 4.3.
- Integration‑as‑Code Engine: Encodes repeatable integration steps into version‑controlled scripts, enabling CI/CD pipelines for ECU software.
Microchip Automotive Hardware Platform
| MCU Family | Core | Max Clock | Flash / RAM | Safety Features | AUTOSAR Support |
|---|---|---|---|---|---|
| PIC32MZ EF | MIPS‑32 M‑Class | 200 MHz | 512 KB Flash / 128 KB RAM | Dual‑core lockstep, ECC | Classic AUTOSAR (MCAL) |
| SAM V71 | ARM Cortex‑R5 | 300 MHz | 2 MB Flash / 384 KB RAM | Safety‑island, lockstep, CRC | Classic AUTOSAR (MCAL) |
| AVR‑XMEGA AU | AVR‑8 | 32 MHz | 256 KB Flash / 16 KB RAM | Watchdog, lockstep | Classic AUTOSAR (MCAL) |
All three families meet ISO 26262 ASIL‑B requirements; the SAM V71 can be qualified up to ASIL‑D with additional safety IP.
Automation‑First Workflow
- Project bootstrap: EB’s integration‑as‑code scripts pull the appropriate MCAL package for the selected MCU and generate a baseline AUTOSAR configuration.
- Continuous validation: Automated unit‑test generation and static analysis run on every commit, catching integration regressions early.
- Scalable deployment: The same code base can be re‑targeted across the three MCU families with only parameter changes, accelerating portfolio diversification.
This approach not only trims manual effort but also creates a reproducible artifact set that can be fed into future AI‑driven configuration tools—an early step toward model‑based code synthesis.
Benefits for OEMs and Tier‑1 Suppliers
| Benefit | Traditional AUTOSAR | EB + Microchip Solution |
|---|---|---|
| Integration time | 12–18 months | 8–12 months (≈30 % reduction) |
| Project risk | High – many manual steps | Low – scripted, version‑controlled |
| Scalability | Limited to single MCU | Multi‑MCU family reuse |
| Safety certification effort | Separate per MCU | Consolidated MCAL package, shared safety IP |
| Future‑proofing | Manual updates needed | Automation ready for AI‑assist |
Real‑World Impact
Early adopters report that the pre‑integrated MCAL reduces “bring‑up” cycles from weeks to days. For a midsize sedan ECU targeting a 48 V power‑train, the combined stack shaved 4 weeks off the schedule, allowing engineering resources to focus on advanced driver‑assist features rather than low‑level driver code.
Bottom Line
Elektrobit’s proven EB tresos AUTOSAR tools paired with Microchip’s automotive‑grade MCUs deliver a turnkey, automation‑centric solution that accelerates Classic AUTOSAR integration by roughly a third while preserving safety and scalability. For OEMs and Tier‑1 suppliers racing to launch software‑defined vehicles, the partnership offers a practical shortcut to a production‑ready software foundation—freeing engineers to concentrate on differentiation rather than integration.
