We write firmware for STM32, Nordic and NXP microcontrollers

Firmware is the program on the microcontroller that runs your device. We write it for your board and test it on that board. When the work is done, you get the source code.

A CONTROL BOARD, SEEN FROM ABOVE FIRMWARE runs here DISPLAY shows the menu BUTTONS what you press SENSORS take readings MOTOR runs and stops MEMORY keeps settings CONNECTOR to other units
Illustration: an example control board, not a client's. The firmware runs in the chip at the centre, and the coloured lines lead to the parts it reads and drives.

Scope

What we take on

Any one of these, or the whole firmware of a product.

We work with

  • STM32
  • Nordic nRF
  • NXP
  • FreeRTOS
  • Zephyr
  • CAN and CANopen
  • USB
  • UART, I2C, SPI
  • IEC 62304, class C
  • Firmware for a new product

    The complete firmware of a new device, up to the version that goes into production.

  • Drivers for the parts on your board

    Code for each chip, sensor, display and motor on the board, so the rest of the firmware can use them.

  • Links to other devices

    CAN and CANopen, USB, UART, I2C and SPI, to other units and to a PC.

  • Bootloader and updates

    The small program that starts the device, and checks and installs a new firmware version.

  • Real-time behaviour

    FreeRTOS or Zephyr, where the device must respond within a fixed time. On the Intec lift controller that time was 5 ms.

  • Fixing existing firmware

    When firmware is too slow, too large or fails now and then, we find the cause and fix it, and show you the measurement.

Questions

Questions about firmware projects

Can you take over firmware that someone else wrote?

Yes. We build the code and run it on your board first, then tell you what state it is in before any larger work begins. The Intec lift project started from firmware written for an older microcontroller.

Do we get the source code, and who owns it?

Yes, you get all of it with its documentation, and you own it. If you prefer, we work in your repository from the first day.

What do you need from us to start?

A few lines on what the device must do, the schematic if there is one, and a board or the date when boards arrive.

Do you work at a fixed price or by the hour?

Both. A fixed price needs a written scope. Work that is hard to scope in advance, such as tracking down a fault, is better done by the hour.

Oleksii Kvasnikov

Oleksii Kvasnikov · Founder and lead engineer

Tell us about the board and what it has to do

The schematic and the name of the microcontroller help. If firmware already exists, tell us what is wrong with it.