Visualization of embedded ECUs in a car, illustrating Piaxo’s software integration layers

Embedded Software

AUTOMOTIVE

  • Embedded development from MCAL to Basic Software, RTE, and Application layers

  • Configuration and integration of Classic and Adaptive AUTOSAR stacks

  • Testing expertise across unit, integration, and qualification levels using Tessy, GoogleTest, and CANoe

  • Proficient with toolchains from Vector, Elektrobit, Simulink, Polarion, Jira, and others

  • Compliance with ISO 26262 (functional safety) and ISO/SAE 21434 (cybersecurity)

  • Experienced with single-core and multi-core processors from NXP, Renesas, Nvidia, Infineon, and more

Projects
Resources
Careers

Software Development Phase

SWE.1 Requirements Elicitation

SWE.1 focuses on translating system requirements into a clear, structured set of software requirements. This involves understanding client expectations, safety concepts, functional goals (such as those from ADAS or infotainment systems), and non-functional goals, then creating a traceable and verifiable set of software-specific requirements.

We ensure that all software requirements are fully aligned with the system architecture and safety standards, including ISO 26262, where applicable. Using requirements management tools (IBM DOORS, Polarion, Jama) and modeling standards (SysML, Drawio, IBM Raspberry), our engineers define what the software must do, forming the backbone for downstream development activities.

SWE.2 Software Architectural Design

SWE.2 defines the software architecture, detailing components, interfaces, and their interactions within the embedded system. It includes dynamic behavior via activity, sequence, and state diagrams. Platform constraints, memory, CPU, and Ethernet usage targets are set alongside non-functional goals like modularity and timing.

Piaxo applies its Classic and Adaptive AUTOSAR expertise to design scalable, reusable architectures that ensure traceability, ASPICE compliance, and safety in complex systems like EVs and ADAS.

SWE.3 Detailed Design and Unit Construction

SWE.3 translates the architecture into detailed design specifications and actual code. Each software unit is defined with internal logic, data types, algorithms, and control flows—followed by implementation in accordance with MISRA C or equivalent coding standards.

Piaxo engineers apply model-based design (Simulink, TargetLink) and static code analysis to ensure quality early in development. This is where control algorithms, diagnostics, and communication stacks come to life, especially in performance-critical modules such as BMS, MCAL layers, or sensor fusion engines.

SWE.1 to SWE.6 V-cycle diagram showing Piaxo’s ASPICE-aligned software development and testing process

Software Testing Phase

SWE.4 Unit Verification

SWE.4 ensures that every software unit works as intended before integration. Verification here is mostly static and component-level, including peer reviews, unit tests, and code coverage analysis.

Piaxo executes these activities using tools like VectorCAST, Tessy and GoogleTest, ensuring compliance with coverage criteria (e.g. MC/DC for safety-critical components) and detecting defects early. This stage is essential for clean builds and high maturity ratings in ASPICE assessments, especially when targeting TISAX Level 3 or ISO 26262 ASIL-C/D environments.

SWE.5 Integration Test

SWE.5 focuses on assembling software units into subsystems or the complete software product. Integration testing validates that interfaces work correctly and that control logic performs as designed in combination.

Piaxo’s teams use continuous integration pipelines and test automation with tools like Jenkins, GitLab CI/CD, and CANoe to reduce regression risk and improve delivery speed. We validate data flows, communication stacks (CAN, LIN, Ethernet), and real-time behavior at this level, which is especially relevant for automotive domains, such as ECUs handling powertrain, ADAS, or body control.

SWE.6 Qualification Test

SWE.6 represents the final verification stage where the integrated software is validated against its original requirements under operational conditions. These qualification tests simulate vehicle-level conditions using test benches, HiL systems, or on-road scenarios. Piaxo conducts complete qualification campaigns including robustness, fault injection, and interface compliance testing.

Our teams ensure full traceability from test cases back to requirements. We frequently collaborate with OEMs during vehicle bring-up phases, especially on critical modules for hybrid ECUs, cybersecurity features, or OTA update systems.

Software
Development & Testing

Piaxo has experience with all in car ECUs, from Powertrain to Entertainment, and can bring added value in a specific part of the product development with individual expertise or complete product development, including support in obtaining ASPICEaccreditation.

Our engineering team has deep knowledge with leading tool chains, from Vector to OEM specific and semiconductor from NXP, Nvidia, Infineon and others. Whether it’s an AUTOSAR project, ASIL D or a multi-core processor, we harness the power of these cutting-edge technologies to design versatile and high-performance solutions.

Projects
Partnership Options
Careers

Skills

We like to think of our team as the cool hero in a movie, swooping in with expertise, skills and tools to save the day, ensuring every project’s success.

Check below to see what our standard engineer CV looks like.

Piaxo engineers presented as a skilled and confident team, emphasizing expertise and professionalism

Our individual resources

    • Years of Experience: 8-12 years

    • Knowledge: Proficient in requirements engineering, analysis, and management

    • Tools: Skilled in using IBM Doors, Polarion, and other requirements management tools

    • Methodologies: Experienced in Agile and Waterfall methodologies

    • Standards: Familiar with ASPICE and ISO 26262 standards

    • Years of Experience: 8-12 years

    • Knowledge: Expert in software design patterns, architecture models, and system optimization

    • Tools: Proficient with UML, Enterprise Architect, and similar architectural tools

    • Methodologies: Skilled in Agile, DevOps, and Microservices architecture

    • Standards: In-depth understanding of AUTOSAR and ISO 26262

    • Years of Experience: 8-12 years

    • Skills: Application layer development, real-time operating systems, Real-Time Environment (RTE) configuration, optimization

    • Tools: Proficient in C/C++, Python, MATLAB/Simulink

    • Standards: Knowledge of ISO 26262

    • Years of Experience: 8-12 years

    • Skills: Software integration, build management, configuration control

    • Tools: Experience with CI/CD tools, Git, Jenkins

    • Standards: Familiarity with AUTOSAR guidelines

    • Years of Experience: 8-12 years

    • Skills: Communication stack development (CAN, LIN, Ethernet)

    • Tools: Vector tools, AUTOSAR development environments

    • Standards: AUTOSAR and ISO 26262

    • Modules: Com, PduR, CanIf / LinIf / EthIf, CanTp / LinTp / SoAd

    • Years of Experience: 8-12 years

    • Skills: Diagnostic software development, UDS protocols

    • Tools: AUTOSAR Diagnostic tools, CANdelaStudio

    • Standards: ISO 14229, AUTOSAR

    • Modules: DCM, DEM, NvM

    • Years of Experience: 8-12 years

    • Skills: System services, ECU state management

    • Tools: AUTOSAR system tools, C/C++

    • Standards: Compliance with AUTOSAR and ISO 26262

    • Modules: OS, EcuM, BswM, ComM, WdgM

    • Years of Experience: 8-12 years

    • Skills: Memory management, NVRAM services

    • Tools: AUTOSAR memory stack tools

    • Standards: AUTOSAR compliance

    • Modules: NvM. Fee, Fls, Eep

    • Years of Experience: 8-12 years

    • Skills: I/O hardware abstraction, sensor integration

    • Tools: AUTOSAR I/O stack tools

    • Standards: Adherence to AUTOSAR guidelines

    • Modules:

      • MCAL: DIO, PORT, PWM, SPI, Adc

      • ECUAL: DioIf, PortIf, PwmIf, SpiIf, AdcIf

    • Years of Experience: 8–12 years

    • Skills: Test case design, execution, and automation; Hardware-in-the-Loop (HIL), Software-in-the-Loop (SIL), and Model-in-the-Loop (MIL) testing; debugging, defect tracking, and regression testing

    • Tools: Proficient with Vector tools (CANoe, CANape), dSPACE, Jenkins, Python, and test automation frameworks

    • Methodologies: Experienced in functional, integration, and system testing within the V-model, Agile, and Waterfall frameworks

    • Standards: Strong knowledge of ISO 26262, ISTQB principles, and ASPICE testing processes