Zephyr

Zephyr has built-in debugging for many of its supported boards. Here's a real-world example of utilizing the these tools to track down and fix a networking error with CoAP.

Manufacturing is marathon, not a sprint. Chris Gammell walks through five phases of IoT device production, discussing what's involved in each step and how Zephyr RTOS can help during his talk from the 2024 Embedded Open Source Summit.

Golioth Firmware Engineer Mike Szczys describes how we use GitHub Codespaces and Development (Dev) Containers to train engineers all over the world without any install required. Answering the question of how fast can a new Zephyr RTOS user go from zero to successful code compilation.

The RAK5010 is a cellular board based on Quectel's BG95 modem (Qualcomm chipset). A Nordic nRF52840 microcontroller "runs the show", connecting to the modem via UART. This is a nice combination for a number of applications like remote sensing, application tracking, and Bluetooth <> Cellular gateway. Let's walk through the process of developing for this board in the Zephyr RTOS.

Guest author Jerónimo Agulló goes over the basics of GNSS and how the NMEA0183 set of messages standardizes communication between geolocation modules and microcontrollers. Then he shows how a new system in Zephyr makes it easier than ever to set up communication.

In this post, we'll walk through a couple methods for defining abstract hardware interfaces in Zephyr using...

Golioth works with Qualcomm. The Golioth Firmware SDK, release 0.12.0, supports the Zephyr Modem subsystem. This enables support for more modem technologies, starting with Qualcomm, and support for the Quectel BG95 as a first class cellular modem.

Both Zephyr and Golioth have solutions for keeping track of multiple revisions of your hardware. Let's walk through how to tell Zephyr there is both a "Rev A" and "Rev B" of your hardware. We'll finish up by talking about how Golioth organizes OTA firmware updates for your different board revisions.