Embedded Systems

Hardware and firmware as one

An embedded system is only good when hardware and firmware fit together. We design both under one roof, so pin assignments, interfaces and timing are right from day one. That means no integration problems afterwards and 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 already been ordered, and then a pin turns out to be assigned 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, conditioning and processing signals. From accelerometers to temperature, from analog to digital.

Industrial controllers

Control modules for machines and installations, built to run reliably in harsh environments.

IoT devices

Connected devices with BLE, Wi-Fi or LTE. Collect data, process it locally and send it securely. Our sensor-link building blocks for 4G, security and remote updates give you the foundation from the start.

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, which power supply, which environmental conditions.

Component and platform selection

We choose the microcontroller, sensors and other components based on the requirements of the whole system, hardware and firmware together. That way you don't find out later that a chip is short on I/O, memory or processing power.

Pin planning and interface design

Before the schematic is drawn, we fix the pin assignment and bus architecture, with the hardware engineer and the firmware engineer at the same table. That removes the most common reason for a PCB respin.

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

We test hardware and firmware together. The question is whether the system does what it needs to do, which goes further than whether the chip works. That includes edge cases, timing and EMC behavior.

Production handover

You get a working system: PCB design, firmware source code, documentation and production files. Everything you need to carry on by yourself.

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, Tokio, 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 more than ten years, from PCB design to firmware and everything in between. Our engineers do both the hardware and the firmware, so we prevent problems at the boundary between the two instead of fixing them afterwards. Take the DoseRx1, a pharmaceutical 3D printer for which we developed the electronics, firmware and GUI as one system. We use that experience on 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