Tag: zephyr

Spring Cleaning with Golioth: Dust off your Zephyr skills in April 2025

Spring is a time of renewal, growth, and fresh starts—and your IoT projects deserve some spring cleaning, too! Dust off those ideas sitting idle, sharpen your embedded development toolkit, and join us for a free Zephyr RTOS Training on April 30th, 2025.

Useful Zephyr Shells for IoT Development

The Zephyr shell subsystem will help you directly interact with and troubleshoot your IoT hardware. This post details our most commonly used commands, as well as a listing of all Zephyr shell modules that we could extract from a recent project.

Adding sound to the Aludel Elixir based Reference Designs

This post highlights moving code from one Zephyr project to another and all the considerations for code portability.

How to Add Golioth to an Existing Zephyr (or NCS) Project

Golioth removes the pain of connecting constrained devices to the cloud. This post shows you how to add Golioth to your existing Zephyr project and get your first device connected.

Free Zephyr Training: February 26th, 2025

Golioth is hosting a free Zephyr training on February 26th, 2025. Join us for this three-hour crash course that will get you up to speed with the basics of building IoT applications using Zephyr RTOS.

Using Zephyr SMP with Multiple MCUs

It's easy to see that Golioth makes firmware updates for internet-connected devices a snap. But combine Golioth Cohorts, our improved OTA event log, and interconnectivity tools like SMP, and you end up with a powerful OTA scheme for all of the controllers in a complex system.

Zephyr for Hardware Engineers: Changing Boot Configurations

Zephyr board configurations can be changed from within your overlay files for your application. In this article, we show how you can change the properties and nodes of your devicetree to create different behavior during boot.

Use Zephyr SoC config files to streamline hardware types

Zephyr configuration that is specific to the chip, not just the board itself, can be centralized in your application. This means less duplication of configuration options across your IoT board definitions which improves both readability and maintainability of your code.

Want to stay up to date with the latest news?

We would love to hear from you! Please fill in your details and we will stay in touch. It's that simple!