Cloud9 IDE Update (c9-core-installer_3.1.3543)

it's a pretty small patch:

https://patchwork.kernel.org/patch/9177249/raw/

Documentation/pwm.txt | 6 ++++--
drivers/pwm/sysfs.c | 15 ++++++++++++---
2 files changed, 16 insertions(+), 5 deletions(-)

I tried pinging the author David Hsu, but his email address is disabled.

Regards,

Right now, or at least last I checked( a few months ago ) the naming in
DT's was as thus:

"ehrpwm0A",
"ehrpwm0B",
"ehrpwm1A",
"ehrpwm1B",
"ehrpwm2A",
"ehrpwm2B";

This wont change will it ? Only in sysfs, right ?

Correct just the sysfs names… of course that’s what every user space application uses…

Regards,

I have updated my system starting with a base image from: https://rcn-ee.com/rootfs/2017-04-07/elinux/ubuntu-16.04.2-console-armhf-2017-04-07.tar.xz
Then updating the kernel: Linux bbb-266a 4.9.30-ti-rt-r37 #1 SMP PREEMPT RT Sun May 28 15:55:20 UTC 2017 armv7l armv7l armv7l GNU/Linux

I am using the udev rule previously suggested: 80-gpio-no-root.rules

/etc/udev/rules.d/80-gpio-noroot.rules

You could see if that is in fact a permissions error by running the python
script as root. If it runs without error, then something in the BBIO
library is not quite ready for prime time yet. My guess is that it would be
a simple pathing issue. e.g. the pathing in the update BBIO library is not
quite up to date.

The Adafruit_BBIO code usage does work when the user is root.

Kindest regards,
Mary

Then it's a matter of permissions. Which means you need to adjust
permission forr the user using those applications. Make udev rules for the
hardware you're using to allow a group to use that hardware, then add that
user to that group. Or just run the application as root.

FYI, startup scripts run in the traditional manner all run as root anyhow.
So perhaps running as root is the optimal fix ?

The goal with the Stretch images is to fix that..

Right now the gpio's can be exported/etc by "debian or any user in
"gpio" group" pwm is close, but i need to break userspace, so waiting
for all the nodejs libraies to get fixed, before i break that..

So, let us "know" which calls don't work in Stretch:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Stretch_testing

Side note, these "rootless" changes are happening in stretch "first"..

Regards,

Thank you for your input. Upon further testing, my application is working using Adafruit_BBIO. I must have forgotten a step when I was doing it manually using python3.