We design and build embedded systems end to end — firmware, electronics, and production handover — for connected devices, industrial equipment, and smart building products, on microcontrollers, Embedded Linux, and SoM platforms.
PettersonApps handles embedded development from prototype to production, including schematic and PCB design, firmware, drivers, connectivity, and validation. One team manages both hardware and software, ensuring they work together seamlessly.
ESP32 (S2, S3, C3, C6), ESP8266, and STM32 (L0, L4, F1, F4, F7, H7)
Buildroot, Yocto, Device Tree, and BSP bring-up on Raspberry Pi CM4/CM5, NVIDIA Jetson, and Lantronix Open-Q
FreeRTOS, Zephyr, and Azure RTOS (ThreadX) with multithreaded, memory-safe architecture
BLE, Wi-Fi, Matter, Thread, Zigbee, and LoRaWAN, including provisioning and mesh networking
Modbus, CAN and CAN FD, J1939, KNX, DALI-2, M-Bus, 0-10 V, and 4-20 mA, including protocol gateways
Sony IMX sensors over MIPI CSI-2, USB 2.0/3.x, LVDS, and HMI on LVGL, OLED, E-Ink, and touchscreens
DC, BLDC, and stepper drives with closed-loop control, IMU and analog acquisition
Multilayer PCB and flex cable design in Altium Designer and KiCad, power architecture, and board bring-up
Secure Boot, flash encryption, TLS with mbedTLS or wolfSSL, and secure OTA updates with anti-rollback
BOM management, second-sourcing, obsolescence planning, and coordination with contract manufacturers
Every part on this board is something we design, write, or bring up ourselves. Point at one to see the layer behind it.
04.Connectivity
Provisioning, mesh networking, and secure device-to-cloud links — tuned on the bench until the radio meets its range and power budget.
You have a product concept and need a team that covers both the board and the code. We take you from architecture and component selection to a validated prototype and a design ready for small-batch production, and we tell you early when a cheaper chip or simpler design meets the requirement.
Your current device is unstable, hard to update, or built around an obsolete component. We review the existing design, stabilize or rewrite the firmware, add secure OTA updates, and handle second-sourcing so supply problems stop driving your roadmap.
Your equipment must talk to PLCs, meters, lighting, and building systems. We implement Modbus, CAN, KNX, DALI, and M-Bus on your hardware, and build gateways that convert between protocols and connect the field level to the cloud.
You already have an app or platform and need the connected hardware to match. We build firmware, wireless provisioning, and secure device-to-cloud communication so the device works with your backend from the first release. Cloud and app work is covered by our IoT development team.
In most connected products, every layer is a handoff to another vendor. With us it is one team, from silicon to cloud, so a problem is traced through the whole stack instead of bounced between vendors.
One stack, one team.
Device-to-cloud messaging and the APIs your backend and apps talk to, developed together with the firmware so data arrives in the shape the product expects.
Secure Boot, flash encryption, and TLS from the first build, plus signed OTA updates with anti-rollback so every device in the field can be updated safely.
Provisioning, mesh networking, and radio tuning on the bench until each link meets its range and power budget.
Bare metal, RTOS, or Embedded Linux chosen to fit the product, with Yocto and BSP bring-up handled by the team that writes the drivers.
C and C++ on ESP32 and STM32, written by the same engineers who laid out the board, so a timing bug is chased from the register to the cloud without a handoff.
Component selection, multilayer PCB and flex design, and board bring-up on the bench before the first production run.
One team, one build.
Most embedded projects go over budget because of early choices: the wrong MCU, too little memory, or a power budget that misses battery-life targets. We start by fixing requirements, interfaces, power and cost targets, and pick the platform and components with second-sourcing and lifecycle in mind.
The same engineers who design the PCB write and debug the firmware, so problems are traced across the boundary. We bring up every board with oscilloscopes and logic analyzers, test signal integrity and protocols, and validate the design with unit tests and hardware-in-the-loop (HIL) testing.
A working prototype is not a product. We build with Git, CMake, and CI/CD pipelines (GitHub Actions, GitLab CI), document the code with Doxygen, implement secure OTA updates, and support the move to manufacturing: BOM, component sourcing, and coordination with the contract manufacturer.
Before you ask.
Planning a new device or fixing one?
Share your requirements or current design. We review the architecture, components, and risks, then provide a written technical assessment with a recommended approach and scope estimate.