[beagleboard] Host Pru Synchronization
I thought I submitted this question but I can't find it so maybe i didn't
hit post. If it is a duplicate, I apologize.
I am trying to figure out the pru and see how I would use it in my
application. I am using the beta c libraries, which may be a problem.
All of the things I am doing I have made to work individually. I just can't
get them to all work together.
My goal here is to synchronize a set of commands to the pru.
The Pru code is:
for (i = 0; i < 3; i++){
waitForHost();
//" CLR R31, R31, 30 \n"
//" WBS R31, 30 \n"
//" CLR R31, R31, 30 \n"
readInstruction();
// perform task
notifyHost();
//" LDI R31.b0, PRU0_ARM_INTERRUPT + 16 \n"
}
the Host code is:
initializeApplication();
for (i = 0; i < 3; i++){
writeInstruction();
notifyPru();
//prussdrv_pru_send_event(ARM_PRU0_INTERRUPT);
waitForPru();
//prussdrv_pru_wait_event(PRU_EVTOUT_0);
//prussdrv_pru_clear_event(PRU_EVTOUT_0, PRU0_ARM_INTERRUPT);
}
I added a write to shared memory location 0 for debug and when I run this
once the pru gets the first notification
it does not stop at the waitForHost() at the top of the loop. The loop
index is 2, never stopping at 0 or 1.
if I comment out the notifyPru(); call the pru waits and does not execute
the loop.
I can either get it to not execute any passes or all of them at once.
Any light would be appreciated.
--
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Host - Pru synchronization
I am trying to understand how to take advantage of the pru to see if I can
use it in my application.
I am trying to synchronize the pru execution from the host. I am using the
c libraries, which could be a proble. What I am doing is simple enough
that I don't think this should be a problem unless it really just doesn't
work.
My pru code looks like this:
for (i = 0; i < 3; i++){
waitForHost()
// " CLR R31, R31, 30 \n"
// " WBS R31, 30 \n"
// " CLR R31, R31, 30 \n"
readInstruction();
// read from shared memory location
// do work for instruction
notifyHost()
// " LDI R31.b0, PRU0_ARM_INTERRUPT + 16 \n"
}
the host loop is:
// Initialize the pru
for (i = 0; i < 3; i++){
// write to shared memory location
writeInstruction();
// Tell the pru to read the instruction
notifyPru();
// prussdrv_pru_send_event(ARM_PRU0_INTERRUPT);
// Wait for pru to complete the operation
waitForPru();
// prussdrv_pru_wait_event(PRU_EVTOUT_0);
// prussdrv_pru_clear_event(PRU_EVTOUT_0, PRU0_ARM_INTERRUPT);
}
For debugging the pru writes the loop index to shared memory location 0.
As is, the first time the host reads the debug location, its value is 2 and
never is 0 or 1.
It is as if the first time the pru is notified, it runs to completion, not
stoping for the waitForHost at the top of the loop.
If I comment out the notifyPru() in the host, the host hangs waiting for
the pru because the pru is still waiting.
Any help would be appreciated.
--
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Host - Pru synchronization
On 9/26/2014 10:33 AM, Ray Madigan wrote:
>
> My pru code looks like this:
>
> for (i = 0; i < 3; i++){
> waitForHost()
> // " CLR R31, R31, 30 \n"
> // " WBS R31, 30 \n"
> // " CLR R31, R31, 30 \n"
> As is, the first time the host reads the debug location, its value is 2 and
> never is 0 or 1.
> It is as if the first time the pru is notified, it runs to completion, not
> stoping for the waitForHost at the top of the loop.
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
char...@steinkuehler.net
--
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Host - Pru synchronization
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 > cha...@steinkuehler.net > -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Host - Pru synchronization
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 >> cha...@steinkuehler.net -- Charles Steinkuehler char...@steinkuehler.net signature.asc Description: OpenPGP digital signature
Re: [beagleboard] Host - Pru synchronization
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 LDIR17, 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 > >> cha...@steinkuehler.net > > -- > Charles Steinkuehler > cha...@steinkuehler.net > > -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Host - Pru synchronization
Some PRU code samples: https://github.com/jstampfl?tab=repositories On Fri, Oct 3, 2014 at 12:14 PM, Ray Madigan 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 > LDIR17, 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 >> >> cha...@steinkuehler.net >> >> -- >> Charles Steinkuehler >> cha...@steinkuehler.net >> >> -- > 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 beagleboard+unsubscr...@googlegroups.com. > 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Host - Pru synchronization
I believe the readme that comes with the PRU pckage has it pretty much covered, but i did see a website or something that had a listing of all the instructions . . . On Thu, Oct 2, 2014 at 9:14 PM, Ray Madigan 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 > LDIR17, 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 >> >> cha...@steinkuehler.net >> >> -- >> Charles Steinkuehler >> cha...@steinkuehler.net >> >> -- > 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 beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
