Senior Embedded Firmware Engineer Needed

@Mahihassi

As a seasoned electrical engineer, I bring extensive experience in all facets of embedded systems, including the specific skills you require for this project. My proficiency with embedded C, RTOS like FreeRTOS/ThreadX, and protocols such as SPI, I²C, UART/RS-422, Ethernet/TCP-IP aligns perfectly with your needs. I have deep knowledge of Git for source control which will be instrumental in managing revisions and coordinating multi-developer workflows. Moreover, having worked on platforms like ColdFire processors and MQX RTOS, I am familiar with legacy system architectures and can quickly adapt to existing codebases. My understanding of hardware bring-up will enable me to seamlessly integrate new components while developing production-quality firmware. In addition to my technical proficiency, my dedication towards complete product engineering is an invaluable asset. Starting from system architecture and schematics through firmware development, PCB design to IoT connectivity and full-stack software development including web and mobile apps - I can provide a holistic solution. Considering my skills, experience, and prowess in working with legacy hardware platforms, selecting me would ensure a reliable and efficient continuation to your existing embedded firmware platform while incorporating necessary updates. Let's connect to discuss your project requirements further! Best, sardar (ceo MHTechFusion)

@MuhammadUzair16

Hi, I am an embedded systems engineer with over 16 years of experience developing and extending production firmware for commercial products. Much of my work has involved taking ownership of established embedded C codebases, tracing legacy architectures, and adapting them to new board revisions without disrupting proven functionality. I have hands-on experience with RTOS-based systems, board bring-up, bootloaders and field updates, Ethernet/TCP-IP, and SPI, I²C, UART, RS-232/RS-422 interfaces. I am also comfortable debugging interactions between firmware and hardware using schematics, datasheets, scopes, and logic analyzers, then carrying the work through integration, regression testing, and production release. My background includes supporting firmware alongside hardware development and taking consumer and commercial products from concept through production. I would begin with a focused codebase and hardware review, map the affected drivers and application layers, bring up the new peripherals incrementally, and validate each change against the existing platform using Git-managed, reviewable updates. Are the current source tree, new-board schematics, and prototype hardware available for the initial review? I would be glad to discuss the platform and relevant legacy firmware projects in more detail.

@SPARKtechBD

Since 2003 I am working in Digital Electronic. So more than 18 years of experience in Electronics. Arduino NANO/UNO/MEGA, ESP32 and Raspberry PI to build a digital device to read sensor data and send it to the web server, motor control, control relay switches and LEDs. More than 5(five) years of experience in Arduino design and build. If you want an excellent and error-free project delivery, then send a message to me, please. Have more than 10(years) years of experience in C/C++ to build Windows/Linux applications and micro-controller firmware building. If you want a good job delivery, then send a message to me, please. Since 1995 I have been working on Analog and Digital Electronics to build any kind of device. I have build lots of devices. So more than 20 years of experience on Electronics. Including power supply design. Any kinds of schematic and PCB design. Expert PCB design in EasyEDA Pro IDE.

@tshibsamuel477

Hi there, I read your offer carefully and understand that you need a senior embedded firmware engineer to extend an existing commercial embedded C firmware platform for a new hardware revision, including RTOS integration, peripheral support, communication interfaces, debugging, and validation. I can support existing codebase review, new hardware bring-up, SPI/I2C/UART/RS-422/Ethernet integration, RTOS-based firmware updates, embedded debugging, Git workflow, bootloader/update support, and production-quality validation documentation. My experience with embedded C/C++, RTOS-based systems, hardware bring-up, communication interfaces, Ethernet/TCP-IP, firmware debugging, and legacy embedded platforms fits this project well. Just send me a message and we can discuss the current architecture, new hardware changes, and first integration milestone. Best regards, Samuel Tshibangu

@WishingBell

Hi, I understand you need someone to extend an existing embedded C firmware platform to support a new hardware revision, including driver work for SPI, I2C, UART/RS-422 and Ethernet on an RTOS. The main technical risk is integrating new board support into a legacy codebase and bootloader while preserving field-update paths and timing-sensitive comms. I'd start by reproducing the current build locally (CodeWarrior/toolchain and Git), run the existing test harness on hardware or a NetBurner target if present, and map out the HAL and RTOS hooks. Then I’d add board support layers and isolated peripheral drivers, validate with JTAG + logic analyzer, and exercise firmware-update and bootloader paths. I’d keep changes small and trackable in feature branches and add focused unit/hardware-in-loop tests for the new modules. Do you have the schematics and the current toolchain versions available?

@tangramua

Dear ,   We carefully studied the description of your project and we can confirm that we understand your needs and are also interested in your project. Our team has the necessary resources to start your project as soon as possible and complete it in a very short time.   We are 25 years in this business and our technical specialists have strong experience in C Programming, Electronics, Microcontroller, PCB Layout, RTOS, Debugging, Git, Embedded Systems, Firmware Development and other technologies relevant to your project.   Please, review our profile https://www.freelancer.com/u/tangramua where you can find detailed information about our company, our portfolio, and the client's recent reviews.   Please contact us via Freelancer Chat to discuss your project in details.    Best regards, Sales department Tangram Canada Inc.     

@sekai1116

Drawing from my extensive experience as an Embedded Systems and Electronics Engineer, I bring a wealth of knowledge that speaks directly to the needs of your project. I have a strong background in Embedded C and have worked with a multitude of RTOS such as FreeRTOS, making me well-equipped to understand your existing architecture. My proficiency with essential communication interfaces like SPI, I²C, UART/RS-422, and Ethernet instill confidence that I can successfully develop and integrate firmware for any new hardware components you require. Over the years, I've honed my skills in debugging and hardware bring-up, which will be crucial for this project. In addition, my familiarity with Git enables streamlined source control practices, enhancing collaboration within the team. Moreover, with my experience working on ColdFire processors and using MQX RTOS and CodeWarrior similar to what your project requires, we can hit the ground running for efficient progress. Should you partner with me, you will also benefit from my strong background in RF communications which could come in handy for troubleshooting telecommunications equipment issues if needed. As a detail-oriented engineer, I recognize the importance of adhering to tight production schedules without compromising on quality. Let's collaborate towards breathing new life into your existing platform while ensuring it is optimized for performance and reliability.

@Specgi

I am excited to apply for your Senior Embedded Firmware Engineer position. I have experience developing reliable and efficient embedded firmware for microcontroller-based systems, with expertise in C/C++, RTOS, peripheral drivers, communication protocols, and hardware integration. I can contribute to the complete firmware development lifecycle, from architecture and implementation to debugging, optimization, and production support, ensuring a robust and maintainable solution. My approach focuses on writing clean, modular, and well-documented code while collaborating closely with hardware and software teams. I have experience working with interfaces such as UART, SPI, I2C, CAN, USB, and Ethernet, as well as debugging using oscilloscopes, logic analyzers, and JTAG/SWD tools. I prioritize performance, reliability, and compliance with project requirements, ensuring firmware is thoroughly tested and optimized for real-world applications. I am committed to delivering high-quality firmware solutions on schedule while maintaining clear and consistent communication throughout the project. I am confident in my ability to quickly understand your system requirements, resolve technical challenges, and provide long-term support as needed. I look forward to discussing your project and how I can contribute to its success.

@XRProConnect

Hi, Aashiq here from Cape Town, South Africa. This project instantly caught my eye, so I had to reach out. I see you’re looking for a Senior Embedded Firmware Engineer to extend and integrate an existing commercial embedded firmware platform. It sounds like a great opportunity to leverage my expertise in embedded systems while diving into the established architecture. I've spent years helping companies enhance their firmware solutions, focusing on integrating new functionalities and ensuring production-quality outputs. My experience with RTOS and communication interfaces like SPI and I²C has consistently delivered strong results. I’d be happy to share samples of similar projects I've successfully completed. Based on what you mentioned, here is how we would approach the project: - Review and understand the existing firmware codebase. - Develop and integrate firmware for new hardware components. - Implement debugging and validation processes. - Collaborate closely using Git for version control. You can count on clear communication throughout the project. I’ll ensure a seamless, user-focused solution optimized for performance. Best Regards, Aashiq

@starttechno

Your requirement is clearly an extension of a production firmware platform, not a prototype: the priority is safely understanding the existing Embedded C architecture and bringing the new hardware revision into it without disrupting established behavior. I can take this on with a disciplined codebase-first approach. I would begin by mapping the MQX/RTOS tasks, interrupt paths, board-support layer, driver abstractions, build configuration, and current Git workflow. From there, I would compare the old and revised schematics/BOMs, implement or adapt peripheral drivers, and integrate SPI, I²C, UART/RS-422, and Ethernet/TCP-IP functions with attention to timing, buffer ownership, error recovery, and low-latency communication paths. For ColdFire, MQX, CodeWarrior, or NetBurner-based code, I would preserve existing conventions where practical rather than force a rewrite. Each hardware change would be validated through staged bring-up: clocks and GPIO, serial diagnostics, individual buses, RTOS task interaction, network communication, then regression and fault testing. I will keep commits traceable and document board-level configuration, known limitations, and firmware-update/bootloader implications where applicable. Do you already have the revised schematics and a list of the peripherals that changed from the current board? Muhammad Saad

@mayr81

Senior Embedded Firmware Engineer role aligns with solid embedded C + RTOS firmware integration work. I can extend an existing commercial embedded platform for a new hardware revision by quickly mapping the current architecture, identifying abstraction layers for board/driver differences, and implementing production-quality support for new components. Key focus areas: embedded C development, RTOS-based design (FreeRTOS/MQX/uC/OS/ThreadX-style patterns), and bring-up plus debug through JTAG/UART. I’m comfortable adding and validating SPI, I²C, UART/RS-422, and Ethernet/TCP-IP interfaces, ensuring reliable communication behavior and clean integration with existing modules. Workflow: review legacy code, implement incremental changes with Git-based source control, add firmware hooks for boot/updates where required, and support system integration and firmware validation cycles to reach stable, shipping-ready releases.

@trm66614

I appreciate the opportunity to work on your existing embedded firmware platform. With extensive experience in embedded C development and a solid understanding of RTOS, I’m well-prepared to contribute to your project effectively. My hands-on experience includes developing firmware for various hardware interfaces like SPI, I²C, and UART, ensuring smooth integration of new components into established systems. I prioritize delivering production-quality firmware that meets user expectations and aligns with the architecture you have in place. Collaborating closely with teams has enabled me to tackle challenges effectively, especially in debugging and maintaining communication protocols. I have successfully managed firmware validation processes and utilized Git for source control in previous projects. My past work with ColdFire processors and familiarity with MQX RTOS align well with your needs. I’m keen to learn more about your specific requirements Could you share more details about the existing firmware architecture to better understand integration challenges?. Thank you for considering my proposal; I look forward to potentially collaborating with you. Best Regards, Talha

@sufyanasmat38

Hello, Working with an existing embedded firmware platform requires a strong understanding of hardware interfaces, firmware architecture, and system-level integration. Our team has experience supporting embedded products through hardware revisions, peripheral integration, firmware enhancements, debugging, and production deployment while maintaining code quality and long-term maintainability. We have worked extensively with Embedded C, RTOS-based systems, hardware bring-up, communication protocols including SPI, I²C, UART/RS-232/RS-422, and Ethernet/TCP-IP. Our approach focuses on understanding the existing architecture first, then implementing new functionality in a clean and scalable manner while ensuring reliability through thorough testing and validation. We would be glad to review the current platform, support the new hardware revision, and deliver production-ready firmware that integrates seamlessly with the existing system. Looking forward to discussing the project and contributing to its successful deployment. Best regards, Sufyan | Fourge Team

@mobasherreza10

As an experienced Senior Embedded Firmware Engineer with a notable background in working with established systems, your project aligns perfectly with my skill set. My proficiency in embedded C programming and extensive knowledge in RTOS such as MQX and FreeRTOS will allow me to seamlessly analyze and extend your existing firmware platform for the required hardware configurations. Having worked with numerous communication interfaces including SPI, I²C, UART/RS-232/RS-422, and Ethernet, I possess the understanding and expertise needed for the task. In addition to these core proficiencies, I've developed a mastery over debugging embedded systems and have been adept at hardware bring-up tasks. I'm also well-acquainted with Git for source control which ensures efficient project collaboration and management. Importantly, my experience extends to the preferred ColdFire processors as well as MQX RTOS which serve as valuable assets for your project.

@Ryan15222

Hi, I am an Embedded Firmware Engineer with extensive experience in Embedded C, FreeRTOS, STM32, ESP32, hardware bring-up, and embedded communication protocols including SPI, I²C, UART/RS-232/RS-422, and Ethernet/TCP-IP. I have worked on maintaining and extending existing firmware platforms, integrating new hardware, debugging complex embedded systems, and delivering production-ready firmware. I am comfortable working with legacy codebases, understanding existing architectures, implementing new features, and validating firmware through hardware testing. My workflow includes version control with Git, structured code reviews, and thorough documentation to ensure maintainable and reliable firmware. While my primary experience is with modern ARM-based embedded platforms rather than ColdFire/MQX, I am confident in quickly adapting to established firmware architectures and development environments. I look forward to discussing your hardware platform and contributing to the successful integration of your new hardware revision. Best regards,

@melopgabriel

Hi, You need someone who can take an existing embedded C firmware platform, understand it quickly, and extend it for new hardware without disrupting production stability. That is exactly the kind of work I enjoy. I have worked on legacy embedded systems involving RTOS-based firmware, device drivers, and communication interfaces such as SPI, I²C, UART, and Ethernet/TCP-IP. I am comfortable debugging hardware bring-up issues, tracing faults at the protocol level, and integrating changes into an established codebase with Git. My approach would be to first map the current architecture, identify the hardware deltas, and validate each interface before layering in new functionality. From there, I would implement and test incrementally, with careful attention to firmware reliability and integration risk. If this fits your needs, I would be glad to discuss the platform and next steps. Best regards, Gabriel

@Aaleen110

The hardest part of this job is integrating new hardware into an existing commercial embedded C firmware platform, that is the hard part. I will review the existing codebase for the embedded firmware platform and then I will develop the C code for the new hardware components, using the SPI, I²C, and UART/RS-422 interfaces where needed. I will also bring in Ethernet support. I would build the hardware interface drivers first, so that all new features can be tested against this foundation. I will use Microcontroller for this work, and PCB Layout experience helps in understanding hardware constraints for firmware development. I will need to know the specific Microcontroller family and the clock speed for the new hardware revision. 8 reviews on here, everything delivered on time and on the agreed price so far, plus Preferred Freelancer status. I will send back the proposed timeline and estimate once I have the Microcontroller details.

@arturg6

Hello, "Modular RTOS Firmware Extension" - adding new hardware to an existing firmware platform I will use FreeRTOS with a hardware abstraction layer to isolate the new peripherals, ensuring clean integration and easy future updates. I built a similar low‑level Linux driver and test‑bench for SAS drives: https://www.freelancer.com/projects/sas/SAS-Drive-Test-Bed-Setup/reviews I will also implement a robust bootloader update mechanism to allow safe firmware upgrades over Ethernet. Could you share the current repository structure and the target hardware revision details? Looking forward to working with you. Artur Giżycki

@dmytrobazavluk

Hi, Dmytro here from Illinois. The usual culprit when extending legacy embedded firmware platforms for a new hardware revision points at hidden pin-mapping changes and timing regressions inside Board Support Packages (BSP)—which often cause silent driver lockups across RTOS task queues, Ethernet MAC ring buffers, or peripheral bus transactions (SPI/I²C). Having engineered commercial firmware platforms across NXP ColdFire, MQX RTOS, CodeWarrior IDE, and NetBurner environments, my approach focuses on: • Architecture Review & BSP Adaptation: Auditing your existing C codebase and BSP layer to isolate new hardware peripherals, updating low-level register abstractions, and ensuring pin multiplexing and memory-mapped register definitions align with the new PCB revision. • RTOS Driver & Peripheral Integration: Extending MQX/FreeRTOS tasks, interrupt service routines (ISRs), and queue handlers for updated SPI, I²C, UART/RS-422 sensors, and TCP/IP stack endpoints without introducing race conditions or task starvation. The critical decision hinges on whether this hardware revision requires modifying the existing bootloader flash partitioning layout or updating the MQX BSP network stack parameters for new Ethernet PHY components. If a short call is easier, we can review your existing hardware architecture and CodeWarrior environment in ten minutes — otherwise, share your block diagram or pin-out diffs, and I'll start outlining the migration strategy.