Bluesky has seen a large increase in its number of users over the last few weeks. To learn more about how the AT Protocol works, we set up a Pipeline to allow for microcontrollers to post to Bluesky via Golioth.
If you have ever tried communicating with a device on a private network, you may have encountered Network Address Translation (NAT). Because the number of connected devices has long outpaced the number of unique addresses in the IPv4 address space, public IP addresses have to be shared between devices. This introduces a number of challenges.
Did you know that Zephyr doesn't have a plain old GPIO example? The closest thing is the blinky example that controls LEDs. Why is that? Zephyr expects you to write your own devicetree bindings. It's not that hard, and it's the topic of today's post.
Take a deeper look inside the Bluetooth Mesh demo that connects to the Cloud via Golioth. Sandra Capri of Ambient Sensors (a Golioth Design partner) walks through the code and workflow of this demo.
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.
Golioth attended the Hackaday Superconference in 2023 and created a "badge hack" to send images from a tiny embedded device up over a cellular network and display on badgecase.io.
