Embedded Systems

Hardware and firmware as one

An embedded system only works well when hardware and firmware work together seamlessly. We design both under one roof, so pin assignments, interfaces, and timing are aligned from day one. No integration surprises, no finger-pointing between disciplines.

Sound familiar?

  • Your hardware was designed without considering the firmware, and now you're running into limitations
  • Integration between hardware and firmware takes more time than the development itself
  • The PCB has been ordered, but a pin turns out to be wrong or an interface is missing
  • You have a working prototype, but it's not robust enough for production
  • You don't want to coordinate three vendors for one embedded system

We design hardware and firmware as one system. From the start.

What we build

Sensor systems

Reading sensors, signal conditioning and processing. From accelerometers to temperature, from analog to digital.

Industrial controllers

Control modules for machines and installations. Robust, reliable, designed for harsh environments.

IoT devices

Connected devices with BLE, Wi-Fi, or LTE. Collect data, process locally, and transmit securely.

Measurement equipment

Precision measurement instruments with high accuracy. From prototype to production.

Motor control

Driving motors, actuators, and relays. From simple PWM to closed-loop control.

Embedded HMI

Systems with a display or touchscreen as part of the embedded design.

Our approach

Hardware and firmware co-design

Specification and architecture

Together we define what the system needs to do. We bring hardware and firmware requirements into a single document: which sensors, which interfaces, how much memory, what power supply, what environmental conditions.

Component and platform selection

We choose the microcontroller, sensors, and other components based on the total system requirements, not just the hardware or just the firmware. This prevents running out of I/O, memory, or processing power after the fact.

Pin planning and interface design

Before the schematic is drawn, we define the pin assignment and bus architecture. Hardware engineer and firmware engineer at the same table. This eliminates the most common cause of PCB respins.

Develop in parallel, integrate together

While the PCB is being laid out, firmware development starts on a devkit or previous revision. By the time the first prototypes arrive, the firmware is ready to flash.

Test and validate

Hardware and firmware are tested together. Not just "does the chip work" but "does the system do what it needs to do." Including edge cases, timing, and EMC behavior.

Production handover

You receive a working system: PCB design, firmware source code, documentation, and production-ready files. Everything you need to continue independently.

Technology

  • Microcontrollers/processors: STM32, ESP32, Nordic nRF, RP2040, CM4/CM5
  • Languages: Rust (preferred), C
  • Protocols: SPI, I2C, UART, CAN, USB
  • Wireless: BLE, Wi-Fi, LoRa, LTE-M/NB-IoT
  • Frameworks: Embassy, RTIC, egui
  • Tools: KiCad, Fusion360, Git, CI/CD, JTAG/SWD
  • Designed for: EMC, thermal management, and manufacturability

About us

Jitter B.V. has been developing complete embedded systems for over ten years: from PCB design to firmware and everything in between. Our engineers handle both the hardware and the firmware, which means we prevent problems at the boundary between the two rather than fixing them after the fact. We put that experience to work for your project.

Frequently asked questions

What is embedded systems development?
Embedded systems development is the design and construction of electronic systems where hardware (PCB) and firmware (software on the microcontroller) form one integrated whole. Think of a sensor that measures, processes, and transmits data, or an industrial controller that operates a machine. At Jitter, we design both under one roof.
What's the difference between firmware development and embedded systems development?
Firmware development focuses on the software running on a microcontroller. Embedded systems development also includes the hardware design: the PCB, component selection, power architecture, and interfaces and sometimes even the enclosure. In embedded systems development, hardware and firmware are designed together so they are optimally aligned.
When do you need an embedded systems specialist?
When you want to build a physical product that measures, controls, or communicates, and you don't have a team that can design both the electronics and the firmware. Also when you have a prototype that isn't robust enough for production, or when the integration between hardware and firmware is causing problems, a specialized team can make the difference.
What does embedded systems development cost?
An embedded systems project with hardware and firmware typically starts around €15,000 for a simple design. More complex systems with multiple sensors, wireless communication, or certification requirements cost €25,000 to €60,000 or more. We work with fixed pricing per project phase. After a no-obligation intake meeting, you receive a clear quote.
How long does an embedded systems project take?
A typical project from specification to working prototype takes 3 to 6 months. This includes hardware design, firmware development, PCB production, and integration testing. Simpler projects can be faster, complex systems with certification take longer. We provide a realistic timeline at the start.
Why is it better to have hardware and firmware designed together?
When hardware and firmware are designed by the same team, choices like pin assignments, bus architecture, and power sequencing are aligned from the start. This prevents costly PCB respins, shortens integration time, and results in a more robust end product. The most common problems with embedded products arise at the boundary between hardware and firmware.

Need an embedded system?

Get in Touch