Platform Independent EV Charger Firmware Development

@amelectronics

I am a skilled and reliable Embedded Systems Engineer with over 6 years of hands-on experience in Arduino, ESP32/ESP8266, and microcontroller-based development. I specialize in designing efficient, stable, and scalable embedded solutions, turning ideas into fully functional hardware-software systems. I have a strong background in electronics, sensors, communication protocols (UART, I2C, SPI, MQTT, WiFi, BLE), and real-time embedded systems. My development approach focuses on clean, well-structured, and well-documented firmware, ensuring long-term reliability and easy maintenance. I also provide thorough testing, debugging, and performance optimization, including power efficiency improvements where required. I am a detail-oriented engineer with strong problem-solving skills and extensive experience in hardware debugging and firmware optimization. Beyond technical expertise, I value clear communication, meeting deadlines, and maintaining high client satisfaction. I work closely with clients to fully understand project requirements and deliver high-quality results. Pricing is flexible and can be discussed based on project scope and complexity. I am open to both short-term and long-term projects. Let’s work together to build a professional, reliable, and efficient embedded system for your needs.

@hayteekeys

HI, KINDLY READ THROUGH MY PROPOSAL I will deliver a professional, modular, and highly portable embedded firmware architecture for your EV Charger system, consisting of a robust Bootloader and a scalable Main Application Framework designed for long-term maintainability and easy porting across different MCU families. MY APPROACH ✅ Phase 1: Define clean layered architecture (BSP - HAL- Drivers - Services - Application) with strong hardware abstraction. ✅ Phase 2: Develop Bootloader with CAN-based OTA, CRC validation, safe dual-slot update, recovery mechanism, and version management. ✅ Phase 3: Build Main Application Framework with RTOS-ready structure, driver abstraction, and clear APIs. ✅ Phase 4: Full documentation, porting guide, and build system portability (CMake + VS Code preferred). RELEVANT PROJECTS • EV Charger firmware platform (STM32 + CAN bootloader with safe OTA). DELIVERABLES • Complete Bootloader source code with CAN OTA • Scalable Main Application Framework • HAL + Driver abstraction layer • Memory map, architecture documentation, and porting guide • CMake-based build system for easy IDE portability QUESTIONS 1. Do you have a preferred primary MCU for the initial development (STM32F7/H7, etc.)? 2. Is FreeRTOS or another RTOS required from the start? 3. What is your target timeline for the first functional bootloader milestone? Ready to start immediately. I prioritize clean, maintainable, and future-proof architecture as requested.

@cesur135

With my extensive experience in industrial automation and embedded systems, I am confident that I can effectively contribute to your EV charger firmware development project. My proficiency in C programming, particularly in designing robust and scalable architectures using MISRA-oriented clean coding will ensure the creation of a modular, platform-independent firmware able to support multiple microcontrollers, IDEs, and hardware platforms. With a background in STM32, TI/NXP platforms, I have an understanding of their unique properties and can skillfully ensure minimal modifications facilitating easy migration between different ARM-based MCUs. Additionally, my expertise in CAN protocols coupled with experience in developing bootloaders will ensure the creation of a comprehensive firmware capable of updating over CAN communication, performing _FLASH operations,and conducting_firmware integrity verification while providing recovery measures if ever needed. Moreover, coming from a background that values long-term maintainability and scalability ensures I'm well-positioned to provide you with stable and scalable solution for future EV charger products.

@salmanali11053

Hello, Your requirement aligns very well with my 11+ years of experience in automotive and industrial embedded systems, especially in scalable firmware architecture, CAN communication, abstraction layers, and reusable embedded platforms. What I liked in your post is the focus on: * portability across MCU platforms * long-term maintainability * modular architecture * reusable bootloader/application framework This is the correct approach for EV charger products expected to evolve across different hardware platforms. My experience includes: * Embedded C firmware architecture * CAN-based systems * RTOS-ready software design * HAL/BSP abstraction * Modular driver frameworks * MISRA-oriented development * STM32 and automotive-grade embedded systems For this project, I would recommend a phased approach focusing initially on: * portable architecture foundation * BSP/HAL separation * CAN bootloader framework * configurable project structure * reusable APIs and services A few questions: 1. Which MCU/platform is planned for Phase 1? 2. RTOS or bare-metal initially? 3. Is secure boot or encrypted update planned later? I’d be happy to discuss the architecture direction further. Regards, Salman Ali

@mahads31

As an experienced freelance developer focused on delivering scalable, high-quality digital solutions, I am a perfect fit for your complex firmware development project. My expertise lies in embedded systems, bootloader development, and cross-platform architecture design. I am well-versed in the C programming language and have a deep understanding of CAN communication, which are crucial to the success of your EV charger firmware. In addition, my broad experience across different platforms including STM32, TI, and NXP aligns perfectly with your need for a platform-independent and easily portable solution. Furthermore, my industrious nature and MISRA-oriented coding style prioritize clean architectures—essential for your long-term maintainability requirements. Lastly, it is worth noting that I am not new to the world of EV charging systems. Throughout my career, I've gained invaluable insights working on similar projects that make me highly attuned to the specific challenges associated with this field. By choosing me for this project, you're putting your trust in someone committed to delivering an industrial-grade and reusable embedded platform — an investment that pays off with easy scalability for any future EV charger products you may develop. Let’s get started on building your future-proof firmware architecture together!

@pradeep152006

Hello, Your project aligns strongly with my embedded firmware development background, especially in modular embedded systems, hardware abstraction, communication interfaces, and scalable firmware architecture. I can assist in developing both the bootloader and application framework with a strong focus on portability, maintainability, and long-term scalability across multiple MCU platforms. My approach would include: - Layered firmware architecture (BSP/HAL/Driver/Service/Application) - Platform-independent Embedded C design - Modular CAN-based bootloader implementation - Configurable memory mapping and firmware validation - RTOS-ready application structure - Clean API separation and reusable drivers - Portable build structure compatible with multiple IDEs/toolchains - Documentation for porting, memory map, workflow, and build process I understand the importance of industrial-style firmware structure over quick implementation and can design the framework with future migration support for STM32, TI, NXP, Renesas, and other ARM-based platforms. I would be interested in discussing: - Target MCU/platform for initial implementation - Flash layout constraints - CAN protocol/update flow expectations - RTOS preference (if any) - Security and firmware validation requirements - Future communication stack expansion plans Open to discussing the project further as per your convenience. Regards Pradeep

@stergioskiour

Hi there, Your EV Charger platform-independent framework project matches my background perfectly. I am an Electrical & Computer Engineer from Greece, specializing in embedded systems architecture, hardware abstraction, and modular firmware design. My engineering thesis focused on "Designing AHB Interconnection Interfaces in SystemC for High-Level Synthesis," giving me a deep understanding of hardware abstraction layers (HAL), bus interfaces, and scalable system design .Why I can build this for you: Layered Architecture: I write clean Embedded C that separates BSP/HAL from the Application layer. This keeps the codebase decoupled from specific MCU vendors (STM32, TI, NXP) and ready for RTOS. Bootloader & CAN: I have solid experience programming microcontrollers and verifying firmware. I can design a reliable CAN bootloader with CRC verification, flash partitioning, and safe rollback recovery. Modern Build Environment: I highly support your VS Code + CMake preference, ensuring toolchain independence and a version control-friendly structure.I prioritize clean, self-documented code and rigorous architecture documentation (memory maps, flowcharts) over rushed deployment. Let's connect to discuss your flash memory limits and preferred RTOS. Best regards, Stergios Kiourtsis

@maheshlachake

Hello, Greetings from EmbeddedFirmwareHelper. We are interested in discussing your EV Charger Bootloader + Application Firmware Framework project. We work on embedded firmware development for industrial and IoT products, with experience in Embedded C, STM32 firmware, CAN/FDCAN communication, bootloader flow, flash memory handling, driver abstraction, and modular firmware architecture. For the bootloader, we can support CAN-based firmware update, flash erase/write/read abstraction, CRC/checksum validation, configurable memory mapping, timeout-based jump to application, recovery handling, version management, and safe update flow. For the application framework, we can design a layered structure with BSP, MCU abstraction, driver, service/middleware, and application layers. The aim will be to keep MCU-specific code isolated so reusable logic can be ported across STM32, TI, NXP, Renesas, and other ARM-based MCUs with minimal changes. We can also provide architecture notes, memory map, bootloader workflow, API documentation, porting guide, build instructions, and firmware update process documentation. Before estimating timeline and budget, we would like to discuss the first target MCU, CAN update protocol, flash layout, RTOS preference, application scope, and milestone expectations. Regards, [Your Name] EmbeddedFirmwareHelper

@ashiqiitkgp

Hi there, As an Embedded Systems Architect with extensive experience in automotive/EV communication protocols, I specialize in designing hardware-agnostic firmware. I can build a highly modular, MISRA-C compliant Bootloader and Application Framework that abstracts vendor-specific silicon, ensuring seamless portability across STM32, TI, and NXP MCUs. My Execution Strategy: Platform-Agnostic Bootloader: I will develop a secure CAN-based bootloader utilizing a strict Hardware Abstraction Layer (HAL). It will feature robust flash partitioning, CRC-based integrity checks, timeout jumps, and fail-safe recovery mechanisms, entirely decoupled from specific IDE lock-ins. Layered Application Framework: I will architect the main firmware using a strict top-down model: BSP → HAL → Middleware (RTOS ready) → Service Layer → Application. This isolates hardware dependencies, allowing you to scale up to ISO15118 (Ethernet) or Modbus later without rewriting core logic. Build System: I will set up a VS Code + CMake build environment, guaranteeing seamless compilation across different toolchains (GCC, Keil, CCS). I prioritize clean architecture over quick hacks to ensure long-term maintainability. Let's discuss your primary MCU target for the initial port. Best regards,

@gvk2

I have more than 9 years of experience working on embedded domain. Keen to involve in this, please discuss. Negotiable Price