Some PRU code samples: https://github.com/jstampfl?tab=repositories
On Fri, Oct 3, 2014 at 12:14 PM, Ray Madigan <[email protected]> wrote: > Thanks for the reference document. I have been out of town all week and > am just getting back at this. I don't want to be told the answer, thats > just no fun. I am trying to figure out how this works so if someone can > tell me why I'm not thinking about this correctly that would be useful. > > I have tried many permutations of the following and can't seem to find > something to start with. > > #define ARM_PRU0_INTERRUPT 21 > #define CONST_PRUSSINTC C0 > #define SICR_OFFSET 0x24 > > // Load the interrupt number into register 17 > LDI R17, ARM_PRU0_INTERRUPT > // Write 4 bytes from R17 into pruss intc offset by the sicr > SBCO R17, CONST_PRUSSINTC, SICR_OFFSET, 4 > > Are there tutorials somewhere for this assmebly language, I haven't used > assembler since the 8080 :) > > > On Monday, September 29, 2014 3:44:59 PM UTC-7, Charles Steinkuehler wrote: >> >> Section 6.2.2.5 "Interrupt Status Clearing": >> >> https://github.com/beagleboard/am335x_pru_package/blob/master/ >> am335xPruReferenceGuide.pdf >> >> On 9/26/2014 6:47 PM, Ray Madigan wrote: >> > Thank you very much. >> > >> > I appreciate you taking time to help me figure this out. >> > >> > Now I just have to figure out how to do what you just said. >> > >> > On Friday, September 26, 2014 2:15:28 PM UTC-7, Charles Steinkuehler >> wrote: >> >> >> >> You can't clear bits in the status register, you have to clear >> whatever >> >> is generating the status bit directly. That's either an input pin or >> >> (in your case) the interrupt from the local INTC. >> >> >> >> So try clearing the actual interrupt bit, and the PRU code should then >> >> wait as expected for the next "handshake". I suspect the PRU is >> >> currently running to completion because you're never clearing the >> >> interrupt that kicks things off, so waitForHost() doesn't actually do >> >> anything after the first "wait" and simply falls through from then on. >> >> >> >> -- >> >> Charles Steinkuehler >> >> [email protected] <javascript:> >> >> -- >> Charles Steinkuehler >> [email protected] >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- John Stampfl -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
