[beagleboard] Shared PRU Memory and beyond

Currently working with the Beaglebone Black Rev C and the PRU has the following arrangement: PRU0 = 8k RAM, PRU1 = 8k RAM, and 12k RAM Shared I have successfully been able to have one PRU access its own 8K, the other PRU's 8K, and the shared 12K. This

[beagleboard] Re: Shared PRU Memory and beyond

PDT), in > gmane.comp.hardware.beagleboard.user Bruce Chidester > wrote: > >This leaves me with a total memory of 28K. Storing float's I can store > >7,168 values. I would like to capture 20,000 values in about 250ms. > > Capture from what? > > 80 samples/msec... or 8 per second. If I converted

Re: [beagleboard] Re: PRU Messaging

t; > > On Mon, May 24, 2021 at 10:44 AM, Bruce Chidester > wrote: > > Maybe some code in the post will promote some response: > > *Main Application:* > > #include > #include > #include > #include > #include > #include > #include > #define DE

[beagleboard] Re: PRU Messaging

io0.rpmsg-pru.-1.30: new rpmsg_pru device: /dev/rpmsg_pru30 and the device does not show in /dev/ What is the secret to making those devices show up? On Tuesday, May 25, 2021 at 11:25:28 AM UTC-5 Bruce Chidester wrote: > Dennis, > > I have made a flasher and have flashed 10.9 im

[beagleboard] Re: PRU Messaging

AM UTC-5 Dennis Bieber wrote: > On Tue, 25 May 2021 07:40:20 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user Bruce Chidester > wrote: > > >*It is asking you to confirm which Beagle you are using.:* > >I am using Beaglebone Black Revision C > > > > >

[beagleboard] Re: PRU Messaging

, May 24, 2021 at 3:01:50 PM UTC-5 Dennis Bieber wrote: > On Mon, 24 May 2021 10:25:57 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user Bruce Chidester > wrote: > > > >*2 This is the BB AI correct?* > >I do not know what this question means..please clarify

Re: [beagleboard] Re: PRU Assumptions - True or False

Does the 5.x kernel support an interrupt from the PRU while also supporting the bi-directional messaging through rproc? On Friday, May 28, 2021 at 12:38:08 PM UTC-5 RobertCNelson wrote: > On Fri, May 28, 2021 at 12:36 PM Robert Nelson > wrote: > > > > On Fri, May 28, 2021

[beagleboard] PRU Messaging

Group, I have been attempting to make a messaging example and I am either very close or so far away I don't realize it since I cannot seem to get it to respond. Once I get it working I will leave the answer for the world, please help me get this example working. It is at:

[beagleboard] SOLUTION - Missing /dev/rpmsg_pru30 and /dev/rpmsg_pru31

I am in the middle of struggling while introducing myself to the PRU. I want to contribute to the world to help some other struggling individual and this seems like the right place to post a solution. I am using Beaglebone Black Rec C. Running the

[beagleboard] SOLUTION - Fully functioning PRI interrupting the host example

This is a fully functioning PRU interrupt example that works on my BBB revision C board. This example demonstrates the PRU interrupting the host using PRU0 and PRU1. This example is ready to compile and ready-to-run example that had both the application code and the PRU code together. Hope

[beagleboard] SOLUTION - Fully functioning example of a PRU interrupting a host application

This is a fully functioning PRU interrupt example that works on my BBB revision C board. This example demonstrates the PRU interrupting the host using PRU0 and PRU1. This example is ready to compile and ready-to-run example that had both the application code and the PRU code together. Hope

[beagleboard] Re: PRU Assumptions - True or False

9:35 AM UTC-5 Dennis Bieber wrote: > On Fri, 28 May 2021 08:13:05 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user Bruce Chidester > wrote: > > >I am using BBB Revision C > > > >Please help me get clarity on my assumptions that I believe I have > learned

Re: [beagleboard] Re: PRU Assumptions - True or False

28 May 2021 08:13:05 -0700 (PDT), in > > gmane.comp.hardware.beagleboard.user Bruce Chidester > > wrote: > > > > >I am using BBB Revision C > > > > > >Please help me get clarity on my assumptions that I believe I have > learned > > >so

Re: [beagleboard] Re: PRU Messaging

t=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers_wl=ym_sub1=Internal_sub2=Global_YGrowth_sub3=EmailSignature> > > On Tue, May 25, 2021 at 11:47 AM, Bruce Chidester > wrote: > > I have a new image with 10.9 installed with an apt update; apt upgrade > > I wonder if my iss

Re: [beagleboard] Re: PRU Messaging

h (including updates), > was to start with Professor Yoder's PRUCookbook > <https://markayoder.github.io/PRUCookbook/>. That at least should get > you going. He has information on BBB as well as BBAI. > > df > > > On Tue, May 25, 2021 at 11:51 AM Bruce Chidester &

Re: [beagleboard] SOLUTION - Missing /dev/rpmsg_pru30 and /dev/rpmsg_pru31

> > > > > Sent from Yahoo Mail on Android > <https://go.onelink.me/107872968?pid=InProduct=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers_wl=ym_sub1=Internal_sub2=Global_YGrowth_sub3=EmailSignature> > > On Thu, May 27, 2021 at 12:00 PM, Bruce Chidester > wrote

[beagleboard] PRU Assumptions - True or False

I am using BBB Revision C Please help me get clarity on my assumptions that I believe I have learned so far and tell me where I am incorrect: 1. There are 2 architectures to interact with the PRU's. They are *UIO* and *RemoteProc*. And they can easily be selected in the /boot/uEnv.txt file.

[beagleboard] SOLUTION - Fully functioning PRU RProc Messaging example

This is a fully functioning PRU RProc Messaging example that works on my BBB revision C board. The thing that makes this solution unique is as of this date of writing, I could not find a ready to compile and ready to run example that had both the application code and the PRU code together.

[beagleboard] Re: PRU Messaging

0); __R31 = PRU_ARM_INTERRUPT_PULSE; // Clear interrupt CT_INTC.SICR = 15; } } On Sunday, May 23, 2021 at 2:10:24 PM UTC-5 Bruce Chidester wrote: > Group, > > I have been attempting to make a messaging example and I am either very > close or so far away I don't realize it since I