Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

So . . . yeah. For 4.x kernels it's broken. william@beaglebone:~$ ls /sys/class/pwm/ william@beaglebone:~$ nano bspwm_P9_22_13-00A0.dts william@beaglebone:~$ dtc -O dtb -o bspwm_P9_22_13-00A0.dtbo -b 0 -@ bspwm_P9_22_13-00A0.dts Error: bspwm_P9_22_13-00A0.dts:53.2-54.1 syntax error FATAL ERROR:

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Hi Mike, Yeah, that's pretty cool, except it does need an update at minimum when showing sysfs paths for *ocp* targets . Also I'm not entirerly sure it generates correct overlay files for( at minimum ) ehrpwm* and kernels 4.1.x+ On Thu, Jul 28, 2016 at 1:16 PM, Mike

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 07/28/2016 03:20 PM, William Hermans wrote: I think what would be super useful, if a web interface, or maybe even native app that did pinmux for people. Select a few options from dropdowns, click a few checkboxes, and viola ! Have it generate a *dts file for you.

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Charles, The idea I had in my mind is that someone could potentially, more easily. Figure out how to use device tree files. By examining something that is closer to self explanatory, and not a wall of code to hurdle. I think your overlays illustrate very well how device tree files work, but that

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

I think what would be super useful, if a web interface, or maybe even native app that did pinmux for people. Select a few options from dropdowns, click a few checkboxes, and viola ! Have it generate a *dts file for you. I will say, and agree that this platform is not like something like the rPI(

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 7/28/2016 2:52 AM, William Hermans wrote: > Charles, > > Also, I've been meaning to ask you what you'd think of individual pin overlay > files based on universal-IO. I have all of P8 done, or most of( I don't wont > touch the eMMC pins - but HDMI + audio is fair game). > Was considering how

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Charles, Also, I've been meaning to ask you what you'd think of individual pin overlay files based on universal-IO. I have all of P8 done, or most of( I don't wont touch the eMMC pins - but HDMI + audio is fair game). I got bored, when our internet bouncing equipment got struck by lightning

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Thanks Charles. Read this last night, and been meaning to thank you for the information. But kept getting sidetracked . .. gpio-of-helper, I have not been able to find decent documentation on that, but I have not looked recently. Probably somewhere in linux/documentation/ . . . On Wed, Jul 27,

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 7/27/2016 12:33 AM, William Hermans wrote: > Charles, > > Is there a way through modifying your overlay files to put an output pin in a > specific state as the overlay file is loaded ? I noticed one can change input > to > output as needed in fragment@2. But do not see a way to change pin

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Oh, right so just two ways of configure-ring, and using the same pin ? Yeah, no big deal to me, I'd just never use P9_92, and haven't to date. On Tue, Jul 26, 2016 at 10:33 PM, William Hermans wrote: > Charles, > > Is there a way through modifying your overlay files to put an

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Charles, Is there a way through modifying your overlay files to put an output pin in a specific state as the overlay file is loaded ? I noticed one can change input to output as needed in fragment@2. But do not see a way to change pin state. unless if it'll work if i replace "input" with hi, or

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

> > You can replace cape_universal by the libpruio universal overlay. That > doesn't enable drivers/subsystems (= saves power and resources > consumptions), but has the same pinmuxing capability. It's even more safe, > since it seems that cape_universal can damage your CPU by a sequence like > >

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

> > You can replace cape_universal by the libpruio universal overlay. That > doesn't enable drivers/subsystems (= saves power and resources > consumptions), but has the same pinmuxing capability. It's even more safe, > since it seems that cape_universal can damage your CPU by a sequence like > >

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

If we create gpio/pinmux group, I think we could keep from burdening users while moving Cloud9 IDE to the 'debian' user. I believe we also have a sudoers for the 'debian' user, meaning we could probably at that point prevent direct root login unless someone does something to disable the root

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On Fri, Jun 24, 2016 at 8:10 PM Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 6/24/2016 5:52 PM, William Hermans wrote: > > /Note the security 'bar' is not set particularly high, given the/ > > /default BBB images have no root password. :)/ > > > > > > Thats been changed,

[beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Hi William! Am Dienstag, 19. Juli 2016 19:54:02 UTC+2 schrieb William Hermans: > > SO, after talking with Robert and finding that all these kernel modules > that get loaded from cape_universal=enable. I wonder how this impacts other > capes such as the Logic supply RS232 / CAN cape that

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

I guess maybe the thing to do would be to edit the universalio overlay file of choice. So that it did not touch the needed pins / peripherals used by a given cape with eeprom. On Tue, Jul 19, 2016 at 10:54 AM, William Hermans wrote: > SO, after talking with Robert and finding

[beagleboard] Re: cape-universal & 4.1.x = default.. ;)

SO, after talking with Robert and finding that all these kernel modules that get loaded from cape_universal=enable. I wonder how this impacts other capes such as the Logic supply RS232 / CAN cape that automatically loads it's own device tree overlay. Could capes such as this be loaded first,

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 6/24/2016 5:52 PM, William Hermans wrote: > /Note the security 'bar' is not set particularly high, given the/ > /default BBB images have no root password. :)/ > > > Thats been changed, since at least the last couple of images. Ahh...that's probably why you were getting the "askpass"

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

> > *Note the security 'bar' is not set particularly high, given the* > * default BBB images have no root password. :)* > Thats been changed, since at least the last couple of images. On Fri, Jun 24, 2016 at 3:47 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 6/24/2016 5:41

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 6/24/2016 5:41 PM, William Hermans wrote: > One thing to point out though. sudo can be more exact, in that you can > specify > an exact command( including parameters ) that a normal user can use ( with > sudo > of course ), and can make it so those user do not need to provide a passwd - >

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

https://github.com/wphermans/Bonejs/blob/master/permissions.md is the link to the file where I discuss what I personally do for permissions, etc. One thing to point out though. sudo can be more exact, in that you can specify an exact command( including parameters ) that a normal user can use (

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

I pasted my udev rule here last night, but also I have it listed in the permissions.md file of my bonejs github project. I'm going through changing my documentation structure. So hopefully I can cover more, and hopefully cleaner / clearer. You, Robert, or anyone can just grab that udev rule, and

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 6/24/2016 4:42 PM, William Hermans wrote: > Charles, > > So, a minor complaint. None of your overlays configures *ALL* pins not used > by > hdmi( audio and video ) and all other pins not in use by the system ( eMMC, > i2c-0/2, etc ). I had to use a cape I suppose Robert created: Robert is

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Charles, So, a minor complaint. None of your overlays configures *ALL* pins not used by hdmi( audio and video ) and all other pins not in use by the system ( eMMC, i2c-0/2, etc ). I had to use a cape I suppose Robert created: debian@beaglebone:~$ dmesg |grep univ [0.00] Kernel command

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

> > *See the readme:* > > * https://github.com/cdsteinkuehler/beaglebone-universal-io > * > Ok, my bad. How did I miss that ? *That's probably the best option if you need things setup early on,* > * otherwise you can just run a

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 6/24/2016 12:27 PM, William Hermans wrote: > Just as an indication of what I'm looking at. > > debian@beaglebone:~$ ls /lib/firmware/ |grep univ > cape-univ-audio-00A0.dtbo > cape-univ-emmc-00A0.dtbo > cape-univ-hdmi-00A0.dtbo > cape-universal-00A0.dtbo > cape-universaln-00A0.dtbo The above

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 6/24/2016 12:22 PM, William Hermans wrote: > Charles, > > So one thing I do find kind of confusing. Is which universal-io device tree > to > load at boot. Basicaly, my board is currently set stock + hdmi audio, and > video > disabled. > > Could you please give me a rundown on what each

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Just as an indication of what I'm looking at. debian@beaglebone:~$ ls /lib/firmware/ |grep univ cape-univ-audio-00A0.dtbo cape-univ-emmc-00A0.dtbo cape-univ-hdmi-00A0.dtbo cape-universal-00A0.dtbo cape-universaln-00A0.dtbo univ-all-00A0.dtbo univ-bbgw-00A0.dtbo univ-emmc-00A0.dtbo

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Charles, So one thing I do find kind of confusing. Is which universal-io device tree to load at boot. Basicaly, my board is currently set stock + hdmi audio, and video disabled. Could you please give me a rundown on what each dtb is for ? I'll document that information and write up a blog post

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Okay . . . Went through the file and replaced sudo -A for '' ( empty string- or null ). And then had to add to my udev rules file . . . SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c 'chown -R root:gpio /sys/class/gpio; chmod -R 770 /sys/class/gpio; chown -R root:gpio

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Ok so one not so fun issue . . . william@beaglebone:~/dev/bonejs$ config-pin P8.07 low sudo: no askpass program specified, try setting SUDO_ASKPASS Cannot write gpio direction file: /sys/class/gpio/gpio66/direction EXCEPT william@beaglebone:~/dev/bonejs$ ls -al /sys/class/gpio/gpio66/direction

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

> > Wrap away! > > I'm just happy the universal overlay concept has caught-on. I wanted > people to be able to do most simple things without having to craft > custom device-tree overlays. Using a custom overlay is still the most > flexible option, but there's a pretty high barrier to entry. >

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 6/23/2016 5:26 PM, William Hermans wrote: > > So the wrapper is really simple. But what I plan on doing with said wrapper > will > be really neat I think. How does configurering your pin modes from a web page > sound ? ;) That sounds pretty awesome! -- Charles Steinkuehler

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On 6/23/2016 5:22 PM, William Hermans wrote: > Thanks Charles. > > Yes, initially I was thinking that perhaps that file reflected what the > current > values of pins were. But after thinking while waiting for your reply I was > thinking that too. Initial state of the pins at the time the

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

By the way, it's just a wrapper for Nodejs, but otherwise I'm not changing a thing. So far all I really want / need is: "use strict"; var fs = require('fs'); var exec = require('child_process').exec; exports.config = function(pin, value){ var params = pin + ' ' + value; var child =

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Thanks Charles. Yes, initially I was thinking that perhaps that file reflected what the current values of pins were. But after thinking while waiting for your reply I was thinking that too. Initial state of the pins at the time the overlay was loaded. Another question regarding config-pin . . .I

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

The status file is created by the kernel logic, and I believe simply reflects the load-time configuration of the GPIO, which all default to inputs when the overlay loads)...but I haven't crawled through the kernel code to figure out exactly what it's doing to create the status file. I suspect the

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

@Charles So I'm not sure if this is normal or not. Thought I'd bring it to your attention in case it's not. william@beaglebone:~$ sudo chown root:gpio /usr/bin/config-pin william@beaglebone:~$ config-pin P8.07 hi william@beaglebone:~$ cat /sys/devices/platform/ocp/ocp:cape-universal/status . .

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

> > It does, but it depends on the image you start with. Usually it's > found in /opt/source/beaglebone-universal-io/, with a symlink for > config-pin in /usr/local/bin/config-pin: > > >

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

It does, but it depends on the image you start with. Usually it's found in /opt/source/beaglebone-universal-io/, with a symlink for config-pin in /usr/local/bin/config-pin: https://github.com/RobertCNelson/omap-image-builder/blob/master/target/chroot/beagleboard.org-wheezy.sh#L389-L396 On

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

I thought, perhaps incorrectly that config-pin came shipped by default. On Thu, Jun 23, 2016 at 9:22 AM, William Hermans wrote: > My cure . . . > > william@beaglebone:~$ wget > https://raw.githubusercontent.com/cdsteinkuehler/beaglebone-universal-io/master/config-pin >

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

My cure . . . william@beaglebone:~$ wget https://raw.githubusercontent.com/cdsteinkuehler/beaglebone-universal-io/master/config-pin william@beaglebone:~$ sudo chmod +x config-pin [sudo] password for william: william@beaglebone:~$ sudo cp ./config-pin /usr/bin william@beaglebone:~$ config-pin -l

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Still no dice . . . william@beaglebone:~$ dmesg |grep univ [0.00] Kernel command line: console=tty0 console=ttyO0,115200n8 bone_capemgr.enable_partno=cape-universaln root=/dev/mmcblk0p1 rootfstype=ext4 rootwait ipv6.disable=1 [5.541989] bone_capemgr bone_capemgr: enabled_partno PARTNO

[beagleboard] Re: cape-universal & 4.1.x = default.. ;)

@Robert So I decided to give universal-io a go for the first time( finally ), but . . . trying to follow along with Charles' examples on github . . . william@beaglebone:~$ sudo config-pin -l P9.14 sudo: config-pin: command not found At this point, I do not know what is going on. So I check

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

nyt, btw, ping charles on that email thread.. we should have slew rate controls ... Also just my $0.02, I'd like to see the universal overlay loaded when needed (via config-pin?) and not during boot by default. This will continue to let anything else that loads overlays function as they were

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

nyt, btw, ping charles on that email thread.. we should have slew rate controls ... Also just my $0.02, I'd like to see the universal overlay loaded when needed (via config-pin?) and not during boot by default. This will continue to let anything else that loads overlays function as they were

[beagleboard] Re: cape-universal & 4.1.x = default.. ;)

This will break any scripts and libraries that load overlays as needed. I don't see how loading it by default benefits anything :( On Tuesday, July 21, 2015 at 12:26:36 PM UTC-4, RobertCNelson wrote: > > Hey Guys, > > In the v4.1.x-ti tree, we have a couple more hdmi-audio pins but >

[beagleboard] Re: cape-universal & 4.1.x = default.. ;)

Also the only updates I needed for the beaglebone gem was to change a single line to look for the new slots file, everything else worked the same, so I assume not much else is needed for pybbio and bonescript. With this auto-loading however, it breaks loading overlays for these libraries

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On Wed, Oct 14, 2015 at 2:48 AM, wrote: > Also the only updates I needed for the beaglebone gem was to change a single > line to look for the new slots file, everything else worked the same, so I > assume not much else is needed for pybbio and bonescript. With this >

Re: [beagleboard] Re: cape-universal & 4.1.x = default.. ;)

On Wed, Oct 14, 2015 at 8:56 AM, Robert Nelson wrote: > On Wed, Oct 14, 2015 at 2:48 AM, wrote: >> Also the only updates I needed for the beaglebone gem was to change a single >> line to look for the new slots file, everything else worked the same, so