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

Well, I like to document stuff, as I'm a very technical person. The problem is, when you have a professional gig, and other things all happening at the same time. Some things just don't get done as often as I'd like. There is also a big difference between helping someone here, and writing blog po

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

Hello William, Nice page there William. Yes we have the right installation written above for using uio. Documenting it on eLinux seems to be the next logical thing also. I'm opting to help here, already registered with my account on eLinux, or go for a personal page as well. There's a weak s

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

Ok thanks Robert, Yes, well, some rationale at least from my side as input. After I've checked my options to go for PRU, I found there's both remoteproc and uio. At first glance, I did not like the remoteproc implementation as it appears to be more of an interrupt based approach. I think this

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

> > Actually, it's just my locally cross built kernel that have the large > modules, for the official *.deb, the *.ko objects are separate in the > linux-image-`uname -r`-dbg package. ;) (for gcc-4.7 + that is..) > > Yeah, just adding a blacklist for users who want to tune things is the > easiest w

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

On Tue, Jul 19, 2016 at 1:56 PM, John Syne wrote: > Hi Robert, > > I was one of those users who uses Systemtap, but I always build my own > kernel with debug symbols enabled, so I would recommend a standard kernel > version without debug symbols and if you are up to it, add another build > with a

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

Hi Robert, I was one of those users who uses Systemtap, but I always build my own kernel with debug symbols enabled, so I would recommend a standard kernel version without debug symbols and if you are up to it, add another build with a -dbg.deb kernel/modules version. Regarding the other kernel

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

Ok, thanks Robert. I am really starting to warm up to universal-io. Never had the chance, or reason to get it working before. Now . . . I'm using it to test custom cape circuits, and all kind of things. Plus I really do want to write that webpage GPIO / peripheral configuration page . . . but that

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

On Tue, Jul 19, 2016 at 12:24 PM, William Hermans wrote: > Ah those! most of them come from loading the cape overlay... >> (cape_universal=enable) >> >> Regards, > > Seriously ? Wow I had no idea. Is this a requirement, or can it be changed > ? Or . . .hmmm how could one modify this behavior so

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

temptation <--- wtf did that come from . . . dahm spell checker lol. *attemtping . . .* On Tue, Jul 19, 2016 at 10:24 AM, William Hermans wrote: > Ah those! most of them come from loading the cape overlay... >> (cape_universal=enable) >> >> Regards, > > Seriously ? Wow I had no idea. Is this a r

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

> > Ah those! most of them come from loading the cape overlay... > (cape_universal=enable) > > Regards, Seriously ? Wow I had no idea. Is this a requirement, or can it be changed ? Or . . .hmmm how could one modify this behavior so that only what's needed is loaded. Other than my hackish fix. Or,

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

Sorry Robert I did not mean to reply only directly to you . . . but also . . . a few users wanted to use systemtap: > > https://wiki.archlinux.org/index.php/SystemTap > > that needs debug_info.. > > So question about this. Are these few people more important than the rest of the users out here ? N

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

On Tue, Jul 19, 2016 at 12:06 PM, William Hermans wrote: > I think it's pretty well documented here. However you could always write > up an eLinux or whatever wiki page . . . I do have my own web page > http://www.embeddedhobbyist.com/ with stuff on it that is important to > me. But this informat

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

I think it's pretty well documented here. However you could always write up an eLinux or whatever wiki page . . . I do have my own web page http://www.embeddedhobbyist.com/ with stuff on it that is important to me. But this information for using UIO on TI kernels I feel is largely useless. Because

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

Hi Joseph, On Tue, Jul 19, 2016 at 11:52 AM, Joseph Heller wrote: > Finally, that worked William (&John &Robert)! I did a small check with an > LED and am able to with it on/off now via the PRU and uio. > > For your consideration, I wonder how you feel like to document this more > structurally s

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

Finally, that worked William (&John &Robert)! I did a small check with an LED and am able to with it on/off now via the PRU and uio. For your consideration, I wonder how you feel like to document this more structurally so others can benefit from it? I was offset by some older posts on the foru

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

Well, not to mention you installed a *bone* kernel anyhow. So what we're talking about is really moot. e.g. a topic for a different discussion. So. . . back on topic . . . *Download suitable linu image and reboot:* william@beaglebone:~$ sudo apt-get install linux-image-4.4.14-ti-r34 william@beagl

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

On Mon, Jul 18, 2016 at 3:08 PM, Joseph Heller wrote: > small progress here; > 4.4.x-ti r34 did not result in any good (only remoteproc as far as I could > tell), no uio. > > Therefore went for the bone version, non -rt: > > cd /opt/scripts/tools/ > sudo git pull > sudo ./update_kernel.sh --bone-

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

small progress here; 4.4.x-ti r34 did not result in any good (only remoteproc as far as I could tell), no uio. Therefore went for the bone version, non -rt: cd /opt/scripts/tools/ sudo git pull sudo ./update_kernel.sh --bone-kernel --lts-4_4 which gave me kernel 4.4.15-bone11 and a new dmes

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

ok thanks William for the heads-up. Did a check on 4.1.5-ti-r10, so the non-rt version, but no luck yet (but not out of options). Had one failure again truing to apt-get install a 4.1.5 bone15 kernel, so need to try that as well. I missed Robert's remark though earlier in the post to use 4.4.x-

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

So apparently you got bit by the rt kernel bug as many have in the past. So, if you want to use uio_pruss right now with TI's most recently kernel. You're going to have to opt out of using an rt kernel. Which honestly is not a huge deal. On Sat, Jul 16, 2016 at 4:58 PM, William Hermans wrote: >

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

RT kernel strikes again apparently . . . william@beaglebone:~/dev/dtb-4.4-ti$ sudo apt-get install linux-image-4.4.14-ti-r34 william@beaglebone:~/dev/dtb-4.4-ti$ sudo reboot william@beaglebone:~$ uname -r 4.4.14-ti-r34 william@beaglebone:~$ cd dev/dtb-4.4-ti/ william@beaglebone:~/dev/dtb-4.4-ti$

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

Right, and . . . william@beaglebone:~/dev/dtb-4.4-ti$ head /boot/uEnv.txt #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 uname_r=4.4.14-ti-rt-r34 #uuid= #dtb= ##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..) ##BeagleBone Black: HDMI (Audio/Video) d

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

Robert. You instructions here: https://groups.google.com/forum/#!searchin/beagleboard/Robert$20Nelson$20r34%7Csort:date/beagleboard/l59Dx8ygxNg/GhdRzR7IDAAJ do not work. I do not what to tell you other than I followed you instructions to the "T" and . . . william@beaglebone:~$ lsmod |grep uio ui

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

BTW, if you want to use 4.1 kernel, then use 4.1-bone for uio_pruss and 4.1-ti for remoteproc. Regards, John > On Jul 16, 2016, at 9:57 AM, Joseph Heller wrote: > > Hi William, thanks for the support, some input got me further at least. This > is how far I got today: I now have the uio dri

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

Hi Joseph, As I said before, Robert wasn’t able to get Remoteproc working using devicetree overlays, so he provided instructions on how to modify the devicetree and then use dtb-rebuilder to create dtbo file. The default is to have neither Remoteproc nor uio_pruss installed because most users d

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

I decided to follow Roberts instructions exactly. As I'm not a device tree overlay guru, and I'd have to fool around with the dtsi file, convert it into an overlay file, add a fragment . . . and asI said I'm no guru with that so. A project for a different time. Currently though I'm in the middle o

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

heh, ok back on "the job". I keep getting interrupted today . . . On Sat, Jul 16, 2016 at 11:24 AM, William Hermans wrote: > @Robert, I do not think he cares specifically about the TI kernel using > uio_pruss, he was just experimenting with it. But anyway, I'm testing your > instructions now, an

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

@Robert, I do not think he cares specifically about the TI kernel using uio_pruss, he was just experimenting with it. But anyway, I'm testing your instructions now, and will probably go about it slightly different than how you explained . . . but you know how I am. exact steps how to will follow.

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

On Jul 16, 2016 11:57 AM, "Joseph Heller" wrote: > > Hi William, thanks for the support, some input got me further at least. This is how far I got today: I now have the uio driver more or less enabled on 4.1.5-ti-rt-r10 via my DTS file: I thought i was very explicit in my email, 4.4.x-ti r34 or l

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

Hi William, thanks for the support, some input got me further at least. This is how far I got today: I now have the uio driver more or less enabled on 4.1.5-ti-rt-r10 via my DTS file: /dts-v1/; /plugin/; / { compatible = "ti,beaglebone", "ti,beaglebone-black"; part-number = "OMNI-ROBOT"

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

I was going to look into this yesterday, but did not for personal reasons. Anyway, no idea whom you're speaking to( I do not see all posts on this group ), but it does not matter what Robert demonstrated. From the information given fro Robert's post. It's clear to at least me that uio_pruss is supp

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 that

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

You still have to follow Roberts instructions I provided you earlier in this thread. Robert didn’t use overlays because Remoteproc had an issue, so if you want to use uio_pruss, you still have to use the same instructions. This applies to the 4.4-ti kernel. Regards, John > On Jul 15, 2016,

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 uio_pruss.

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 --- You

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

> > But, you mentioned something else, that got me thinking: after backing up > the sd card and writing a new image to the sd-card, it failed first pass > (no booting BBG whatsever I tried). Flashed the image again, and then my > BBG booted. So now I start to suspect my sd card actually. Time for n

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 secon

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

> > 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 second stage uEnv.txt file the uname_r variable had not changed to reflect the upgrad

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

Overlay for Remoteproc doesn’t work so you must follow Roberts instructions to select between rproc or uio: You can swap between rproc and uio for the pruss... while, uio can be loaded as an overlay, rproc was failing, so we need to use the dtb-rebuilder... Step 1: upgrade to r34 and reboot:

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 > l

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

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 about this. So it sounds like right off the bat, all you need to do is load the PRU o

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

> > 2) The "ti" version seems to be dropped starting the 4.5.0 series kernel, > so I guess remoteproc was dropped in the end with newer kernels altogether? > No. That kernel is probably straight out of mainline. Which means it hasn't had either the *bone* or *TI* patchset applied to it yet. On We

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

> > 1) is it possible to install another kernel image, and how is this done > exactly? Unfortunately I managed to get my image on the sd-card unbootable > when installing another kernel (bone-kernel instead of ti-kernel). I guess > that uEnv.txt is not correctly updated when switching kernels. Actu

[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 frequ