<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>gpio Archives - The Golioth Developer Blog</title>
	<atom:link href="https://blog.golioth.io/tag/gpio/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.golioth.io/tag/gpio/</link>
	<description>Golioth, Zephyr, and IoT Development News and How Tos</description>
	<lastBuildDate>Mon, 03 Feb 2025 14:48:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://blog.golioth.io/wp-content/uploads/2023/09/cropped-Golioth_Symbol_Coral_RGB-1-32x32.png</url>
	<title>gpio Archives - The Golioth Developer Blog</title>
	<link>https://blog.golioth.io/tag/gpio/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Zephyr for Hardware Engineers: GPIO</title>
		<link>https://blog.golioth.io/zephyr-for-hardware-engineers-gpio/</link>
		
		<dc:creator><![CDATA[Chris Gammell]]></dc:creator>
		<pubDate>Thu, 05 Sep 2024 12:30:40 +0000</pubDate>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[Prototyping]]></category>
		<category><![CDATA[Zephyr]]></category>
		<category><![CDATA[Bindings]]></category>
		<category><![CDATA[Code Samples]]></category>
		<category><![CDATA[gpio]]></category>
		<guid isPermaLink="false">https://goliothblogdev.wpenginepowered.com/?p=7872</guid>

					<description><![CDATA[<p>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.</p>
<p>The post <a href="https://blog.golioth.io/zephyr-for-hardware-engineers-gpio/">Zephyr for Hardware Engineers: GPIO</a> appeared first on <a href="https://blog.golioth.io">The Golioth Developer Blog</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>How to Set Up ESP32 GPIO Pins in Zephyr</title>
		<link>https://blog.golioth.io/how-to-set-up-esp32-gpio-pins-in-zephyr/</link>
		
		<dc:creator><![CDATA[Mike Szczys]]></dc:creator>
		<pubDate>Tue, 11 Jan 2022 15:43:59 +0000</pubDate>
				<category><![CDATA[Zephyr]]></category>
		<category><![CDATA[button]]></category>
		<category><![CDATA[Device Tree]]></category>
		<category><![CDATA[ESP32]]></category>
		<category><![CDATA[gpio]]></category>
		<category><![CDATA[overlay]]></category>
		<guid isPermaLink="false">https://blog.golioth.network/?p=453</guid>

					<description><![CDATA[<p>Getting your ESP32 GPIO pins working with Zephyr is easy, and using a devicetree overlay file to do so makes it painless to change pins (or even boards/architectures) in the future. Today we&#8217;re looking at a simple overlay file for the ESP32 architecture and talking about the syntax used to choose input and output pins. [&#8230;]</p>
<p>The post <a href="https://blog.golioth.io/how-to-set-up-esp32-gpio-pins-in-zephyr/">How to Set Up ESP32 GPIO Pins in Zephyr</a> appeared first on <a href="https://blog.golioth.io">The Golioth Developer Blog</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
