Technologies we use
ESP-IDF

RTOS

STM32

Arduino

Raspberry Pi

Linux

Zephyr OS

C/C++

Python

Nordic nRF

NXP
TI
Key Capabilities
C/C++ & Assembly
- MISRA C compliant code
- Mission-critical systems
- Bare-metal & RTOS-based
- Low-level driver development
Hardware Interfaces
- High-speed: USB 2/3, MIPI-DSI/CSI, I2S, DDR3/4
- Low-speed: I2C, SPI, QSPI, UART, CAN
- Industrial: Ethernet, RS-485, SDIO
- 1-Wire, PWM, ADC/DAC
RF & IoT Protocols
- Cellular: NB-IoT, LTE-M, LTE, GPRS
- Wireless: WiFi, BLE, ZigBee, LoRa, UWB
- Mesh: Thread, Z-Wave, 6LoWPAN
- NFC, RFID (433 MHz, 860–960 MHz)
Communication Stack
- MQTT, HTTP/HTTPS, FTP
- Modbus TCP/RTU, SNMP
- TCP/IP, UDP/IP, DLMS
- AWS IoT, Azure IoT Hub
Security & Crypto
- AES encryption
- SSL/TLS — WolfSSL, mbedTLS
- Secure boot mechanisms
- Custom secure algorithms
RTOS & Embedded Linux
- FreeRTOS, Zephyr OS, TI-RTOS
- Yocto, Buildroot, ROS/ROS 2
- LVGL, TouchGFX, emWin GUI
- TensorFlow Lite, sensor fusion
Development Process
Requirements & Spec
Hardware components, communication protocols, power management, and functional logic are fully specified before any code is written.
Architecture Design
Block diagrams, UML, workflow charts, and API/interface definitions — establishing module relationships and system states.
Agile Development
2-week sprints with modular C/C++ implementation. Each sprint includes testing on target hardware to catch issues early.
Code Review & QA
MISRA C compliance validation, senior engineer review, and QA sign-off. Git-based review flows with Jira tracking.
Release & Delivery
Git version tagging (e.g. v1.2.0), full technical documentation, and demo applications for each release.
Hardware Bring-Up
Custom test firmware for all interfaces, UART console output, and real-time hardware-firmware debugging collaboration.
Supported Platforms
MCU
- STM32 (F, G, H, L, WB, MP1)
- Nordic nRF52 / nRF53 / nRF9160
- NXP i.MX-RT, LPC families
- Espressif ESP32 / ESP8266
- TI MSP430, MSP432, CC series
- Atmel/Microchip AVR, SAM
- Silicon Labs EFR32
MPU
- NXP i.MX 6 / 7 / 8 series
- STM32MP1
- Raspberry Pi CM3 / CM4 / CM5
- NVIDIA Jetson (Nano, Orin)
- Qualcomm Snapdragon
- Allwinner A-series
Tools
- STM32CubeIDE, MCUXpresso
- Segger Embedded Studio
- GCC, Clang, LLVM toolchains
- J-Link, OpenOCD, JTAG/SWD
- Wireshark, logic analyzers
- Git, Jira, Confluence
Häufig gestellte Fragen
Für welche Mikrocontroller entwickeln Sie Firmware?
Wir unterstützen STM32 (F/G/H/L/WB/MP1), Nordic nRF52/53/9160, NXP i.MX-RT, Espressif ESP32/ESP8266, TI MSP430/CC-Serien, Atmel/Microchip AVR und Silicon Labs EFR32.
Arbeiten Sie mit Bare-Metal oder RTOS?
Beides. Wir entwickeln Bare-Metal-Firmware für ressourcenbeschränkte MCUs und RTOS-basierte Firmware (FreeRTOS, Zephyr OS, TI-RTOS) sowie Embedded Linux (Yocto, Buildroot).
Welche Kommunikationsprotokolle unterstützen Sie?
WiFi, BLE, LoRa, ZigBee, NB-IoT, LTE-M, MQTT, HTTP/HTTPS, Modbus TCP/RTU, CAN, I2C, SPI, UART, USB und weitere.
Können Sie mit unserer bestehenden Hardware arbeiten?
Ja. Wir führen regelmäßig Hardware-Inbetriebnahmen und Firmware-Entwicklungen für kundenseitig bereitgestellte Designs durch.
Liefern Sie den Quellcode?
Ja. Der gesamte Code wird über Git mit Version-Tags, vollständiger technischer Dokumentation und Demo-Anwendungen geliefert.
Warning