Regardless of the timing, you want to store 20,000 values but I think you've calculated correctly that you can only store 7,168 values in the 28k of combined PRU memory and that would only be true if some of the PRU memory wasn't used by your PRU program when it's loaded.
So are you trying to find a way to store the data back in the main host memory instead? Remoteproc/RPMSG can send the data back but I don't think it's fast enough for you. I'm doing that now with code written in C. (It was a bear to learn and get going but I'm a rusty guy too. ) I am reading 12-bit AD with the onboard ADC (Touchscreen controller in general-purpose mode). I saw one post on the TI E2E forum that indicated that Remoteproc/RPMSG is not intended to be a fast data transfer mechanism. That was by a TI engineer I think. The only alternative I can think of is declaring variables in your PRU code whose address is actually in the main host memory (Linux) space. I've tried to do this using the example in Mark Yoder's PRU Cookbook but I could not get it to work. I decided that I didn't really need that and went another route. @TJF on this forum promotes a solution called libpruio that might work. I don't know if it's fast enough though. This is a good group so keep the discussion going and maybe we can figure something out. On Monday, May 17, 2021 at 8:26:49 PM UTC-4 lazarman wrote: > Hello > > Google Am335x PRU Support package it's got 6 labs and examples including > ADC. > > It's written for the SDK Linux Dennis mentioned but people have gotten > these examples to work with Linux supported in this group > > There's also a Support package tar containing step by step HTML of all > the labs above preserved from the old wiki. > > There's several PDF files supporting all this some are application notes > > Getting started with RPMSg on Linux is one > > If you start with these HTML files it's really well written it's a how-to > > Labs 1 to 3 require CCS JTAG > > The other labs deal with Linux > > The ADC example passes samples back to Linux. > > For a full blown PID loop using both PRU there's a example code also on > GitHub preserved from TI support expert Nick. > > The PRU support package 5.8 code on GitHub or wherever get it in the > examples shows linker commands for using shared RAM. > > The concept in any book of accessing these has more to do with pragma or > compliler specific linker commands in gcc should not change > > Every book or cookbook or tutorial ever written was all this data I > pointed you to explained by an experienced engineer's using TI wiki Data > > That my opinion. > > Remember this stuff will talk about building code from command line in > the 4G SDK which requires a native Ubuntu box or a virtual box Ubuntu on > windows 7. Officially vbox support isn't suppored anymore but I got it > working recently only tested windows 7 > > All this discussion can be found by googling " PRU ADC beaglebone" > also many discussion on E2E forum replace Beaglebone with 2E > > I'd suggest reading that getting started first > > > Or use Mark Yoder's cookbook which is web-based compilation on the board > itself. I have not tried that > > Lastly if you take the Apple's and Oranges approach which is taking the > source code I mentioned and trying to follow the cookbook web based > compilation. Most people seem to fail trying this I don't recommend it > > Pick one approach > > > Good luck > Mark > > > > > > > > > Sent from Yahoo Mail on Android > <https://go.onelink.me/107872968?pid=InProduct&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature> > > On Mon, May 17, 2021 at 6:32 PM, Dennis Lee Bieber > <dennis....@gmail.com> wrote: > > On Mon, 17 May 2021 13:00:04 -0700 (PDT), in > gmane.comp.hardware.beagleboard.user Bruce Chidester > <brucechidester-re5...@public.gmane.org> wrote: > > > Not sure I am replying properly to preserve the format desired for this > >page, but your (Dennis B) response definitely deserves a response from me. > > Difficult -- somehow your added comments are formatted as quoted text > (ie, my comments). > > > > >On Monday, May 17, 2021 at 12:39:53 PM UTC-5 Dennis Bieber wrote: > > > > >> 80 samples/msec... or 80000 per second. If I converted properly, about > >> 0.0125msec per sample. > >> > >> I will be sampling from an ADC up to 1MHz maybe. > > The PRU itself only runs at 200MHz, and you have to account for how > many instructions are needed to run your ADC-start, read, store, notify > host logic. > > >> Does the second addition contain the updates to the remote proc process? > > > It uses Remote Proc for the examples -- but does NOT have ADC examples. > It does warn that Remote Proc/rpmsg is fairly new (at the time of the book) > and that things might change. Unfortunately TI has changed its document > access, so the links in the 2nd edition book don't work. Most of the > documentation seems to be at > > http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_PRU-ICSS_PRU_ICSSG.html#remoteproc-and-rpmsg > (note: processor SDK -- TI's raw OS build system). > > The examples are the simple Blink LED until Button Pressed; a PWM > generator, Ultrasonic distance sensor. > > >> Thanks for the DSP lead...that is awesome as well. > > On the BB AI -- and not much information has appeared on programming > > > them. > > > > -- > Dennis L Bieber > > -- > 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+unsub...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/v2u5ag1dlpbh5fkli20unvb8d8a2b254o3%404ax.com > . > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a53c9616-a9b6-4bda-9cfa-0db9ee494bf5n%40googlegroups.com.
