Dual-MCU CMake Porting
$8-15 USD / hour
Posted 1 minute ago
•
Ends in 6 days
$8-15 USD / hour
I already have a CMake-based firmware project running on one STM microcontroller, and I’m ready to extend it to a second MCU from a different chip family. Both devices must remain fully supported after the port. Here is what we will tackle together during one or two focused remote sessions (screen-share / pair-programming): • Update the CMake build system so that Visual Studio Code offers a clean dropdown (or other selectable build profile) letting me switch targets instantly. • Adapt and, where necessary, split startup files, linker scripts, and low-level hardware setup to satisfy each chip’s memory map and peripheral layout. • Keep the application codebase unified, isolating any processor-specific differences behind clear CMake options or source folders. I’m looking for someone fluent in modern CMake, STM toolchains, and VS Code’s CMake Tools extension who enjoys teaching while coding. We’ll walk through every change together so I can understand and maintain the solution myself. By the end of our sessions I expect: 1. A repository that builds cleanly for both MCUs from the same command palette dropdown. 2. Updated linker scripts, startup code, and conditional source files committed and explained. 3. Clear documentation of any new CMake variables or targets we introduce. If you’re comfortable sharing your screen, guiding step-by-step, and moving quickly, let’s schedule the time and get it done.
Project ID: 40817446
About the project
9 proposals
Open for bidding
Remote project
Active 5 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
9 freelancers are bidding on average $16 USD/hour for this job


Hi, I understand you need one CMake firmware repository to support two STM microcontrollers, with an easy target switch in VS Code. I can work with you in focused screen-sharing sessions to organize CMake profiles, separate startup files and linker scripts, and keep the shared application code clean. I’ll isolate MCU-specific code in clear source folders and options, verify clean builds for both targets, and explain each C Programming and Microcontroller change as we go. The final repository will include the updated Electronics setup, documented variables, and simple build instructions. Which exact STM MCU families, toolchain files, and current CMake presets or build profiles are already used in the repository? Please start the chat and let’s discuss your current CMake structure and MCU details.


Hello, My 10+ years of embedded-systems and STM32 experience make me well suited to porting your CMake firmware across two STM MCU families while keeping the application unified. I understand the hardware differences behind startup code, memory maps, linker scripts, peripherals, and processor-specific low-level setup, not just the build configuration. My background spans industrial electronics, automation, controllers, sensors, ADC systems, I2C, UART, and complete product development from schematic through testing and commissioning. Combined with my Embedded Systems and STM32 skills, this allows me to connect the CMake structure to the actual target hardware and clearly isolate MCU-specific files and options. I am comfortable working collaboratively through screen sharing and explaining changes as they are made, so you can maintain the repository confidently afterward. I would be glad to help establish clean VS Code target selection, reliable builds for both MCUs, and clear documentation of the new CMake structure. Thanks!


My 8+ years in embedded systems and firmware development make me well suited to porting your CMake-based STM firmware while keeping both MCU targets maintainable. I work in C and embedded environments, with hands-on experience integrating microcontrollers into robust hardware systems and carrying projects through implementation, testing, troubleshooting, and documentation. My background in electronics and microcontroller development is especially relevant to separating processor-specific startup, hardware configuration, memory-related settings, and peripheral differences without unnecessarily duplicating the application. I also bring strong system-integration and troubleshooting skills, which are valuable when validating that each target builds and operates correctly within the same project structure. During the remote sessions, I can explain the changes clearly as we work so the resulting configuration remains understandable and maintainable. I would be glad to guide this porting work collaboratively and help you finish with a clean dual-target firmware project and documented CMake setup.


Hi there, Could you share which STM32 families are involved, and whether the second target needs different HAL or bare-metal startup code? Also, do you want one VS Code kit per MCU, or a single dropdown that switches linker script, startup, and defines together? The main challenge is keeping one firmware tree clean while letting CMake generate two correct builds. A good approach is to split target-specific files into small source groups, then drive compiler flags, linker scripts, and startup objects from CMake presets or CMake Tools build variants. The risky part is hidden chip differences in clock setup, RAM layout, interrupt vectors, or peripheral init order. That is usually handled by making the MCU layer explicit early, then validating each build with a full clean compile and a quick flash test before merging shared code paths. During the session, we can wire the dropdown in VS Code, update the toolchain logic, and leave the project with clear variables and comments so the setup is easy to maintain. If the scope stays focused, this should fit well into one or two screen-share sessions. Best, Hlib


✅ Hi There✅ , Good morning! I am skilled engineer with skills including Embedded Systems, Microcontroller, Electronics, STM32, Firmware Development and C Programming. Recently, I've done similar project so I am very confident to start your project. I can review your project requirements, understand the technical challenges, and develop a practical and cost-effective solution that meets your specifications. I focus on accuracy, quality, clear communication, and delivering work within the agreed timeline. I would be happy to discuss your project in more detail, understand your expectations, and explain how I can contribute to its successful completion. Please message me here so we can discuss the details. Best regards,
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗