Service · automotive software engineering
Your engineering partner for software-defined vehicle development.
We work alongside your team across the software-defined vehicle: integrating AUTOSAR on embedded ECUs and software platforms on high-performance computers, developing application software and complex device drivers, and carrying the work through integration, testing and validation.
- AUTOSAR Classic · HPC platforms
- Application SWCs · CDDs
- Automotive Ethernet · TSN · MACsec
- Secure boot · OTA
- SIL · HIL test engineering
- Agentic workflow engineering
ECU software platform · who owns which layer
- Applicationyour SWCs · your services
- RTE · middlewareRTE · ara::com · SOME/IP · DDS
- ServicesDcm · Dem · NvM · Csm · KeyM · IdsM · WDG · E2E
- CommunicationCAN/CAN FD · Ethernet (DoIP, SOME/IP, SD) · MACsec · TSN
- OS · MCAL · LinuxAUTOSAR OS · Yocto · hypervisor
- Bootloadersecure boot · UDS 0x34–0x37 · A/B update
- Hardware · HSMyour MCU, your HSM
our scope yours
The work
Basic software, application software and test benches, in your repository and your process.
The basic software, the communication stacks, the bootloader and the safety and security mechanisms have to be configured, integrated with the MCAL of the chosen controller, kept consistent across variants and maintained for the life of the product. Application software and complex device drivers have to be specified, implemented and released on that platform, and the whole has to be verified on the bench. We take on any of these parts or all of them, with the vendor platforms you have chosen and in your repository.
Our own products are built this way: the CCM-EV charging stacks are complex device drivers and AUTOSAR modules on customer platforms, the security assets integrate with vendor Dcm and crypto stacks, and both are verified with UCAN Studio on the bench.
What we take on
Scope of the service.
Application software and complex device drivers
Software components and CDDs from specification to release on your platform: communication and diagnostic functions, protocol applications, safety and security mechanisms, hardware-close drivers.
- SWCs against your architecture and interfaces
- Complex device drivers where the platform ends, the way our CCM-EV stacks are built
- MISRA C:2012, unit and integration tests, reviews in your process
Agentic workflow engineering
Connect engineering intent, execution and evidence.
We apply agentic automation where it strengthens automotive software development: carrying context across code, configuration, simulation, stimulation, diagnostics, test and trace, and connecting the surrounding repositories, CI, requirements and bench services. Changes remain reviewable, external actions permission-controlled and conclusions grounded in evidence.
Continuity across development and validation
Carry project context across development, integration and validation instead of reconstructing it at every handoff.
- Code and configuration stay connected to the run
- Reports, traces and logs remain attached to conclusions
- The next iteration starts from the evidence of the last
Automotive Ethernet
Ethernet stacks from the PHY to the secured, scheduled frame.
Physical layer
MAC, PHY and switch drivers for 10BASE-T1S and 10/100/1000BASE-T1, including external MAC-PHY and automotive switch chips.
Secure communication
IEEE 802.1AE MACsec with MKA, TLS 1.2 and 1.3 with PSK or certificates, hardware-accelerated cryptography on security modules and HSMs.
Time-sensitive networking
IEEE 802.1AS-Rev gPTP, 802.1Qbv scheduled traffic, 802.1Qbu frame preemption, 802.1CB frame replication for deterministic communication.
Bootloader
Secure boot and software update, integrated and hardened.
Secure boot
Signature verification with ECDSA/RSA, HSM-protected keys, secure key provisioning, runtime attestation, multi-stage boot on a hardware root of trust, MPU/MMU memory protection, measured boot on Linux, anti-rollback with secure counters.
Software update
Bootloader with cryptographic verification chains; UDS 0x34/0x35/0x36/0x37 per ISO 14229-1; OEM download protocols; delta updates; A/B dual-bank with fallback; error recovery with integrity checks; partial updates on constrained MCUs; campaign management.
Process and quality
Automotive-grade process, with requirements, design and tests as code.
Standards-compliant
Automotive SPICE level 2, ISO 26262 compatibility for safety-related elements; MISRA C:2012 and CERT C static analysis; coverage including MC/DC; hazard analysis and risk assessment for safety features.
Requirements, design and tests as code
Traceability generated from the repository; baseline and variant management with variant recipes as code; unit, integration and system tests automated at every level.
Tooling and CI
Pipelines built for automotive integration and configuration workflows, quality gates per stage, and hardware-in-the-loop automation with UCAN Studio for system-level validation.
Maintenance
Long-term support for deployed platforms.
Maintenance engineering
Security patches, bug fixes and compatibility updates for changing hardware and toolchains, with full regression testing.
Production support
Tiered L1–L3 support with defined SLAs: diagnostics, root-cause analysis, issue reproduction, field fixes for critical defects.
Feature evolution
Planned platform evolution: new features, updated security protocols, adaptation to new ISO and SAE standards with validation and compliance testing.
How an engagement runs
How an engagement runs.
- 01
Assess
Platform, vendors, controller, variants, process constraints; the state of the current integration.
- 02
Plan
Integration plan with baselines and quality gates; responsibilities between your application team and ours.
- 03
Integrate
Configuration, integration and custom development in your repository and toolchain, with CI and tests as code from the first baseline.
- 04
Maintain
Handover with documentation, then maintenance and support at the agreed level for the life of the platform.
Platforms
Classic AUTOSAR on the microcontroller, HPC platforms on the central computer.
Configuration and integration of the platforms you have chosen: vendor AUTOSAR Classic stacks on the ECU, and on the high-performance computer AUTOSAR Adaptive, Eclipse S-CORE, embedded Linux and the middleware between them.
Classic AUTOSAR integration
Configuration and integration of third-party Classic platforms with your ECU software, tuned for the resources of the controller.
- OEM AUTOSAR system, DEXT and SECXT integration
- Ethernet stacks with DoIP, SOME/IP and SD
- Crypto stack modules: Csm, KeyM, IdsM, HSM
- CAN / CAN FD communication stack
- Memory stack for data flash and EEPROM
- Safety mechanisms: WDG, E2E protection
- Vehicle diagnostics: UDS, OBD-II, J1939
- MCAL integration for NXP, Infineon, Renesas and other targets
- OEM utility and middleware components
- RTE and OS configuration and optimisation
- Custom SWCs and complex device drivers
HPC platform integration
Integration of the software platform on high-performance computers and zone controllers: AUTOSAR Adaptive where it is chosen, Eclipse S-CORE and embedded Linux where it is not, and the middleware that connects them to the Classic ECUs.
- AUTOSAR Adaptive: ara::com, execution and state management, IAM, persistency
- Eclipse S-CORE and other open-source SDV platforms
- Embedded Linux (Yocto) and POSIX RTOS integration, board support and system images
- Hypervisors and mixed-criticality partitioning: safety and real-time next to compute
- Service-oriented middleware: SOME/IP, DDS, service discovery, signal-to-service gateways to Classic ECUs
- Container and orchestration runtimes for application deployment on the HPC
- Security frameworks: identity and access management, secure boot chain, crypto services
- Resource management for multi-core, multi-process applications; runtime measurement and performance optimisation
- Over-the-air update integration for HPC software
Demo · 30 minutes · online
Request a demo of the HIL bench we validate ECU software on
A 30-minute screen-share with an Alefbits engineer: an ECU integration validated on the bench: communication stack, diagnostics and a bootloader update sequence exercised with UCAN Studio, with the traces. You choose a slot in the calendar or send the form and we propose two.
Request a demoEngagement
Scope the work
Tell us the ECU, the platform and vendor, what is to be built or tested and where the project stands. An engineer answers with an assessment proposal.
Contact us