Key Takeaways
- Elektrobit (EB) ve Microchip, Microchip’in otomotiv-grade mikrodenetleyicileri üzerinde çalışan ön-entegrasyonlu bir AUTOSAR yığını sunmak için ortaklık kurdu.
- Ortak çözüm, erken benimseyenlere göre tipik Classic AUTOSAR entegrasyon süresini 8-12 haftadan 3-5 haftaya düşürüyor.
- Otomasyon-öncelikli araçlar (integration-as-code) manuel çabayı ≈ %70 azaltıyor ve entegrasyon-ile ilgili kusurları ≈ %40 düşürüyor.
- Güvenlik-kritik ISO 26262-uyumlu MCAL ve BSW bileşenleri kutudan çıktığı gibi sağlanıyor, OEM ve Tier-1 tedarikçileri için sertifikasyon yollarını kolaylaştırıyor.
Why the Automotive Software Landscape Demands Faster AUTOSAR Development
The shift toward software-defined vehicles (SDVs) has forced original equipment manufacturers (OEMs) and Tier-1 suppliers to compress development cycles while preserving functional safety (ISO 26262 ASIL A-D) and functional integrity. Traditional Classic AUTOSAR projects typically involve:
| Aspect | Conventional AUTOSAR Integration | EB + Microchip Pre-Integrated Stack |
|---|---|---|
| Integration time | 8 – 12 weeks (manual MCAL/BSW setup) | 3 – 5 weeks (automation-driven) |
| Manual code changes | 200 + lines per ECU on average | < 50 lines (generated) |
| Defect rate | 1.2 defects/1 kLOC | 0.7 defects/1 kLOC |
| Certification effort | Separate MCAL qualification | MCAL already ISO 26262-rated |
| Scalability | Linear with engineer headcount | Near-linear with automation scripts |
Sources: internal benchmark data from early-access customers (Q2 2026).
The Core of the Collaboration
Microchip Automotive Hardware Platforms
- PIC32MZ-EF and SAMD5x-E5x families, featuring up to 400 MHz cores, 2 MB flash, and 512 KB RAM.
- Integrated safety-critical peripherals (dual-CAN FD, Ethernet, LIN) with ASIL-B compliance out of the box.
- Support for AUTOSAR Adaptive as well as Classic profiles, enabling a migration path for future-proof ECUs.
Elektrobit’s EB tresos Portfolio
- EB tresos Classic provides a fully certified Microcontroller Abstraction Layer (MCAL), Basic Software (BSW), and RTE generator.
- Integration-as-Code framework turns repetitive configuration steps into version-controlled scripts (Git-compatible).
- Toolchain includes EB Configurator, EB Generator, and EB Automation Server for continuous integration (CI) pipelines.
How the Joint Solution Accelerates Development
- Pre-Integrated MCAL & BSW – Developers receive a ready-made AUTOSAR-compliant MCAL that matches the selected Microchip MCU, eliminating the 2-week “bring-up” phase.
- Automation-First Workflow – EB’s integration-as-code scripts automatically generate RTE files, perform static analysis, and run unit tests on each commit, cutting manual validation time by up to 70 %.
- Single-Source Traceability – All configuration artifacts are stored in a unified repository, satisfying ISO 26262 traceability requirements without extra documentation effort.
- Scalable CI/CD – The solution plugs into Jenkins, Azure DevOps, or GitLab CI, allowing multiple ECU projects to be built in parallel on shared hardware farms.
Real-World Impact
A Tier-1 supplier reported that a high-volume power-train ECU (12 MB flash, 2 MB RAM) moved from concept to production in 4 months, compared with the typical 7-month timeline. The same project achieved ISO 26262 ASIL-C certification with 30 % fewer safety case artifacts, thanks to the pre-qualified MCAL.
Future Outlook
Both companies have announced a roadmap that will extend the partnership to AUTOSAR Adaptive and over-the-air (OTA) update frameworks by Q2 2027, targeting high-performance compute nodes for ADAS and autonomous driving.
Bottom Line
Elektrobit’s EB tresos suite combined with Microchip’s automotive microcontrollers delivers a production-ready AUTOSAR foundation that slashes integration time, reduces defect rates, and eases safety certification. For OEMs and Tier-1 suppliers racing to launch SDVs, the partnership offers a tangible shortcut from silicon to software-defined vehicle features, while preserving the rigor required for automotive safety standards.
