MCU BSP ENGINEER

Develop, configure, integrate, and debug MCU Board Support Package and AUTOSAR Classic basic software for automotive ECUs. The engineer will own OS, MCAL, power-management, Complex Device Driver (CDD), and I/O Hardware Abstraction (IoHwAb) activities from requirements analysis through target integration and validation.

• Develop and integrate MCU BSP software, startup code, linker configuration, memory mapping, interrupt handling, clock initialization, reset handling, and peripheral bring-up.
• Configure and integrate AUTOSAR OS, including tasks, events, alarms, counters, schedule tables, resources, ISR mapping, timing protection, and multicore considerations where applicable.
• Configure and validate MCAL modules such as Port, Dio, Adc, Pwm, Gpt, Icu, Spi, Can, Lin, Wdg, Mcu, Fls, Fee, and related interfaces based on ECU hardware design.
• Implement ECU power-management behavior using EcuM and BswM concepts, 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 covered by standard AUTOSAR modules, with clean interfaces to RTE, BSW, and application software.
• Develop and configure IoHwAb components to abstract sensors, actuators, GPIO, PWM, ADC, pumps, valves, and other board-specific I/O from upper software layers.
• Perform board bring-up and hardware-software integration using schematics, datasheets, debugger traces, register inspection, oscilloscopes, logic analyzers, and bus analyzers.
• Analyze and resolve startup, timing, interrupt, memory, communication, power-state, watchdog, and peripheral-driver issues on the target ECU.
• Create and maintain software requirements, design descriptions, configuration specifications, interface documents, review records, and verification evidence.
• Collaborate with hardware, system, network, diagnostics, integration, application, safety, cybersecurity, and validation teams to close cross-domain issues.

Programming

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

MCU / BSP

Startup code, linker scripts, vector table, memory map, clock, reset, interrupts, cache/MPU, watchdog, peripheral bring-up

AUTOSAR OS

Tasks, ISRs, events, resources, alarms, counters, schedule tables, application partitioning, timing and stack analysis

MCAL

Mcu, Port, Dio, Adc, Pwm, Gpt, Icu, Spi, Can, Lin, Wdg, Fls, Fee and vendor-specific drivers

Power Management

EcuM, BswM, wake-up validation, sleep/shutdown, ignition states, reset strategy, low-power modes and watchdog handling

CDD / IoHwAb

CDD design, register-level drivers, sensor and actuator abstraction, ADC/PWM/GPIO mapping and RTE-facing interfaces

Communication

CAN/CAN-FD, LIN, SPI, I2C, UART; Ethernet exposure is an advantage

Debug & Test

Trace32/Lauterbach or equivalent, CANoe, oscilloscope, logic analyzer, JTAG, register and memory analysis

AUTOSAR Tools

DaVinci Configurator/Developer, EB tresos, Elektrobit or equivalent configuration and code-generation tools

Process & Quality

V-Model, ASPICE awareness, peer reviews, unit testing, integration testing, requirements traceability and change control

Version & Build

Git/GitHub/Gerrit or equivalent, CI awareness, compiler/linker toolchains and build troubleshooting

• 5 to 7 years of automotive embedded-software experience, with at least 3 years of relevant MCU BSP, MCAL, OS, power-management, CDD, or IoHwAb work.
• Strong understanding of MCU architecture, low-level drivers, hardware interfaces, memory, interrupts, timing, and real-time behavior.
• Hands-on AUTOSAR Classic configuration and integration experience, preferably on Infineon AURIX, NXP S32, Renesas RH850, ST, or an equivalent automotive MCU.
• Ability to read schematics and MCU datasheets and translate hardware design into software configuration and driver behavior.
• Strong target-debugging and root-cause-analysis skills, with disciplined use of logs, traces, measurements, and reproducible evidence.
• Ability to work independently across requirements, design, implementation, configuration, integration, review, and test activities.

• Experience with multicore MCUs, memory protection, functional watchdog concepts, bootloaders, secure boot, or over-the-air update dependencies.
• Exposure to ISO 26262 functional safety, cybersecurity engineering, and safety-oriented MCAL or complex-driver development.
• Experience with ECU peripherals and actuator-control products, including pumps, valves, sensors, motor control, or body/comfort ECUs.
• Knowledge of diagnostics, DEM/DCM integration, NVRAM, communication stacks, and MCU-to-SoC communication.

Bachelor's or Master's degree in Electronics, Electrical Engineering, Computer Science, Embedded Systems, or a related discipline. Equivalent relevant automotive embedded-software experience may also be considered.

• Configured and integrated OS/MCAL/BSW modules with reproducible generation and build baselines.
• Board bring-up evidence, verified power-state transitions, validated peripheral behavior, and resolved target issues.
• CDD and IoHwAb components with reviewed interfaces, implementation, tests, and traceability.
• Clear technical documentation, configuration notes, release inputs, known limitations, and validation evidence.