<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[GPIO Problem [Solved]]]></title><description><![CDATA[<p dir="auto">Is there anything special about GPIO 0 and 1?  The reason I ask is that I have a small opto-isolated relay board which works perfectly if I connect it to GPIO 0 or 1, but none of the other GPIO pins operate the relay despite gpio and fast-gpio apparently changing the pin status in the same way.</p>
<p dir="auto">I have two Omega 2 boards and they both behave identically.</p>
<p dir="auto">I'm running the latest firmware on both boards.[link text](link url)</p>
]]></description><link>http://community.onion.io/topic/2029/gpio-problem-solved</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Apr 2026 08:25:51 GMT</lastBuildDate><atom:link href="http://community.onion.io/topic/2029.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 05 May 2017 15:04:47 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to GPIO Problem [Solved] on Sun, 07 May 2017 19:20:25 GMT]]></title><description><![CDATA[<p dir="auto">Is there anything special about GPIO 0 and 1?  The reason I ask is that I have a small opto-isolated relay board which works perfectly if I connect it to GPIO 0 or 1, but none of the other GPIO pins operate the relay despite gpio and fast-gpio apparently changing the pin status in the same way.</p>
<p dir="auto">I have two Omega 2 boards and they both behave identically.</p>
<p dir="auto">I'm running the latest firmware on both boards.[link text](link url)</p>
]]></description><link>http://community.onion.io/post/12976</link><guid isPermaLink="true">http://community.onion.io/post/12976</guid><dc:creator><![CDATA[racarter]]></dc:creator><pubDate>Sun, 07 May 2017 19:20:25 GMT</pubDate></item><item><title><![CDATA[Reply to GPIO Problem [Solved] on Sun, 07 May 2017 07:11:51 GMT]]></title><description><![CDATA[<p dir="auto">Run <code>omega2-ctrl gpiomux get</code> in console and show results.<br />
I had a very similar problem when writing an LCD driver and it all eventually ended up in having wrong <code>gpiomux</code> configuration.</p>
]]></description><link>http://community.onion.io/post/13001</link><guid isPermaLink="true">http://community.onion.io/post/13001</guid><dc:creator><![CDATA[Patryk Wychowaniec]]></dc:creator><pubDate>Sun, 07 May 2017 07:11:51 GMT</pubDate></item><item><title><![CDATA[Reply to GPIO Problem [Solved] on Sun, 07 May 2017 19:19:33 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/3691">@Patryk-Wychowaniec</a> Thanks - that allowed me to see which pins are set to gpio duty and solved my problem!</p>
]]></description><link>http://community.onion.io/post/13010</link><guid isPermaLink="true">http://community.onion.io/post/13010</guid><dc:creator><![CDATA[racarter]]></dc:creator><pubDate>Sun, 07 May 2017 19:19:33 GMT</pubDate></item></channel></rss>