Automotive Driver Assistance C Programming
Budget: $30 – $250 USD
I’m working on an embedded driver-assistance module for an automotive platform and need a seasoned C programmer to turn my high-level specs into lean, real-time code. The task revolves around low-level, bare-metal development: you’ll be reading sensor inputs, performing time-critical processing, and publishing results over the vehicle bus. Robustness matters more than flashy features—latency must stay predictable, memory usage tight, and the code base clean enough for future MISRA-style audits.
You should be comfortable with typical automotive toolchains (GCC-arm or equivalent), hardware debuggers, and communication protocols such as CAN. If you normally scaffold unit tests with Ceedling or similar, that’s a plus; I’d like at least a minimal test harness to verify core logic on the bench before we move to hardware-in-the-loop.
Deliverables:
• Well-commented C source and header files that compile without warnings.
• Simple makefile (or CMake) and build notes.
• A lightweight test suite demonstrating the key driver-assistance routines.
• Concise README outlining configuration, flash procedure, and known limitations.
I’ll share pin maps and timing requirements once we start. If you enjoy squeezing maximum performance out of microcontrollers while keeping the code easy to audit, let’s talk.
You should be comfortable with typical automotive toolchains (GCC-arm or equivalent), hardware debuggers, and communication protocols such as CAN. If you normally scaffold unit tests with Ceedling or similar, that’s a plus; I’d like at least a minimal test harness to verify core logic on the bench before we move to hardware-in-the-loop.
Deliverables:
• Well-commented C source and header files that compile without warnings.
• Simple makefile (or CMake) and build notes.
• A lightweight test suite demonstrating the key driver-assistance routines.
• Concise README outlining configuration, flash procedure, and known limitations.
I’ll share pin maps and timing requirements once we start. If you enjoy squeezing maximum performance out of microcontrollers while keeping the code easy to audit, let’s talk.