Embedded implementation
Develop embedded C and C++ software, with Assembly where required, for bare-metal or RTOS-based systems.
Capability
Embedded Software & Platform Engineering
Build the low-level software and platform foundations that connect embedded hardware to product behaviour.
The scope can start with a driver or platform issue and extend to embedded software architecture and implementation across a subsystem. Platform choices, timing constraints, integration responsibilities and component-level evidence are defined around the assignment.
When to involve CEVOLARION
New hardware needs platform software and drivers before application development can proceed.
An embedded platform change affects timing, configuration or multicore integration.
A bootloader, software component or customer-specific platform adaptation needs defined implementation and verification responsibility.
Focus topics
Recurring types of work within this capability, described in more depth.
AUTOSAR IntegrationBasic software, RTE and MCAL configuration and integration for AUTOSAR-based control units.Bootloader & Firmware UpdateStart-up, image validation and update mechanisms for embedded devices and control units.BSP & Device DriversBoard support, low-level drivers and hardware abstraction for new or changed embedded hardware.
Engineering scope
The agreed assignment determines which activities are included and where the responsibility boundary sits.
BSP, drivers and hardware abstraction
Develop board-support and platform software, low-level drivers and hardware abstraction in coordination with hardware interfaces and bring-up needs.
Architecture and platform configuration
Define embedded software architecture and integrate platform configuration, including multicore platform integration where relevant.
Boot and update mechanisms
Develop or integrate bootloader and update mechanisms within the product platform and agreed release constraints.
Automotive platform work
Support AUTOSAR-related BSW, RTE, MCAL and configuration work where the assignment and selected platform support it.
Build and component verification
Connect software to its build, configuration and toolchain baseline, with unit or component testing support for the implemented scope.
Interfaces to adjacent disciplines
Electronics & Hardware Engineering
Align low-level software with hardware behaviour, pin allocation and prototype findings.
Connectivity, Diagnostics & Interfaces
Integrate communication configuration and interface behaviour into the embedded platform.
System & Software Integration
Supply software and configuration baselines that can be combined and verified at system level.
Example engineering outputs
Outputs are assignment-dependent and agreed for each engagement.
Embedded software components, drivers and board-support software.
Software architecture and platform configuration records.
Bootloader or update integration work products.
Build/configuration baselines and unit or component test results.
Methods and engineering environment
Embedded C / C++, with Assembly where needed.
Bare-metal and RTOS-based development, BSP and hardware abstraction.
AUTOSAR BSW / RTE / MCAL configuration where applicable to the agreed platform.
Component testing and configuration-controlled platform integration.
Where this discipline connects
Highlighted stages indicate typical connections. The actual entry point and scope follow the product and assignment.
Define
Clarify the problem, requirements and responsibility boundary.
Architect
Allocate functions and define system and discipline interfaces.
Develop
Implement electronics, platform and embedded software.
Integrate
Bring components, configurations and interfaces into a working baseline.
Verify & Qualify
Evaluate behaviour and assemble the agreed engineering evidence.
Release & Deploy
Prepare the release, production support and technical handover.
Evolve & Tailor
Maintain, adapt and control change across variants and product life.
Delivered at the scale of the work
This capability can contribute to specialist work, an Engineering Cell, a Defined Work Package or an agreed Managed Service. The collaboration model and partnership tier are separate decisions.
Discuss an embedded software, platform or low-level integration scope.
Describe the current state, the interfaces involved and the result you need. Leave confidential technical files out of the first message.