01 / EMBEDDED
Firmware for devices, sensors and controllers on the client’s platform: bring-up, peripherals and application logic, with team support and integration into existing code.
Platforms and tools follow your context. Some examples:
Embedded
Microcontrollers and hardware/software integration
STM32 · ESP32 · PIC · AVRSelected for the project
ARM · RISC-V · other platformsReal-system constraints
C / C++ · bare metalStates, events and modules
GPIO · I²C · SPI · UARTInterrupts and interfaces
RAM · Flash · response timesProfiling and constraints
Debugging · logs · board testsFrom first boot to testing
The technologies shown are examples.
Engineering support within your team, with shared tools and working methods.
TECHNICAL SCOPE
Work starts from schematics, pin assignments, component documentation and expected behaviour. The architecture separates hardware access, protocols and product logic so modules can be tested and board variants managed without duplicating code. Bare-metal or RTOS is selected according to concurrency, timing and available resources.
At the start, I clarify board availability, documentation, debugging access and compatibility with installed firmware. I can work within the client’s repositories and toolchain, agreeing module responsibilities and how changes will be reviewed.
For example, an acquisition function is tested with known signals, an absent peripheral, timeouts and restarts. Outputs and timing are compared with requirements, recording board revision, configuration and test conditions. Results apply to the verified scope.
Source code, toolchain configuration, build and programming instructions, interface documentation and test results. Acceptance criteria connect real inputs to expected outputs and timing limits.
Useful inputs include a working board, schematics, component list, available firmware and examples of the signals or messages to handle.
The starting point can be your existing platform. Porting or architectural changes are assessed against the agreed constraints and objectives.
A custom ESP32 embedded solution with modular firmware, security features and Wi-Fi/BLE connectivity for connected products.
Microchip reports early PIC64-HPSC radiation results: TID to 200 krad(Si) and SEL testing to 78.2 MeV·cm²/mg. A technical analysis of RISC-V, radiation effects, ECC and mission software.
Agricultural drone software and firmware: C++20 architecture, PX4 autopilot, MAVLink communication and sensor data. SLX AgriPilot illustrates the engineering capabilities needed by UAV manufacturers, integrators and survey platform developers.
ESP-IDF 6.0 changes Picolibc, PSA Crypto, legacy drivers, build workflows and OTA. Here is how to assess risk before upgrading ESP32 firmware in production.
How chiplets, advanced packaging and UCIe can change embedded processors, edge AI accelerators and long-term product design.
A balanced look at RISC-V and ARM for embedded products: ecosystem maturity, licensing, customization, tools, AI acceleration and adoption risk.
How to structure a local ESP32 IoT device with AP/STA networking, HTTP endpoints, a responsive web UI and predictable firmware behavior.
THE NEXT STEP
