[beagleboard] Re: Explanation of PRU Programming in C

On Tuesday, May 16, 2017 at 1:01:55 AM UTC+2, Clark Sann wrote: > > Hi Joseph > > Nice writeup. You did a good job of explaining a complex topic...at least > it seems complex to me. I have however found a possible error. > > Shouldn't you be referring to the DEFAULT_INC value rather than the >

[beagleboard] Re: 4.4.x-ti kernel with rproc & uio (r34)

On Wednesday, July 6, 2016 at 4:56:13 PM UTC+2, RobertCNelson wrote: > > Step 3: (uio) > > Edit your device tree: > > nano src/arm/am335x-bonegreen.dts > > Change: > /* #include "am33xx-pruss-uio.dtsi" */ -> #include "am33xx-pruss-uio.dtsi" > make ; sudo make install > > set blacklist: > >

[beagleboard] How to use shared memory between PRU and ARM (in C): an example

Here's an example I'd like to make share: how to use shared memory between PRU and ARM using uio_pruss and prussdrv: http://catch22.eu/beaglebone/beaglebone-pru-ipc/ Feel free to comment here on this forum post. There's also a git repository

[beagleboard] Re: Explanation of PRU Programming in C

Updated link: http://catch22.eu/beaglebone/beaglebone-pru-c/ -- 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

Re: [beagleboard] Re: Explanation of PRU Programming in C

Thanks for the positive feedback. The TI video does not work on Mac though. I've now also included the hello world blink LED in C. > On 19 Apr 2017, at 19:38, Greg wrote: > > Excellent! I did a couple of projects with PRU and C code, and this type of > tutorial is

[beagleboard] Explanation of PRU Programming in C

Hi guys, after a deep dive, I've found how to program to PRU in C (instead of Assembly). Here's my contribution: http://catch22.eu/omnirobot/beaglebone-pru-c/ Feel free to comment on this forum! -- For more options, visit http://beagleboard.org/discuss --- You received this message because

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

quot;infests" TI kernels ? using something like 50M + memory > needlessly . . . > > > > On Tue, Jul 19, 2016 at 9:52 AM, Joseph Heller <joseph.h...@gmail.com > > wrote: > >> Finally, that worked William ( )! I did a small check with an >> LED and am a

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

s far as I could tell a couple of weeks ago this is not possible with remoteproc. I might be wrong though, but this is how I came to the conclusion to go for uio. Regards, Maarten On Tuesday, July 19, 2016 at 7:05:33 PM UTC+2, RobertCNelson wrote: > > Hi Joseph, > > On Tue, Jul 19, 20

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

he device tree file loaded successfully:* > william@beaglebone:~$ lsmod |grep uio > uio_pruss 4928 0 > uio_pdrv_genirq 3539 0 > uio 8822 2 uio_pruss,uio_pdrv_genirq > > On Mon, Jul 18, 2016 at 1:12 PM, Robert Nelson <robert...@gmail.

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

loader does not work yet because of this, and quits with prussdrv_open() failed So I think I need to figure out a bit of my device tree to get the correct pinmuxing / overlay file now. On Sunday, July 17, 2016 at 6:44:08 PM UTC+2, Joseph Heller wrote: > > ok thanks William for the he

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

t;>> william@beaglebone:~$ uname -r >>>> 4.4.14-ti-rt-r34 >>>> >>>> william@beaglebone:~$ cat /etc/dogtag >>>> BeagleBoard.org Debian Image 2016-05-01 >>>> >>>> william@beaglebone:~/dev/dtb-4.4-ti$ grep "#include&qu

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

peaking to can show you exactly how to set > up uio_pruss on the newer TI kernels . . . Then just ignore that person, as > he / she has no idea what they're talking about. > > I should have time today to test this myself and it won't take all day. > Maybe an hour. > > On Sat,

[beagleboard] Where to find release notes of the images (and kernel)?

Could not find the answer yet, so posting it here: Where to find release notes of the beaglebone images (and kernel)? Assuming they are somewhere, are they? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

That sound like choosing either: "Robert didn’t use overlays" or "all you need to do is load the PRU overlay file to get uio_pruss working" Not done here yet with trying both options, but took me a day so far stretching my patience in reality. --> Is there a kernel or preferably an image

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

Did not get uio driver up and running yet, is this still an issue on the 4.4 kernel? I did not see a confirmation reading this post either. Tried both loading via device tree (uio_pruss_enable) or plain insmod

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

Sorry for any confusion, but I'd like to use uio On Thursday, July 14, 2016 at 7:50:58 PM UTC+2, john3909 wrote: > Overlay for Remoteproc doesn’t work so you must follow Roberts > instructions to select between rproc or uio: > -- For more options, visit http://beagleboard.org/discuss ---

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

On Thursday, July 14, 2016 at 8:18:37 PM UTC+2, William Hermans wrote: > > Well, I used apt-get install. I traced back the command entered when >> examining .bash_history: >> *# sudo apt-get install linux-image-4.1.15-bone-rt-r18 * > > > So you say it just failed, and when you examined the

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

On Wednesday, July 13, 2016 at 10:19:11 PM UTC+2, William Hermans wrote: > > By the way, TI's most recent kernels are purportedly supposed to use > either remoteproc, or uio_pruss. I say purportedly because I have not > personally experimented with that yet, but Robert made a post not long ago

Re: [beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

On Wednesday, July 13, 2016 at 10:11:56 PM UTC+2, William Hermans wrote: > > The traditional Debian way, you use APT. Something like . . . > > *william@beaglebone:~/dev$ apt-cache search linux-image | grep 4.1.15-bone* > linux-image-4.1.15-bone-rt-r17 - Linux kernel, version 4.1.15-bone-rt-r17 >

[beagleboard] Kernel change and naming convention (for the sake of uio / prussdrv)

Ok guys, here is my first question on how to change to another kernel version. I'm using a BBG for my omni-robot project, and started opting for using the PRU's to generate accurate variable frequency PWM signals for my stepper motors (my c code was still showing the occasional delays in