MCU BSP ENGINEER

ROLE PURPOSE

The main function of this role is to develop, configure, integrate, and debug MCU Board Support Package (BSP) and AUTOSAR Classic basic software for automotive Electronic Control Units (ECUs). The engineer will take full responsibility for OS, Microcontroller Abstraction Layer (MCAL), power management, Complex Device Driver (CDD), and I/O Hardware Abstraction (IoHwAb) tasks from the analysis of requirements through to integration and validation in real-world applications.

KEY RESPONSIBILITIES

• Develop and integrate MCU BSP software, including startup code, linker configurations, memory mapping, interrupt handling, clock initialization, reset handling, and peripheral bring-up.

• Configure and integrate AUTOSAR OS, addressing tasks, events, alarms, counters, schedule tables, resources, ISR mapping, timing protections, and multicore considerations as necessary.

• Configure and validate MCAL modules (e.g., Port, Dio, ADC, PWM, GPT, ICU, SPI, CAN, LIN, WDG, MCU, Flash, Fee) based on ECU hardware designs.

• Implement ECU power management strategies, including ignition transitions, wake-up sources, sleep entry and exit, shutdown, reset, watchdog supervision, and low-power state validation.

• Design and develop CDDs for hardware or functions not provided by standard AUTOSAR modules, ensuring clean interfaces to RTE, BSW, and application software.

• Develop and configure IoHwAb components to abstract I/O devices from upper software layers.

• Carry out board bring-up and hardware-software integration using tools such as debugging traces and analyzers.

• Troubleshoot and resolve issues related to startup, timing, interrupts, memory, communication, and driver functionality on the target ECU.

• Create and maintain documentation including software requirements, design descriptions, and verification evidence.

• Collaborate with various teams (hardware, system, diagnostics, etc.) to resolve cross-domain issues.

TECHNICAL SKILLS - MAPPED TO THE ROLE

Programming: Embedded C, C, basic Python or scripting; MISRA C and static-analysis awareness.

MCU / BSP: Startup code, linker scripts, vector tables, memory maps, interrupts, peripheral bring-up.

AUTOSAR OS: Tasks, ISRs, events, resources, alarms, application partitioning.

MCAL: Mcu, Port, Dio, ADC, PWM, and other vendor-specific drivers.

Power Management: EcuM, BswM, and low-power modes handling.

CDD / IoHwAb: CDD design, sensor and actuator abstraction.

Communication: CAN/CAN-FD, LIN, SPI, I2C, UART; Ethernet experience is a plus.

Debug & Test: Trace32, CANoe, or similar tools; skills in debugging and testing integration.

AUTOSAR Tools: Experience with DaVinci Configurator/Developer, EB tresos, or similar tools.

Process & Quality: Familiarity with V-Model, ASPICE, unit and integration testing.

Version & Build: Experience with version control systems and build processes.

REQUIRED EXPERIENCE AND COMPETENCIES

• 5 to 7 years of automotive embedded-software experience, with 3 years specifically in relevant areas.

• Strong understanding of MCU architecture and real-time behavior.

• Hands-on AUTOSAR Classic experience, ideally with specific automotive MCUs.

• Ability to interpret schematics and datasheets, translating hardware into software behaviors.

• Strong debugging skills with a disciplined approach to analysis.

• Capability to work independently across all project areas.

PREFERRED QUALIFICATIONS

• Experience with multicore MCUs and related technologies.

• Knowledge of functional safety standards like ISO 26262.

• Familiarity with ECU peripherals and actuator-control technologies.

• Understanding of diagnostic integration and communication stacks.