[beagleboard] Re: pru + 4.4 kernel?

Jay, you have to do a minimal edit to the device tree and rebuild the blobs. I'm pretty sure 4.4.x kernels will require this (not sure exactly when this was rolled out). Clone this to your Beaglebone: https://github.com/RobertCNelson/dtb-rebuilder Look in the directory src/arm. Find the file:

[beagleboard] Re: pru + 4.4 kernel?

Sadly this did not work. I'm using the default kernel/setup from the image bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz . It uses kernel 4.4.30-ti-r64. Is there something better to start with?

Re: [beagleboard] Re: pru + 4.4 kernel?

On Thu, Dec 15, 2016 at 8:40 PM, Jay Doobie wrote: > Sadly this did not work. I'm using the default kernel/setup from the > image bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz > . > It uses kernel

Re: [beagleboard] Re: pru + 4.4 kernel?

I figured out what happened, it wasn't am335x-boneblack.dts, but am335x-boneblack-wireless.dts. Seems like I can talk to the PRU, but I don't see it doing what it should be doing. Need to grab a copy of prudebug and see if I can debug what the PRU is trying to do vs. is doing. Thanks! On Thu

Re: [beagleboard] Re: pru + 4.4 kernel?

Hello Jay! You need not adapt the device tree when you use a bone kernel. (The device tree fixup is for TI kernels only.) Am Freitag, 16. Dezember 2016 05:44:26 UTC+1 schrieb Jay Doobie: > > I figured out what happened, it wasn't am335x-boneblack.dts, but > am335x-boneblack-wireless.dts. Seems

Re: [beagleboard] Re: pru + 4.4 kernel?

Hi TJF: is there some place I can find more info on the DT's across kernels? I'm using 4.4.30-ti-r64. I have access to the PRU, and I think my DT isn't updating anything (even though it seems to install properly). My DT can be seen here: https://github.com/doobie42/OpenPegasus/blob/master/dt

Re: [beagleboard] Re: pru + 4.4 kernel?

Jay, If by "updating" you mean your overlay isn't loading at boot. That would be because the overlay is not in the initramfs. Which is needed for the latest images. I actually posted on the groups about this a few days go, so I'll find my post and copy paste the procedure here. If this is not wha

Re: [beagleboard] Re: pru + 4.4 kernel?

> > So whatever way that works for you, is the right way. But yes, in my own > opinion loading from uEnv.txt is the proper way. As the pin configurations > take place the quickest possible after a boot. > > >1. So you need the overlay in /lib/firmware of course. >2. Then you need to add the

Re: [beagleboard] Re: pru + 4.4 kernel?

I was grepping /sys/kernel/debug/pinctrl/44e10800.pinmux/pins for 994 -B 4 -A4 and loading my overlay manually: "echo openpegasus > /sys/devices/platform/bone_capemgr/slots" According to dmesg it seems like it accepts my overlay without error. I'll keep the above in mind when I try to load it

Re: [beagleboard] Re: pru + 4.4 kernel?

Jay, Ok, so can you describe in more detail what the problem is ? Also pasting the output of the commands you're running to test your overlay may help too. On Fri, Dec 16, 2016 at 11:45 AM, Jay Doobie wrote: > I was grepping /sys/kernel/debug/pinctrl/44e10800.pinmux/pins for 994 -B > 4 -A4 > >

Re: [beagleboard] Re: pru + 4.4 kernel?

Ya know, I figured out what happened, I wish things were a bit better documented, what you indicated above about creating the initramfs fixed it. I believe what happened was I modifed the uEnv.txt file and thought it took my changes, but it didn't. I was running still with HDMI enabled and th

Re: [beagleboard] Re: pru + 4.4 kernel?

On Fri, Dec 16, 2016 at 11:55 AM, Jay Doobie wrote: > Ya know, I figured out what happened, I wish things were a bit better > documented, what you indicated above about creating the initramfs fixed > it. I believe what happened was I modifed the uEnv.txt file and thought it > took my changes, bu

Re: [beagleboard] Re: pru + 4.4 kernel?

Yeah, of course now the PRU died, which I had working before .time to debug that again :) On Friday, December 16, 2016 at 2:00:53 PM UTC-5, William Hermans wrote: > > > > On Fri, Dec 16, 2016 at 11:55 AM, Jay Doobie > wrote: > >> Ya know, I figured out what happened, I wish things were a bit

Re: [beagleboard] Re: pru + 4.4 kernel?

I have no idea what I did, but I'm back to nothing working and have been unable to get the PRU working ( prussdrv_open(PRU_EVTOUT_0) fails in my program), nor am I able to have my DTO configure the pinmux anymore. Is there a way to increase debug levels so I can see what is going on when it tri

Re: [beagleboard] Re: pru + 4.4 kernel?

On Fri, Dec 16, 2016 at 9:11 PM, Jay Doobie wrote: > I have no idea what I did, but I'm back to nothing working and have been > unable to get the PRU working ( prussdrv_open(PRU_EVTOUT_0) fails in my > program), nor am I able to have my DTO configure the pinmux anymore. Is > there a way to increas

Re: [beagleboard] Re: pru + 4.4 kernel?

Thanks, that is really sweet looking! No matter what I do when I load my DTO it doesn't seem to change the pinmux/ctrl values unfortunately. Everything in dmesg, journalctl acts as if it worked successfully, but I see no change to the pinmux/ctlr. Is there a kernel (or bone_capemgr) level of deb

Re: [beagleboard] Re: pru + 4.4 kernel?

I also just realized, I posted this in the BBB group, not the BBB wireless one. It is a wireless BBB I just received the other day. On Friday, December 16, 2016 at 10:52:27 PM UTC-5, Jay Doobie wrote: > > Thanks, that is really sweet looking! No matter what I do when I load my > DTO it doesn't

Re: [beagleboard] Re: pru + 4.4 kernel?

Jay, So keep this in mind, 99% chance, what you've done, you've somehow screwed up. Don't take this as a negative response please. But more or less a realistic response. I've done "similar" myself. the whole time, I might be thinking . .. "I'm going to let x.y.z have it on the groups . . ." only t

Re: [beagleboard] Re: pru + 4.4 kernel?

>From my own perspective, it does not matter one single bit. I suscribe to the beagleboard.org google group, i get all mails from that group. No idea of sub groups, or whatever. . . .quite honestly I don;t even care. If i know the answer or can give some clues, I'll answer, or give some clues. .

Re: [beagleboard] Re: pru + 4.4 kernel?

I certainly expect I screwed something up. I've yet to see a website that really does a good job describing how to get the pru enaled or setting a main DT or overlay. I was going to try to grab the source for my old main DT and see if I am missing something. I have't been able to get either th

Re: [beagleboard] Re: pru + 4.4 kernel?

Hi Jay, you are correct it is difficult to work through all the issues and find the right sources of information. I did attempt to document the current process for activating the PRU with Remoteproc: https://github.com/Greg-R/pruadc1 More specifically look in the PDF file: https://github.com/G

Re: [beagleboard] Re: pru + 4.4 kernel?

uEnv.txt: https://github.com/doobie42/OpenPegasus/blob/master/uEnv.txt Some progress that might shed light into issues? I have modified the dts files from the dts-rebuilder and in one I can access the PRU, and in the other I can get the pins set the way I want, but sadly not at the same time.

Re: [beagleboard] Re: pru + 4.4 kernel?

Not totally clear what you are saying. I see you have the UIO PRUSS line uncommented in "PRU works". It is not uncommented in "pinmux works". So are you saying when you uncomment the UIO PRUSS line to activate it, it kills the pinmux? Sorry for the confusion! On Saturday, December 17, 2016 at

Re: [beagleboard] Re: pru + 4.4 kernel?

Ahhh! Ok, I had modified things so much last night I went back to the original and forgot to update the uio pruss in the non-overlay version. It WORKS! When I was saying pinmux works, I guess I should have indicated that I was trying to set 990, 99c, 994 to 0x15. So it appears something in

Re: [beagleboard] Re: pru + 4.4 kernel?

Great news, keep going! Greg On Saturday, December 17, 2016 at 11:16:25 AM UTC-5, Jay Doobie wrote: > > Ahhh! Ok, I had modified things so much last night I went back to the > original and forgot to update the uio pruss in the non-overlay version. It > WORKS! > > When I was saying pinmux works