This blog, which originally ran on the Golioth Website, was written by Chris Wilson, the principal of Common Ground Electronics, a boutique embedded systems engineering services firm. For more content like this, click here.
Zephyr has a lot of tricks up its sleeve and most recently I used it to enable power regulators on a custom Golioth board. Perhaps the most interesting part of this is that it can be done entirely with the configuration code, without needing to dive in to any of the C files. And as the icing on the cake, Zephyr even includes interactive shell for working with regulators!
If you’ve been following our blog for a while, or you’ve checked out our growing library of reference designs, you’ll know that we’ve been using an internal hardware platform codenamed “Aludel” for rapid prototyping. Chris Gammell has been busy working on a new version of the Aludel main board with the ability to shut off power to the mikroBUS Click board sockets for low-power operation.
For example, a GPIO from the onboard nRF9160 SIP is connected to the EN pin on the +5V boost regulator. This grants Zephyr firmware the power (ha!) to enable or disable the regulator:
When the first prototype boards arrived from the manufacturer, we needed to enable these power regulators as part of the hardware bring-up process. I was pleasantly surprised to discover that this is actually possible to do entirely with Devicetree & Kconfig without writing any C code!
Zephyr’s regulator bindings
Out of the box, Zephyr provides regulator-gpio and regulator-fixed devicetree bindings for variable and fixed-voltage regulators respectively. These bindings are used to define GPIO-controlled power regulators that can be enabled automatically when the OS boots.
Here’s the devicetree node we’re using for the +5V boost regulator on the Aludel board:
The compatible property matches this node to Zephyr’s regulator-fixed device tree binding, and the regulator-name property is just a descriptive name for the regulator output.
Next, the enable-gpios property is a phandle-array devicetree property which defines the GPIO connected to the regulator’s EN pin:
&gpio0is the phandle for the GPIO0 controller node that controls the pin4is the pin number on the controller- the pin is configured with the
GPIO_ACTIVE_HIGHflag because the regulatorENpin is an active-high input
The regulator-boot-on property tells the regulator driver that the OS should turn on the regulator at boot (but shouldn’t prevent it from being turned off later). We just needed to set the following Kconfig symbol to enable the regulator drivers:
Regulator shell
When you’re bringing up a new board, it’s really helpful to have full control over the power regulators from a diagnostic shell. Zephyr provides a regulator shell that allows you to interact with regulators on your board via the shell interface!
Set the following Kconfig symbols to enable the regulator shell:
With the regulator shell enabled, you can enable/disable the regulator. You can also get/set parameters like voltage, current limit, and operating modes.
Regulator shell example
First, we need to get the device node for the regulator. You can list the available devices and their states using the device list shell command:
To disable the reg-mikrobus-5v regulator, we can run the following shell command:
To enable the reg-mikrobus-5v regulator again, we can run a similar shell command:
Time to hit that play button on some Warren G!
🎵 “Regulators, mount up!” 🎵
Learn more about the Zephyr shell
Controlling power regulators is just one of the neat things you can do with the Zephyr shell. At Golioth we think the Zephyr shell is fantastic and we’ve written extensively about it on our blog. We also use it in the Golioth SDK for things like setting device credentials.
If you’d like to learn more about Zephyr in general, join Golioth for free Zephyr training anytime, anywhere. Learn more here.