Firmware

Zephyr's west manifest system includes an allow-list to filter dependencies from upstream libraries (like the Zephyr tree itself). Use it to tightly control what libraries your projects use, and to stop checking out way too many unused code.

When it comes to automated testing, Zephyr's Native Simulator is worth your consideration. The next release of Zephyr will include offloaded sockets for Native Simulator, which means CI tests that complete many times faster than their native-hardware equivalents.

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.

Pytest is a framework for testing and we use it for our Firmware SDK. This post reviews setting up fixtures that connect embedded projects to pytest.

Golioth's Firmware SDK (v0.11.0) pulls in recent versions of different ecosystems, allowing developers to target a wide range of custom hardware.

Back in September, we released beta support for Zephyr RTOS in the Golioth Firmware SDK, as an...

Almost two years ago I wrote a guide on how to interface with USB devices from WSL2...