I will migrate your embedded firmware between rtos sdks and refactor its architecture

Firmware that started as a quick prototype tends to calcify into blocking loops and tangled globals and migrating it to a different RTOS or SDK only makes the mess more visible. I refactor firmware into modular, non-blocking architectures (dedicated classes per responsibility, clean state machines) and port it across RTOS/SDK boundaries Zephyr, Pico SDK, FreeRTOS so it's something your team can actually extend later.

Features:

• RTOS/SDK migration (Zephyr, Pico SDK, FreeRTOS)
• Blocking-to-non-blocking state machine refactor
• Modular C++ class architecture design
• Driver porting across MCU families
• Build system setup (CMake/West)
• Code review and architecture documentation

What will you get:

• Migrated and/or refactored firmware source
• An architecture diagram and documentation
• Build instructions
• One round of revisions

Guarantee: Firmware that's easier to extend six months from now, not just code that compiles today.