<div dir="ltr">I just tried writing to the pins using the methods in the interrupt example<div><br></div><div>What is very strange is that pin P9-15 toggles whether I write to GPIO1_16 or GPIO2_0, which may be why the read is not correct on it</div><div><br></div><div>So in short, </div><div><div style="font-size:12.8000001907349px">I found that GPIO1_0 to GPIO1_3 did not read or write</div><div style="font-size:12.8000001907349px">I found that GPIO1_30 and GPIO1_31 <span style="font-size:12.8000001907349px">did not read or write</span><br></div><div style="font-size:12.8000001907349px">I found that GPIO0_4 and GPIO0_5 <span style="font-size:12.8000001907349px">did not read or write</span></div></div><div style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px"><br></span></div><div style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">P9-15 writes whether writing to </span><span style="font-size:small">GPIO1_16 or GPIO2_0</span></div><div style="font-size:12.8000001907349px"><span style="font-size:small"><br></span></div><div style="font-size:12.8000001907349px"><span style="font-size:small">Any suggestions form here would be great</span></div><div style="font-size:12.8000001907349px"><span style="font-size:small"><br></span></div><div style="font-size:12.8000001907349px"><span style="font-size:small">Thanks</span></div><div style="font-size:12.8000001907349px"><span style="font-size:12.8000001907349px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 29, 2015 at 2:46 PM, Angelo Fraietta <span dir="ltr"><<a href="mailto:newsgroups@smartcontroller.com.au" target="_blank">newsgroups@smartcontroller.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div>I found the GPIO3 issue<div>from <a href="https://github.com/majestik666/Beagle_GPIO/blob/master/Beagle_GPIO.cc" target="_blank">https://github.com/majestik666/Beagle_GPIO/blob/master/Beagle_GPIO.cc</a> I found the correct define would be</div><div><br><div>#define GPIO3_ADDR 0x481AE000<br></div></div><div><br></div><div>I just have to find out why the other pins failed</div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 29, 2015 at 1:30 PM, Angelo Fraietta <span dir="ltr"><<a href="mailto:newsgroups@smartcontroller.com.au" target="_blank">newsgroups@smartcontroller.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I have done some more tests to check whether all inputs actually work.<div>I set all as inputs like this in the init</div><div><div> *(unsigned long *)(GPIO0_ADDR+OE_ADDR) = 0xFFFFFFFF;</div><div> *(unsigned long *)(GPIO1_ADDR+OE_ADDR) = 0xFFFFFFFF;</div><div> *(unsigned long *)(GPIO2_ADDR+OE_ADDR) = 0xFFFFFFFF;</div><div> *(unsigned long *)(GPIO3_ADDR+OE_ADDR) = 0xFFFFFFFF;</div></div><div><br></div><div>And read them in a task while switching the pins between 1 and zero</div><div><br></div><div><div> data_0 = *(unsigned long *)(GPIO0_ADDR+GPIO_DATAIN);</div><div> data_1 = *(unsigned long *)(GPIO1_ADDR+GPIO_DATAIN);</div><div> data_2 = *(unsigned long *)(GPIO2_ADDR+GPIO_DATAIN);</div><div> data_3 = *(unsigned long *)(GPIO3_ADDR+GPIO_DATAIN);</div></div><div><br></div><div><br></div><div>I found that GPIO1_0 to GPIO1_3 did not work</div><div>I found that GPIO1_30 and GPIO1_31 did not work<br></div><div>I found that GPIO0_4 and GPIO0_5 did not work<br></div><div><br></div><div>I found GPIO1_16 is actually GPIO2_0 - which is very strange as all the other GPIO2 are on P8</div><div>I found none of GPIO3 read a value</div><div><br></div><div>Anyone have have any suggestions? Maybe an incorrect address for GPIO3?</div><span><div><div>#define GPIO0_ADDR 0x44E07000</div><div>#define GPIO1_ADDR 0x4804C000</div><div>#define GPIO2_ADDR 0x481AC000</div><div>#define GPIO3_ADDR 0x481AF000</div></div><div><br></div></span><div>Thanks</div></div><div class="gmail_extra"><br><div class="gmail_quote"><span>On Wed, Jul 29, 2015 at 11:49 AM, Chris Johns <span dir="ltr"><<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><span>On 29/07/2015 2:01 am, Joel Sherrill wrote:<br>
><br>
><br>
> On 7/28/2015 8:39 AM, Mr. Andrei Chichak wrote:<br>
>> Hey Angelo,<br>
>><br>
</span></span>>> If you have about an hour, listen to the <a href="http://embedded.fm" rel="noreferrer" target="_blank">embedded.fm</a> podcast #110<br>
>> (<a href="http://www.embedded.fm" rel="noreferrer" target="_blank">www.embedded.fm</a> <<a href="http://www.embedded.fm" rel="noreferrer" target="_blank">http://www.embedded.fm</a>> or iTunes). They talk with<br>
>> Jason Kridner of Beagleboard.org <<a href="http://Beagleboard.org" rel="noreferrer" target="_blank">http://Beagleboard.org</a>>, also from<span><br>
<span>>> TI. He wants people to send him queries about the Beagle Boards, like<br>
>> your pinout questions.<br>
>><br>
>> RTEMS even comes up in the conversation.<br>
>><br>
><br>
> I saw a tweet on this last week. I need to listen to Jason also.<br>
</span></span>> He is a nice guy and the <a href="http://embedded.fm" rel="noreferrer" target="_blank">embedded.fm</a> podcast is a great resource.<br>
><br>
<br>
Great podcast.<br>
<span><font color="#888888"><br>
Chris<br>
</font></span></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>