<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hey Angelo,<div class=""><br class=""></div><div class="">If you have about an hour, listen to the embedded.fm podcast #110 (<a href="http://www.embedded.fm" class="">www.embedded.fm</a> or iTunes). They talk with Jason Kridner of <a href="http://Beagleboard.org" class="">Beagleboard.org</a>, also from TI. He wants people to send him queries about the Beagle Boards, like your pinout questions.</div><div class=""><br class=""></div><div class="">RTEMS even comes up in the conversation.</div><div class=""><br class=""></div><div class="">Andrei</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 2015-July-28, at 01:19, Angelo Fraietta <<a href="mailto:newsgroups@smartcontroller.com.au" class="">newsgroups@smartcontroller.com.au</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I can confirm that the interrupts do work, however, it is on both edges, not just the rising.<div class="">I wanted to see what sort of performance I could get out of the interrupts by inputting various frequency signals</div><div class="">I modified the code so 13 would toggle every 8 interrupts. It toggled after four full pulses, therefore it interrupted on both edges (see code at end)</div><div class=""><br class=""></div><div class="">Also, I found that it took 1.3us to service the interrupt (I measured the time between the edge of interrupt pin and the toggle point of 13). The beagle is supposed to be 1 1GHz machine. Is there any way I can push faster than 1.3us with a setting in RTEMS (eg nanoseconds per tick) or is 1.3us my absolute best?</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class=""><div class=""><br class=""></div><div class="">//ISR:</div><div class="">rtems_isr GPIO1_IRQHandler (rtems_vector_number vector)</div><div class="">{</div><div class=""> static int i = 0;</div><div class=""><br class=""></div><div class=""> i++;</div><div class=""> //Toggle other three LEDs here:</div><div class=""> *(unsigned long *)(GPIO1_ADDR+GPIO_DATAOUT) ^= ((1<<22)| (1<<23) |(1<<24));</div><div class=""> </div><div class=""> //Clear interrupt:</div><div class=""> //Per AM335x technical reference manual, we can read IRQSTATUS,</div><div class=""> // and then write corresponding bits on IRQSTATUS to clear whichever one was serviced.</div><div class=""> // in this application it's hard coded to number 12 so I just write that bit.</div><div class=""> // For some reason writing IRQSTATUS value back to itself doesn't clear the interrupt.</div><div class=""> unsigned long irqstat = *(unsigned long*)(GPIO1_ADDR + GPIO_IRQSTATUS_1);</div><div class=""> *(unsigned long*)(GPIO1_ADDR + GPIO_IRQSTATUS_1) = (1<<12);</div><div class=""><br class=""></div><div class=""> // we will toggle every </div><div class=""> //*(unsigned long*)(GPIO1_ADDR + GPIO_IRQSTATUS_1) = irqstat;</div><div class=""> if (!(i % 4))</div><div class=""> {</div><div class=""> *(unsigned long *)(GPIO1_ADDR+GPIO_DATAOUT) ^= (1<<13);</div><div class=""> }</div><div class="">}</div></div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Jul 28, 2015 at 1:54 AM, Steve B <span dir="ltr" class=""><<a href="mailto:sbattazzo@gmail.com" target="_blank" class="">sbattazzo@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class=""><div class=""><div class=""><div class="">Hi Angelo,<br class=""><br class=""></div>Here's a handy diagram that shows which ones are which (found on Google Images):<br class=""><a href="http://cholla.mmto.org/computers/beagle/hardware/pinout1-1024x585.png" target="_blank" class="">http://cholla.mmto.org/computers/beagle/hardware/pinout1-1024x585.png</a><br class=""><br class=""></div>GPIO1_12 is connector P8 pin 12. I think I used the adjacent pin (P8 pin 11, or GPIO1_13) and installed a jumper wire between the two.<br class=""></div><div class="">I think it says so in my comments too but I know that may not exactly jump out.<span class="HOEnZb"><font color="#888888" class=""><br class=""><br class=""></font></span></div><span class="HOEnZb"><font color="#888888" class="">Steve</font></span><span class=""><br class=""><div class=""><div class=""><br class=""><div class=""><div class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sun, Jul 26, 2015 at 6:38 PM, Angelo Fraietta <span dir="ltr" class=""><<a href="mailto:newsgroups@smartcontroller.com.au" target="_blank" class="">newsgroups@smartcontroller.com.au</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Greetings Steve, I have modified your code so the standard task only toggles one LED and the interrupt on GPIO12 should toggle the other 3. However, IO cannot for the life of me find which pin is GPIO12 so I can test on the hardware. I have posted the code with the mods I made at the bottom of this email<div class=""><br class=""></div><div class=""><a href="http://beagleboard.org/support/bone101" target="_blank" class="">http://beagleboard.org/support/bone101</a><br class=""></div><div class=""><br class=""></div><div class="">What physical pin should I be toggling to make it work?</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><br class=""></div></blockquote></div></div></div></div></div></div></span></div>
</blockquote></div><br class=""></div>
_______________________________________________<br class="">users mailing list<br class=""><a href="mailto:users@rtems.org" class="">users@rtems.org</a><br class="">http://lists.rtems.org/mailman/listinfo/users</div></blockquote></div><br class="">
<br class=""></div></body></html>