Firmware engineering
Embedded C/C++, bare metal, RTOS, low-level drivers, boot flows, bring-up, performance and reliability.
Independent engineering practice | Poland
Embedded systems, from schematic to firmware.
Firmware, hardware, embedded Linux and system-level debugging delivered with direct ownership by senior engineers.
System viewHW <-> FW
Capabilities
Engineering across the hardware-software boundary.
Work can begin with a blank architecture, an existing codebase, a prototype that needs stabilising, or a failure nobody has isolated yet.
Embedded Linux
Board bring-up, device tree, hardware integration, system services and embedded applications on Linux SBCs and SoCs.
Hardware engineering
Schematic design and review, PCB design, interface design, board bring-up and practical HW/FW co-design.
System integration
USB, PCIe, DDR, CAN, RS-485, UART, SPI, I2C and industrial interfaces - treated as complete signal and software paths.
Debugging & product rescue
Root-cause analysis of difficult hardware/software faults, prototype stabilisation and evidence-based redesign recommendations.
Architecture & review
Architecture, schematic and firmware reviews; feasibility analysis; technical risk assessment before expensive mistakes.
Meet the team
Senior engineering with direct ownership.
Projects are handled directly by two senior embedded engineers with a shared low-level foundation and complementary technical focus. Both work across firmware, Embedded Linux and system integration, with deeper emphasis spanning electronics, architecture, debugging and Edge AI. Trusted specialists join when a project needs expertise outside the core team.
How we work
A clear engineering path, adapted to the problem.
Enough structure to control risk - without turning the engagement into a rigid corporate process.
01
Understand
Define the real requirement, constraints and known failure modes.
02
Investigate
Inspect the evidence, code, schematics, signals and current architecture.
03
Design
Choose the smallest robust solution and make technical risks explicit.
04
Implement
Build in reviewable stages across the necessary hardware and software.
05
Validate
Test behaviour, failure paths and deployment assumptions.
Typical starting points: product concept | schematic | firmware codebase | prototype | failing hardware | architecture question
Projects
Embedded systems built around real constraints.
Public case studies focus on engineering decisions, implementation boundaries and verified prototype behavior.
Project placeholder
Project details are currently private under NDA. A public case study may be added when publication is permitted.
Technology
Tools selected for the engineering task.
Experience is grouped by how it is applied, not presented as a wall of keywords.
Platforms
ARM Cortex-M and Cortex-R, STM32, GD32, ATSAM, PIC, ESP32, Linux SBCs, FPGA-based prototype environments.
Firmware
Embedded C and C++, bare metal, RTOS, drivers, boot and bring-up, low-level storage firmware.
Operating systems
Embedded Linux, board support, device tree, system services and embedded applications.
Interfaces
USB, PCIe, DDR, CAN, RS-485, UART, SPI, I2C, Modbus, GNSS and cellular systems.
Hardware
PCB design and review, KiCad, analogue electronics, isolation, motor control, 4-20 mA, industrial and automotive systems.
Engineering work
Bring-up, HW/FW integration, root-cause analysis, architecture review and complex low-level debugging.
Contact
Have an embedded problem worth discussing?
Share the current state, the constraints and what is not working. A useful first conversation can start from a concept, schematic, codebase or failing prototype.