Home/Zephyr

Zephyr RTOS firmware for constrained IoT.

★★★★★ 4.9 Rated on Google Inc. 5000 honoree · ISO 9001:2015

Production firmware on Zephyr RTOS for resource-constrained devices. ARM Cortex-M, RISC-V, x86. Bluetooth LE, Thread, Matter, and certified protocol stacks, brought up on the board and shipped with signed OTA.

  • ARM Cortex-M, RISC-V, x86
  • BLE 5, Thread, Matter, Zigbee
  • Certified protocol stacks
  • OTA & secure boot
They trust us Tesla NASA Raytheon Virgin Intel Universal
Certifications & Awards ISO 9001:2015 THEA Award Inc. 5000 Growth Badge
What we deliver

Zephyr firmware capabilities at a glance.

Production-ready scope on Zephyr RTOS, documented for hand-off.

Device tree & BSP

Board bring-up on Zephyr: device tree, pin muxing, and a clean BSP so one codebase runs across multiple SoCs.

Drivers & peripherals

Sensor, peripheral, and radio drivers integrated against the Zephyr driver model, or written when the tree doesn't have one.

BLE & connectivity

Bluetooth LE 5.x, Thread, Matter, Zigbee, Wi-Fi, LTE-M, and NB-IoT integrated and taken through certification.

Power management

Tickless idle, peripheral power management, and sub-uA sleep tuned and profiled to hit the battery-life target.

How we work

From silicon select to signed firmware.

We bring up the board, build the stack, and ship the OTA pipeline. Each stage closes with a review you sign off.

01

SoC & board bring-up

Pick the SoC, define the device tree, and get the board printing logs over RTT or UART within the first sprint.

1–2 weeks
02

Drivers & stack

Sensor, peripheral, and radio drivers integrated. BLE, Thread, or Matter stack initialized and validated on hardware.

3–6 weeks
03

Application & power

Application logic, state machines, and aggressive power profiling to hit the battery-life target.

3–8 weeks
04

OTA, certify, ship

Signed OTA pipeline, BLE / Thread / Matter certification, and a signed release image handed off.

2–6 weeks
The Zephyr stack we ship

Production firmware, not demo code.

Each subsystem mapped to what you receive at hand-off.

SubsystemWhat you receive
Zephyr basev3.x LTS and newer, custom forks when needed, West manifest and CI
ArchitecturesARM Cortex-M (M0+, M4, M33, M55, M85), RISC-V (RV32, RV64), x86
SoCs & board filesDevice tree and BSP for Nordic nRF52/53/54, NXP, ST, Silabs, Espressif, Renesas RA
WirelessBLE 5.x, Thread 1.3, Matter 1.x, Zigbee 3.0, Wi-Fi, LTE-M / NB-IoT, certified
Power managementTickless idle, PM policies, sub-uA sleep, measured battery-life report
Security & OTAMCUboot signed dual-slot OTA, PSA Crypto, TF-M and secure boot when supported
ToolingWest, CMake, Renode emulation, Zephyr SDK, JLink / DAPLink, debug docs
FAQ

Common questions about Zephyr.

Process, scope, and what to expect when you start a Zephyr project with Jaycon.

Why Zephyr over FreeRTOS or bare-metal?

Single codebase across SoC vendors, certified BLE / Thread / Matter stacks, mature drivers, and aggressive power-management primitives. Easier to maintain across product lines than vendor-specific SDKs.

What SoCs do you ship Zephyr on?

Nordic nRF52/53/54 series, NXP, ST, Silabs, Espressif, and Renesas RA. We can port to any SoC with a Zephyr SoC tree.

Can you handle BLE / Thread / Matter certification?

Yes. We prepare the device for SIG, Thread Group, and CSA Matter certification, including QDIDs and pre-cert testing in our lab before final lab submission.

How do OTA updates work on Zephyr?

MCUboot dual-slot signed updates over BLE, UART, or USB. The secondary slot validates before swap and rolls back on failure.

Ready to ship on Zephyr?

Send your SoC and battery-life target and we'll scope a firmware build.

Get an Instant Quote