Yeah, from what I hear pretty much all the IO drivers have changed on the BeagleBone Black with the switch to the 3.8 kernel. I have not had a chance to look into it yet, so for the time being PyBBIO is definitely not compatible... but it will be!

from pybbio.

I can not wait for compatibility.

from pybbio.

+1

from pybbio.

There may also be a problem with UART rx and tx. omap_mux is needed in those modules as well.

from pybbio.

This looks like a brilliant piece of work...! Hopefully the compatibility issue is being worked? If so, any ideas of how long to a fix? If not, any ideas of how to backup to a previous version of Angstrom? Regards, Wisar

from pybbio.

PyBBIO will be compatible with the 3.8 kernel soon. I hadn't really had much time to work on it since the BBB came out, but I should hopefully be able to get it working in the next couple (maybe few) weeks.

If you want to go back for now, older Angstrom BealgeBone images are in the archive directory here: http://downloads.angstrom-distribution.org/demo/beaglebone/ .

Sorry for the delay and thanks to everyone who's been reporting details of what's changed with the new kernel!

from pybbio.

Thanks for the quick response. I bought the BB to prototype something that I want to do in Python so will 'def go backwards. Can I trouble you to ask what the latest "good for pyBBIO" version was? It looks like I would need to go back quite a ways from browsing the archive.

On an editorial note...as I researched the BB I was somewhat surprised to see their choice of JavaScript as a primary development language. JavaScript???

Anyway, thanks again and I will look forward to you breaking a little time lose! I wish I were technical enough to help but alas....

Wisar

from pybbio.

I haven't tried it myself, but lazychino has reported a working image here: #20 (comment)

Hey, don't knock JavaScript! :) node.js is based on the V8 engine, which is really fast, and in some ways is a more sensible choice than Python this sort of thing. The reason I chose to write PyBBIO is because I don't think node's event-driven nature is always the right approach for the sort of stuff one might want to do with the BeagleBone, and I'd imagine it could be a bit of a hurdle for beginners. At the risk of starting a flame war, I think Python is one of the best languages for beginners.

from pybbio.

Less knocking JavaScript than not thinking of it as being a natural for the stuff that one might want to do in the physical interface space.  I had actually not known about node.js but as powerful as it may be it seems to target the same space that JavaScript has always targeted...event driven web apps.   In any case I am looking forward to trying your Python interface as I am looking for something that would be easier to support than a development in either C (Arduino) or JavaScript (BBB).

Cheers,
Wisar

From: Alexander Hiam [email protected]
To: alexanderhiam/PyBBIO [email protected]
Cc: Wisar1111 [email protected]
Sent: Saturday, June 1, 2013 8:37 PM
Subject: Re: [PyBBIO] PWM Bindings changed on Beaglebone Black. (#18)

I haven't tried it myself, but lazychino has reported a working image here: #20
Hey, don't knock JavaScript! :) node.js is based on the V8 engine, which is really fast, and in some ways is a more sensible choice than Python this sort of thing. The reason I chose to write PyBBIO is because I don't think node's event-driven nature is always the right approach for the sort of stuff one might want to do with the BeagleBone, and I'd imagine it could be a bit of a hurdle for beginners. At the risk of starting a flame war, I think Python is one of the best languages for beginners.
—
Reply to this email directly or view it on GitHub.

from pybbio.

Has this issue been resolved? I am curious because Adafruit has a tutorial using PYBBIO pwm and im wondering if its bogus. I will hopefully try this tonight so i can let people know if it is working.

http://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black/pwm

Thanks

from pybbio.

I have been working with the Adafruit tutorial you linked to, @Mango-kid, and successfully addressed 4 PWM pins (you can check out my code here https://github.com/AKAMEDIASYSTEM/speedtest ) quite reliably; I'm not sure if other pwm pins are yet available.

One thing I noticed, though, is some weirdness in keeping a PWM pin going (as in, if you have a loop that continually updates a PWM pin via set_duty_cycle()). In my experiences this past week, simply using set_duty_cycle after calling BBIO.PWM.start(pin, duty_cycle, freq) once does not work reliably - after three or four loops, the PWM pin freezes and becomes unresponsive.

However, I have solved this (and have yet to regret it!) by simply calling start(pin, duty_cycle, freq) every time that I would normally just update an already-started pin. Please let me know if you think I'm doing something unwise ;-)

(I'm eagerly hoping for help getting PPM and servo control working on BBB, so any help/advice would be appreciated off-list)

AKA

from pybbio.

It's certainly not bogus, but it is a different library: https://github.com/adafruit/adafruit-beaglebone-io-python (PyBBIO is imported as lowercase 'bbio' ). They wrote that recently to go with their web IDE (I believe), and it has an API similar to RPIO for the Raspberry Pi.

Using the IO pins is pretty much the same on the 3.8 kernel, what's changed is that they removed the user-space pinmux driver, and all of the pinmuxing is done through cape configuration. The way the Adafruit library works, which is certainly viable, is to just use a default pinmux configuration, e.g. the PWM1A pin can't also be used as GPIO1_18, even though it could potentially be muxed that way. This can be taken one step further by creating a virtual cape with the desired pinmux settings, which would then require a reboot after installing.

The reason PyBBIO is not doing the same thing is that, well, I'm stubborn. I really like the idea of pinmuxing from user-space, and I'm still looking for a way to do it. This is looking more and more like a lost cause, however, so I think I will try to get a pinmux-less version up and running soon.

FWIW @AKAMEDIASYSTEM, that's odd, you may want to open an issue on the Adafruit repo.

from pybbio.

Whoa, thanks @alexanderhiam, it is very helpful to hear your account of the differences between yours and adafruit's libraries!
Now I will have to read up on what pinmuxing means... ;-)

from pybbio.

On a slight tangent...the irony is that this change also broke the library that is part of the standard O/S distribution for the BBB and supports analog IO from the Cloud9 IDE.   They have supposedly fixed this but not built a new image yet (though I have been bugging them). 

Cheers,
Will

From: AKA [email protected]
To: alexanderhiam/PyBBIO [email protected]
Cc: Will Kostelecky [email protected]
Sent: Tuesday, June 25, 2013 5:38 PM
Subject: Re: [PyBBIO] PWM Bindings changed on Beaglebone Black. (#18)

Whoa, thanks @alexanderhiam, it is very helpful to hear your account of the differences between yours and adafruit's libraries!
Now I will have to read up on what pinmuxing means... ;-)
—
Reply to this email directly or view it on GitHub.

from pybbio.

Well thanks for the answers guys. I guess i should have spent more time reading the tutorial.

I have had a lot of problems with the Cloud9 IDE and using hardware. The LED example is one case, you can run the program once if you are lucky but usually it does nothing. That being said i have been messing with the software pretty hard so it could be my own doing.

The Adafruit library is great but i hate to use up 4 timers just to create PWM signals. I have done some work on a soft PWM library but its pretty unreliable.

from pybbio.

@AKAMEDIASYSTEM I believe that bug is with the PWM driver (Adafruit_BBIO author here..). There are custom PWM driver and firmware here: https://github.com/SaadAhmad/beaglebone-black-cpp-PWM. They allow you to change the period in real time. The reason you need to call start() is due to that bug, I believe. There is so much in flux with the 3.8 kernel right now that we're kind of taking a patient approach to things, like @alexanderhiam is with PyBBIO.

Regarding userspace pinmuxing...I haven't found a single good way of doing it yet either with 3.8. Bonescript isn't even doing it (but they're looking into it soon, I hear).

Also, to reduce confusion with PyBBIO (an excellent library!), we renamed the Adafruit library to Adafruit_BBIO. We built it due to having so much code using RPi.GPIO, and needing to port it easily.

from pybbio.

@jwcooper I have just installed Adafruit BBIO per your tutorial. GPIO works great in a simple test. however, no luck with the PWM routines. When I enter the PWM start code (from the tutorial)
PWM.start("P9_14", 50)
I get no errors thrown, but no waveform on my 'scope on P9 pin 14.
When I add
PWM.set_frequency("P9_14",100)
I get the error "runtime error: you must start() the PWM channel first."
This doesnt make sense to me, given that I already have issued the PWM.start command
Also, the examples that come with the install all use the line
Import BBIO.xxx
This is out of date, given the new adafruit library Adafruit_BBIO
Any idea what Is wrong? ( at my end probably)
Many thanks.

from pybbio.

@bmillier I've created an issue at the adafruit repository adafruit/adafruit-beaglebone-io-python#6 so as not to confuse this PyBBIO issue. Thanks!

from pybbio.

I am trying BBB with the Adafruit_BBIO 0.0.15 library and Ubuntu 13.04 kernel 3.8.13
result:
RuntimeError: You must start() the PWM channel first

Any way to fix this?

Thanks.

from pybbio.

I am getting the same as above ^

Angle (0 to 180 x to exit):12
Traceback (most recent call last):
File "test.py", line 18, in
PWM.set_duty_cycle(servo_pin, duty)
RuntimeError: You must start() the PWM channel first

I am using Ubuntu 3.8.13-bone20 fresh install with the required packages for the tutorial
here http://learn.adafruit.com/controlling-a-servo-with-a-beaglebone-black/writing-a-program

I am fairly new to this sort of thing so any help/solution would be great !
Thanks.

from pybbio.

@AdrianIRL it looks like jwcooper has figured this out: adafruit/adafruit-beaglebone-io-python#6

from pybbio.

@alexanderhiam Thanks for getting back to me. I have been searching for most of the evening making a few attempts to get this to work. I really would appreciate it if anyone knows of a Ubuntu bone-24/> .img that can boot from SD card instead of needing to flash the emmc. For various reasons I can't stand Angstrom !

from pybbio.

👍

from pybbio.

Make sure that your kernel has full PWM support! In fact, some Ubuntu kernels do not have it enabled. To check if this is your case, try this (after a fresh reboot!):

echo am33xx_pwm > /sys/devices/bone_capemgr.*/slots
echo bone_pwm_P8_13 > /sys/devices/bone_capemgr.*/slots
ls /sys/devices/ocp.*/pwm_test_P8_13/

(those actions are done by the Adafruit library usually)
If in the list you are missing period and duty, then you have a Kernel that was compiled without the flag CONFIG_EHRPWM_TEST.
To fix that, you will have to recompile the Kernel by following the steps on elinux and uncomment the CONFIG_EHRPWM_TEST defconfig.
Hope it helps!

from pybbio.

PyBBIO has been working on 3.8 kernels for a while now, closing issue.

from pybbio.

Hi Alexander:
I first contacted you about the PWM problem I had with PYBBIO months
back when I was using Angstrom (which is why I was on the mailing list
for this email distro.). I gave up on Angstrom, and have since switched
to Debian. When I got your email, I decided to try again to get the PWM
to work.
I followed the installation proc. on your wiki exactly. The "which
dtc" command responded usr/local/bin/dtc , so I assume DTC was OK.
My kernel version is 3.8.13
I am running as root.

The blink.py program works OK.

The fade.py program won't run: error thrown is Name error: name 'run' is
not defined

If I manually enter the following PWM code in python 2.7 , I get the
error shown.

Python 2.7.3 (default, Mar 14 2014, 17:55:54)
[GCC 4.6.3] on linux2
Type "copyright", "credits" or "license()" for more information.

from bbio import *
PyBBIO initialized
analogWrite(PWM1A,100)

Traceback (most recent call last):
File "<pyshell#1>", line 1, in
analogWrite(PWM1A,100)
File
"/usr/local/lib/python2.7/dist-packages/bbio/platform/beaglebone/bone_3_8/pwm.py",
line 28, in analogWrite
pwmEnable(pwm_pin)
File
"/usr/local/lib/python2.7/dist-packages/bbio/platform/beaglebone/bone_3_8/pwm.py",
line 98, in pwmEnable
if (sysfs.kernelFilenameIO('%s/%s' % (helper_path, PWM_RUN)) == '1\n'):
File
"/usr/local/lib/python2.7/dist-packages/bbio/platform/beaglebone/sysfs.py",
line 21, in kernelFilenameIO
fn = glob.glob(fn)[0]
IndexError: list index out of range

I also tried analog_test.py, with the following error thrown:

root@debian-armhf:/usr/local/lib/PyBBIO/examples# python analog_test.py
Traceback (most recent call last):
File "analog_test.py", line 47, in
run(setup, loop)
File "/usr/local/lib/python2.7/dist-packages/bbio/bbio.py", line 63,
in run
loop()
File "analog_test.py", line 37, in loop
val1 = analogRead(pot1)
File
"/usr/local/lib/python2.7/dist-packages/bbio/platform/beaglebone/bone_3_8/adc.py",
line 46, in analogRead
raise Exception('Could load overlay for adc_pin: %s' % adc_pin)
Exception: *Could load overlay for adc_pin:
['/sys/devices/ocp.2/PyBBIO-AIN0./AIN0', 'PyBBIO-AIN0', 'P9.39']

 While I can get the Adafruit BBIO python library to work on some 

functions, their PWM function doesn't show any output on my scope on
P9_14, although it does not throw any errors either.
From the sounds of your email, the issue is closed, so I guess I am
the only one having a problem.
Thanks

Brian Millier
Computer Interface Consultants
31 Three Brooks Drive
Hubley N.S. B3Z 1A3

CELL: (902)403-6329
RES: (902) 876-8645
[email protected]

On 04/08/2014 6:39 PM, Alexander Hiam wrote:

PyBBIO has been working on 3.8 kernels for a while now, closing issue.

—
Reply to this email directly or view it on GitHub
#18 (comment).

from pybbio.

Can you post the output of # ls /lib/firmware/PyBBIO*?

Then do a full wipe of PyBBIO with:

# rm -r /lib/firmware/PyBBIO-*
# rm -r /usr/local/lib/PyBBIO/
# pip uninstall PyBBIO

and just to be sure:

# rm -r /usr/local/lib/python2.7/dist-packages/PyBBIO*
# rm -r /usr/local/lib/python2.7/dist-packages/bbio

Then install through pip with # pip install PyBBIO and post the entire output.

from pybbio.

Brian Millier
Computer Interface Consultants
31 Three Brooks Drive
Hubley N.S. B3Z 1A3

CELL: (902)403-6329
RES: (902) 876-8645
[email protected]

On 05/08/2014 5:17 PM, Alexander Hiam wrote:

Can you post the output of |# ls /lib/firmware/PyBBIO*|?

OK- attached file alexlisting1

Then do a full wipe of PyBBIO with:

|# rm -r /lib/firmware/PyBBIO-*

rm -r /usr/local/lib/PyBBIO/

pip uninstall PyBBIO

|
|

and just to be sure:

|# rm -r /usr/local/lib/python2.7/dist-packages/PyBBIO*

rm -r /usr/local/lib/python2.7/dist-packages/bbio

|
|
|

entire output.

all output, including the rm commands and uninstall/install in file
alexlisting2

A quick test gives identical results as before.- i.e. same errors as
I quoted in 1st email.
Thanks

—
Reply to this email directly or view it on GitHub
#18 (comment).

root@debian-armhf:/lib/firmware# rm -r /lib/firmware/PyBBIO-*
root@debian-armhf:/lib/firmware# rm -r /usr/local/lib/PyBBIO/
root@debian-armhf:/lib/firmware# pip uninstall PyBBIO
Uninstalling PyBBIO:
Proceed (y/n)? y
Successfully uninstalled PyBBIO
root@debian-armhf:/lib/firmware# rm -r /usr/local/lib/python2.7/dist-packages/PyBBIO*
root@debian-armhf:/lib/firmware# rm -r /usr/local/lib/python2.7/dist-packages/bbio
root@debian-armhf:/lib/firmware# pip install PyBBIO
Downloading/unpacking PyBBIO
Downloading PyBBIO-0.9.tar.gz (94Kb): 94Kb downloaded
Running setup.py egg_info for package PyBBIO

Requirement already satisfied (use --upgrade to upgrade): pyserial in /usr/local/lib/python2.7/dist-packages (from PyBBIO)
Requirement already satisfied (use --upgrade to upgrade): smbus in /usr/lib/python2.7/dist-packages (from PyBBIO)
Installing collected packages: PyBBIO
Running setup.py install for PyBBIO
PyBBIO device tree overlay directory not found, creating...
Generating and compiling GPIO overlays... Done!
Generating and compiling ADC overlays... Done!
Installing PyBBIO...
building 'bbio.platform.util._sysfs' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c bbio/platform/util/_sysfs.c -o build/temp.linux-armv7l-2.7/bbio/platform/util/_sysfs.o
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro build/temp.linux-armv7l-2.7/bbio/platform/util/_sysfs.o -o build/lib.linux-armv7l-2.7/bbio/platform/util/_sysfs.so
building 'bbio.platform.util._spi' extension
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c bbio/platform/util/spimodule.c -o build/temp.linux-armv7l-2.7/bbio/platform/util/spimodule.o
gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro build/temp.linux-armv7l-2.7/bbio/platform/util/spimodule.o -o build/lib.linux-armv7l-2.7/bbio/platform/util/_spi.so

install finished with 0 warnings
PyBBIO is now installed on your BeagleBone >=3.8, enjoy!

Successfully installed PyBBIO
Cleaning up...
root@debian-armhf:/lib/firmware#
root@debian-armhf:/lib/firmware# ls -l /lib/firmware/PyBBIO*
-rw-r--r-- 1 root root 737 Aug 5 14:35 /lib/firmware/PyBBIO-ADC-00A0.dtbo
-rw-r--r-- 1 root root 672 Aug 5 14:35 /lib/firmware/PyBBIO-AIN0-00A0.dtbo
-rw-r--r-- 1 root root 672 Aug 5 14:35 /lib/firmware/PyBBIO-AIN1-00A0.dtbo
-rw-r--r-- 1 root root 672 Aug 5 14:35 /lib/firmware/PyBBIO-AIN2-00A0.dtbo
-rw-r--r-- 1 root root 672 Aug 5 14:35 /lib/firmware/PyBBIO-AIN3-00A0.dtbo
-rw-r--r-- 1 root root 672 Aug 5 14:35 /lib/firmware/PyBBIO-AIN4-00A0.dtbo
-rw-r--r-- 1 root root 672 Aug 5 14:35 /lib/firmware/PyBBIO-AIN5-00A0.dtbo
-rw-r--r-- 1 root root 672 Aug 5 14:35 /lib/firmware/PyBBIO-AIN6-00A0.dtbo
-rw-r--r-- 1 root root 672 Aug 5 14:35 /lib/firmware/PyBBIO-AIN7-00A0.dtbo
-rw-r--r-- 1 root root 351 Aug 5 14:35 /lib/firmware/PyBBIO-ecap0-00A0.dtbo
-rw-r--r-- 1 root root 351 Aug 5 14:35 /lib/firmware/PyBBIO-ecap1-00A0.dtbo
-rw-r--r-- 1 root root 353 Aug 5 14:35 /lib/firmware/PyBBIO-ehrpwm1-00A0.dtbo
-rw-r--r-- 1 root root 353 Aug 5 14:35 /lib/firmware/PyBBIO-ehrpwm2-00A0.dtbo
-rw-r--r-- 1 root root 353 Aug 5 14:35 /lib/firmware/PyBBIO-epwmss0-00A0.dtbo
-rw-r--r-- 1 root root 353 Aug 5 14:35 /lib/firmware/PyBBIO-epwmss1-00A0.dtbo
-rw-r--r-- 1 root root 353 Aug 5 14:35 /lib/firmware/PyBBIO-epwmss2-00A0.dtbo
-rw-r--r-- 1 root root 994 Aug 5 14:35 /lib/firmware/PyBBIO-eqep0-00A0.dtbo
-rw-r--r-- 1 root root 994 Aug 5 14:35 /lib/firmware/PyBBIO-eqep1-00A0.dtbo
-rw-r--r-- 1 root root 994 Aug 5 14:35 /lib/firmware/PyBBIO-eqep2-00A0.dtbo
-rw-r--r-- 1 root root 994 Aug 5 14:35 /lib/firmware/PyBBIO-eqep2b-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_10-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_11-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_12-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_13-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_14-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_15-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_20-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_2-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_22-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_23-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_26-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_27-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_30-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_3-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_31-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_4-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_5-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_7-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_8-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio0_9-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_0-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_1-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_12-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_13-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_14-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_15-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_16-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_17-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_18-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_19-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_2-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_28-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_29-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_30-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_3-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_31-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_4-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_5-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_6-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio1_7-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_10-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_1-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_11-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_12-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_13-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_14-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_15-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_16-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_17-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_2-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_22-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_23-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_24-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_25-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_3-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_4-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_5-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_6-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_7-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_8-00A0.dtbo
-rw-r--r-- 1 root root 2402 Aug 5 14:35 /lib/firmware/PyBBIO-gpio2_9-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio3_14-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio3_15-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio3_16-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio3_17-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio3_19-00A0.dtbo
-rw-r--r-- 1 root root 2424 Aug 5 14:35 /lib/firmware/PyBBIO-gpio3_21-00A0.dtbo
-rw-r--r-- 1 root root 2316 Aug 5 14:35 /lib/firmware/PyBBIO-usr0-00A0.dtbo
-rw-r--r-- 1 root root 2316 Aug 5 14:35 /lib/firmware/PyBBIO-usr1-00A0.dtbo
-rw-r--r-- 1 root root 2316 Aug 5 14:35 /lib/firmware/PyBBIO-usr2-00A0.dtbo
-rw-r--r-- 1 root root 2316 Aug 5 14:35 /lib/firmware/PyBBIO-usr3-00A0.dtbo

/lib/firmware/PyBBIO-src:
total 364
-rw-r--r-- 1 root root 856 Aug 5 14:35 PyBBIO-ADC-00A0.dts
-rw-r--r-- 1 root root 578 Aug 5 14:35 PyBBIO-AIN0-00A0.dts
-rw-r--r-- 1 root root 578 Aug 5 14:35 PyBBIO-AIN1-00A0.dts
-rw-r--r-- 1 root root 578 Aug 5 14:35 PyBBIO-AIN2-00A0.dts
-rw-r--r-- 1 root root 578 Aug 5 14:35 PyBBIO-AIN3-00A0.dts
-rw-r--r-- 1 root root 578 Aug 5 14:35 PyBBIO-AIN4-00A0.dts
-rw-r--r-- 1 root root 578 Aug 5 14:35 PyBBIO-AIN5-00A0.dts
-rw-r--r-- 1 root root 578 Aug 5 14:35 PyBBIO-AIN6-00A0.dts
-rw-r--r-- 1 root root 577 Aug 5 14:35 PyBBIO-AIN7-00A0.dts
-rw-r--r-- 1 root root 425 Aug 5 14:35 PyBBIO-ecap0-00A0.dts
-rw-r--r-- 1 root root 425 Aug 5 14:35 PyBBIO-ecap1-00A0.dts
-rw-r--r-- 1 root root 444 Aug 5 14:35 PyBBIO-ehrpwm1-00A0.dts
-rw-r--r-- 1 root root 444 Aug 5 14:35 PyBBIO-ehrpwm2-00A0.dts
-rw-r--r-- 1 root root 422 Aug 5 14:35 PyBBIO-epwmss0-00A0.dts
-rw-r--r-- 1 root root 422 Aug 5 14:35 PyBBIO-epwmss1-00A0.dts
-rw-r--r-- 1 root root 422 Aug 5 14:35 PyBBIO-epwmss2-00A0.dts
-rw-r--r-- 1 root root 2039 Aug 5 14:35 PyBBIO-eqep0-00A0.dts
-rw-r--r-- 1 root root 1922 Aug 5 14:35 PyBBIO-eqep1-00A0.dts
-rw-r--r-- 1 root root 1945 Aug 5 14:35 PyBBIO-eqep2-00A0.dts
-rw-r--r-- 1 root root 1978 Aug 5 14:35 PyBBIO-eqep2b-00A0.dts
-rw-r--r-- 1 root root 2453 Aug 5 14:35 PyBBIO-gpio0_10-00A0.dts
-rw-r--r-- 1 root root 2453 Aug 5 14:35 PyBBIO-gpio0_11-00A0.dts
-rw-r--r-- 1 root root 2453 Aug 5 14:35 PyBBIO-gpio0_12-00A0.dts
-rw-r--r-- 1 root root 2453 Aug 5 14:35 PyBBIO-gpio0_13-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio0_14-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio0_15-00A0.dts
-rw-r--r-- 1 root root 2489 Aug 5 14:35 PyBBIO-gpio0_20-00A0.dts
-rw-r--r-- 1 root root 2420 Aug 5 14:35 PyBBIO-gpio0_2-00A0.dts
-rw-r--r-- 1 root root 2435 Aug 5 14:35 PyBBIO-gpio0_22-00A0.dts
-rw-r--r-- 1 root root 2435 Aug 5 14:35 PyBBIO-gpio0_23-00A0.dts
-rw-r--r-- 1 root root 2441 Aug 5 14:35 PyBBIO-gpio0_26-00A0.dts
-rw-r--r-- 1 root root 2441 Aug 5 14:35 PyBBIO-gpio0_27-00A0.dts
-rw-r--r-- 1 root root 2453 Aug 5 14:35 PyBBIO-gpio0_30-00A0.dts
-rw-r--r-- 1 root root 2408 Aug 5 14:35 PyBBIO-gpio0_3-00A0.dts
-rw-r--r-- 1 root root 2441 Aug 5 14:35 PyBBIO-gpio0_31-00A0.dts
-rw-r--r-- 1 root root 2408 Aug 5 14:35 PyBBIO-gpio0_4-00A0.dts
-rw-r--r-- 1 root root 2414 Aug 5 14:35 PyBBIO-gpio0_5-00A0.dts
-rw-r--r-- 1 root root 2468 Aug 5 14:35 PyBBIO-gpio0_7-00A0.dts
-rw-r--r-- 1 root root 2426 Aug 5 14:35 PyBBIO-gpio0_8-00A0.dts
-rw-r--r-- 1 root root 2426 Aug 5 14:35 PyBBIO-gpio0_9-00A0.dts
-rw-r--r-- 1 root root 2402 Aug 5 14:35 PyBBIO-gpio1_0-00A0.dts
-rw-r--r-- 1 root root 2402 Aug 5 14:35 PyBBIO-gpio1_1-00A0.dts
-rw-r--r-- 1 root root 2441 Aug 5 14:35 PyBBIO-gpio1_12-00A0.dts
-rw-r--r-- 1 root root 2441 Aug 5 14:35 PyBBIO-gpio1_13-00A0.dts
-rw-r--r-- 1 root root 2441 Aug 5 14:35 PyBBIO-gpio1_14-00A0.dts
-rw-r--r-- 1 root root 2441 Aug 5 14:35 PyBBIO-gpio1_15-00A0.dts
-rw-r--r-- 1 root root 2429 Aug 5 14:35 PyBBIO-gpio1_16-00A0.dts
-rw-r--r-- 1 root root 2429 Aug 5 14:35 PyBBIO-gpio1_17-00A0.dts
-rw-r--r-- 1 root root 2429 Aug 5 14:35 PyBBIO-gpio1_18-00A0.dts
-rw-r--r-- 1 root root 2429 Aug 5 14:35 PyBBIO-gpio1_19-00A0.dts
-rw-r--r-- 1 root root 2402 Aug 5 14:35 PyBBIO-gpio1_2-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio1_28-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio1_29-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio1_30-00A0.dts
-rw-r--r-- 1 root root 2408 Aug 5 14:35 PyBBIO-gpio1_3-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio1_31-00A0.dts
-rw-r--r-- 1 root root 2408 Aug 5 14:35 PyBBIO-gpio1_4-00A0.dts
-rw-r--r-- 1 root root 2408 Aug 5 14:35 PyBBIO-gpio1_5-00A0.dts
-rw-r--r-- 1 root root 2408 Aug 5 14:35 PyBBIO-gpio1_6-00A0.dts
-rw-r--r-- 1 root root 2408 Aug 5 14:35 PyBBIO-gpio1_7-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio2_10-00A0.dts
-rw-r--r-- 1 root root 2414 Aug 5 14:35 PyBBIO-gpio2_1-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio2_11-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio2_12-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio2_13-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio2_14-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio2_15-00A0.dts
-rw-r--r-- 1 root root 2453 Aug 5 14:35 PyBBIO-gpio2_16-00A0.dts
-rw-r--r-- 1 root root 2453 Aug 5 14:35 PyBBIO-gpio2_17-00A0.dts
-rw-r--r-- 1 root root 2444 Aug 5 14:35 PyBBIO-gpio2_2-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio2_22-00A0.dts
-rw-r--r-- 1 root root 2447 Aug 5 14:35 PyBBIO-gpio2_23-00A0.dts
-rw-r--r-- 1 root root 2441 Aug 5 14:35 PyBBIO-gpio2_24-00A0.dts
-rw-r--r-- 1 root root 2477 Aug 5 14:35 PyBBIO-gpio2_25-00A0.dts
-rw-r--r-- 1 root root 2438 Aug 5 14:35 PyBBIO-gpio2_3-00A0.dts
-rw-r--r-- 1 root root 2414 Aug 5 14:35 PyBBIO-gpio2_4-00A0.dts
-rw-r--r-- 1 root root 2444 Aug 5 14:35 PyBBIO-gpio2_5-00A0.dts
-rw-r--r-- 1 root root 2420 Aug 5 14:35 PyBBIO-gpio2_6-00A0.dts
-rw-r--r-- 1 root root 2420 Aug 5 14:35 PyBBIO-gpio2_7-00A0.dts
-rw-r--r-- 1 root root 2420 Aug 5 14:35 PyBBIO-gpio2_8-00A0.dts
-rw-r--r-- 1 root root 2420 Aug 5 14:35 PyBBIO-gpio2_9-00A0.dts
-rw-r--r-- 1 root root 2465 Aug 5 14:35 PyBBIO-gpio3_14-00A0.dts
-rw-r--r-- 1 root root 2453 Aug 5 14:35 PyBBIO-gpio3_15-00A0.dts
-rw-r--r-- 1 root root 2459 Aug 5 14:35 PyBBIO-gpio3_16-00A0.dts
-rw-r--r-- 1 root root 2471 Aug 5 14:35 PyBBIO-gpio3_17-00A0.dts
-rw-r--r-- 1 root root 2453 Aug 5 14:35 PyBBIO-gpio3_19-00A0.dts
-rw-r--r-- 1 root root 2471 Aug 5 14:35 PyBBIO-gpio3_21-00A0.dts
-rw-r--r-- 1 root root 2321 Aug 5 14:35 PyBBIO-usr0-00A0.dts
-rw-r--r-- 1 root root 2321 Aug 5 14:35 PyBBIO-usr1-00A0.dts
-rw-r--r-- 1 root root 2321 Aug 5 14:35 PyBBIO-usr2-00A0.dts
-rw-r--r-- 1 root root 2321 Aug 5 14:35 PyBBIO-usr3-00A0.dts
root@debian-armhf:/lib/firmware#

from pybbio.

OK, everything is getting installed correctly, so capemgr must be unable to load the overlays.

Do you have any other overlays loaded? What's the output of # cat /sys/devices/bone_capemgr.*/slots?

Also post (or pastebin) the output of # dmesg after trying to run analog_test.py.

from pybbio.

On 05/08/2014 7:25 PM, Alexander Hiam wrote:

OK, everything is getting installed correctly, so capemgr must be
unable to load the overlays.

Do you have any other overlays loaded?

No- I have no capes per se. (just a breakout cape, but it is entirely
passive- no EEPROM)
I do have a 7" LCD display for it, which I've used in the past, but it
was not hooked up for this test . i.e. I was using HDMI output.

What's the output of |# cat /sys/devices/bone_capemgr.*/slots|?

Also post (or pastebin) the output of |# dmesg| after trying to run
|analog_test.py|.

Both are in the attached file- the first few lines are the cat command,
the rest is the dmesg command.
When I set up Debian on the BB, I used the root login/pwd so I am
running as root. When I tried to use the Adafruit I2C routines as a
normal user-not root, they don't work as root access is needed for SMBUS
routines.Not sure this means anything in this case.

Thanks for your time/attention.

—
Reply to this email directly or view it on GitHub
#18 (comment).

root@debian-armhf:~# cat /sys/devices/bone_capemgr.*/slots
0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI

root@debian-armhf:~# cd /usr/local/lib/PyBBIO/examples
root@debian-armhf:/usr/local/lib/PyBBIO/examples# python analog_test.py
Traceback (most recent call last):
File "analog_test.py", line 47, in
run(setup, loop)
File "/usr/local/lib/python2.7/dist-packages/bbio/bbio.py", line 63, in run
loop()
File "analog_test.py", line 37, in loop
val1 = analogRead(pot1)
File "/usr/local/lib/python2.7/dist-packages/bbio/platform/beaglebone/bone_3_8/adc.py", line 46, in analogRead
raise Exception('Could load overlay for adc_pin: %s' % adc_pin)
Exception: *Could load overlay for adc_pin: ['/sys/devices/ocp.2/PyBBIO-AIN0./AIN0', 'PyBBIO-AIN0', 'P9.39']
root@debian-armhf:/usr/local/lib/PyBBIO/examples# dmesg
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.13-bone20 (root@imx6q-sabrelite-1gb) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Wed May 29 03:11:01 UTC 2013
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 130816
[ 0.000000] free_area_init_node: node 0, pgdat c0977940, node_mem_map c09f1000
[ 0.000000] Normal zone: 1024 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 129792 pages, LIFO batch:31
[ 0.000000] AM335X ES1.0 (neon )
[ 0.000000] PERCPU: Embedded 9 pages/cpu @c0e00000 s14080 r8192 d14592 u36864
[ 0.000000] pcpu-alloc: s14080 r8192 d14592 u36864 alloc=9_4096
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129792
[ 0.000000] Kernel command line: console=ttyO0,115200n8 fixrtc root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] allocated 1048576 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Memory: 511MB = 511MB total
[ 0.000000] Memory: 507432k/507432k available, 16856k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc08b01a8 (8865 kB)
[ 0.000000] .init : 0xc08b1000 - 0xc08f9700 ( 290 kB)
[ 0.000000] .data : 0xc08fa000 - 0xc097a770 ( 514 kB)
[ 0.000000] .bss : 0xc097a770 - 0xc09f07fc ( 473 kB)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[ 0.000000] Total of 128 interrupts on 1 active controller
[ 0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz
[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[ 0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000393] Calibrating delay loop... 363.67 BogoMIPS (lpj=354304)
[ 0.017385] pid_max: default: 32768 minimum: 301
[ 0.017631] Security Framework initialized
[ 0.017732] Mount-cache hash table entries: 512
[ 0.027178] Initializing cgroup subsys cpuacct
[ 0.027216] Initializing cgroup subsys memory
[ 0.027284] Initializing cgroup subsys blkio
[ 0.027432] CPU: Testing write buffer coherency: ok
[ 0.028021] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.028098] Setting up static identity map for 0x80605b00 - 0x80605b58
[ 0.029769] Brought up 1 CPUs
[ 0.029794] SMP: Total of 1 processors activated (363.67 BogoMIPS).
[ 0.031123] devtmpfs: initialized
[ 0.095102] pinctrl core: initialized pinctrl subsystem
[ 0.095343] rstctl core: initialized rstctl subsystem
[ 0.095920] regulator-dummy: no parameters
[ 0.096470] NET: Registered protocol family 16
[ 0.097344] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.107345] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 0.108115] platform 49000000.edma: alias fck already exists
[ 0.108146] platform 49000000.edma: alias fck already exists
[ 0.108170] platform 49000000.edma: alias fck already exists
[ 0.109379] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[ 0.109554] OMAP GPIO hardware version 0.1
[ 0.110981] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[ 0.112337] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[ 0.113840] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[ 0.114390] of_get_named_gpio_flags exited with status 52
[ 0.114420] gpio-rctrl rstctl.3: loaded OK
[ 0.119745] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.121907] cpsw.0: No hwaddr in dt. Using c8:a0:30:ab:84:fb from efuse
[ 0.121940] cpsw.1: No hwaddr in dt. Using c8:a0:30:ab:84:fd from efuse
[ 0.135562] bio: create slab at 0
[ 0.147156] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[ 0.147389] of_get_named_gpio_flags: can't parse gpios property
[ 0.147620] vmmcsd_fixed: 3300 mV
[ 0.150517] SCSI subsystem initialized
[ 0.150922] usbcore: registered new interface driver usbfs
[ 0.151044] usbcore: registered new interface driver hub
[ 0.151363] usbcore: registered new device driver usb
[ 0.153483] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[ 0.155121] input: tps65217_pwr_but as /devices/ocp.2/44e0b000.i2c/i2c-0/0-0024/input/input0
[ 0.157439] DCDC1: at 1500 mV
[ 0.158711] vdd_mpu: 925 <--> 1325 mV at 1100 mV
[ 0.159834] vdd_core: 925 <--> 1150 mV at 1100 mV
[ 0.161040] LDO1: at 1800 mV
[ 0.162172] LDO2: at 3300 mV
[ 0.164160] LDO3: 1800 mV
[ 0.165287] LDO4: at 3300 mV
[ 0.166322] tps65217 0-0024: TPS65217 ID 0xe version 1.2
[ 0.167105] omap_i2c 44e0b000.i2c: unable to select pin group
[ 0.167953] omap_i2c 4819c000.i2c: bus 1 rev0.11 at 100 kHz
[ 0.170539] omap_i2c 4819c000.i2c: unable to select pin group
[ 0.170769] media: Linux media interface: v0.10
[ 0.170883] Linux video capture interface: v2.00
[ 0.171542] Advanced Linux Sound Architecture Driver Initialized.
[ 0.172720] NetLabel: Initializing
[ 0.172742] NetLabel: domain hash size = 128
[ 0.172753] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.172868] NetLabel: unlabeled traffic allowed by default
[ 0.173191] Switching to clocksource gp_timer
[ 0.227527] NET: Registered protocol family 2
[ 0.228725] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.228868] TCP bind hash table entries: 4096 (order: 4, 81920 bytes)
[ 0.229013] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.229113] TCP: reno registered
[ 0.229139] UDP hash table entries: 256 (order: 1, 12288 bytes)
[ 0.229180] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[ 0.229621] NET: Registered protocol family 1
[ 0.230346] RPC: Registered named UNIX socket transport module.
[ 0.230370] RPC: Registered udp transport module.
[ 0.230382] RPC: Registered tcp transport module.
[ 0.230395] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.231474] CPU PMU: probing PMU on CPU 0
[ 0.231509] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[ 0.232169] omap2_mbox_probe: platform not supported
[ 0.491592] VFS: Disk quotas dquot_6.5.2
[ 0.491959] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.493259] NFS: Registering the id_resolver key type
[ 0.493393] Key type id_resolver registered
[ 0.493411] Key type id_legacy registered
[ 0.493482] fuse init (API version 7.20)
[ 0.494490] Btrfs loaded
[ 0.494661] msgmni has been set to 991
[ 0.497745] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 0.497772] io scheduler noop registered
[ 0.497786] io scheduler deadline registered
[ 0.497838] io scheduler cfq registered (default)
[ 0.499424] tps65217-bl tps65217-bl: no platform data provided
[ 0.499609] tps65217-bl: probe of tps65217-bl failed with error -22
[ 0.500485] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.503110] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[ 0.503544] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[ 1.214439] console [ttyO0] enabled
[ 1.219198] [drm] Initialized drm 1.1.0 20060810
[ 1.237594] brd: module loaded
[ 1.247787] loop: module loaded
[ 1.251236] at24 0-0050: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.258525] at24 1-0054: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.265802] at24 1-0055: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.273083] at24 1-0056: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.280370] at24 1-0057: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[ 1.294435] bone-capemgr bone_capemgr.9: Baseboard: 'A335BNLT,0A5A,1713BBBK2128'
[ 1.302250] bone-capemgr bone_capemgr.9: compatible-baseboard=ti,beaglebone-black
[ 1.341289] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 1.378396] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 1.415508] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 1.452614] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 1.458885] bone-capemgr bone_capemgr.9: slot #4: specific override
[ 1.465501] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 4
[ 1.473552] bone-capemgr bone_capemgr.9: slot #4: 'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
[ 1.483708] bone-capemgr bone_capemgr.9: slot #5: specific override
[ 1.490310] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 5
[ 1.498363] bone-capemgr bone_capemgr.9: slot #5: 'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
[ 1.508823] bone-capemgr bone_capemgr.9: loader: before slot-4 BB-BONE-EMMC-2G:00A0 (prio 1)
[ 1.517713] bone-capemgr bone_capemgr.9: loader: check slot-4 BB-BONE-EMMC-2G:00A0 (prio 1)
[ 1.526516] bone-capemgr bone_capemgr.9: initialized OK.
[ 1.532128] bone-capemgr bone_capemgr.9: loader: before slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 1.540896] bone-capemgr bone_capemgr.9: loader: check slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 1.551529] OneNAND driver initializing
[ 1.556963] usbcore: registered new interface driver cdc_ether
[ 1.563170] bone-capemgr bone_capemgr.9: loader: after slot-4 BB-BONE-EMMC-2G:00A0 (prio 1)
[ 1.572039] usbcore: registered new interface driver rndis_host
[ 1.578349] bone-capemgr bone_capemgr.9: loader: after slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 1.587167] usbcore: registered new interface driver cdc_ncm
[ 1.593170] bone-capemgr bone_capemgr.9: slot #4: Requesting firmware 'cape-bone-2g-emmc1.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0'
[ 1.607532] Initializing USB Mass Storage driver...
[ 1.612869] usbcore: registered new interface driver usb-storage
[ 1.619196] USB Mass Storage support registered.
[ 1.624098] bone-capemgr bone_capemgr.9: slot #4: dtbo 'cape-bone-2g-emmc1.dtbo' loaded; converting to live tree
[ 1.634843] bone-capemgr bone_capemgr.9: slot #5: Requesting firmware 'cape-boneblack-hdmi-00A0.dtbo' for board-name 'Bone-Black-HDMI', version '00A0'
[ 1.649138] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[ 1.655806] bone-capemgr bone_capemgr.9: slot #4: #2 overlays
[ 1.662280] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[ 1.667535] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[ 1.676595] bone-capemgr bone_capemgr.9: slot #4: Applied #2 overlays.
[ 1.683479] bone-capemgr bone_capemgr.9: loader: done slot-4 BB-BONE-EMMC-2G:00A0 (prio 1)
[ 1.692196] bone-capemgr bone_capemgr.9: slot #5: dtbo 'cape-boneblack-hdmi-00A0.dtbo' loaded; converting to live tree
[ 1.703486] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[ 1.703507] musb-hdrc: MHDRC RTL version 2.0
[ 1.703521] musb-hdrc: setup fifo_mode 4
[ 1.703548] musb-hdrc: 28/31 max ep, 16384/16384 memory
[ 1.703691] musb-hdrc musb-hdrc.0.auto: *_* mode=3
[ 1.708758] musb-hdrc musb-hdrc.0.auto: *** power=250
[ 1.715031] bone-capemgr bone_capemgr.9: slot #5: #4 overlays
[ 1.723341] platform 4830e000.fb: alias fck already exists
[ 1.730118] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[ 1.735414] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[ 1.745949] bone-capemgr bone_capemgr.9: slot #5: Applied #4 overlays.
[ 1.752853] bone-capemgr bone_capemgr.9: loader: done slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 1.761490] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[ 1.761511] musb-hdrc: MHDRC RTL version 2.0
[ 1.761525] musb-hdrc: setup fifo_mode 4
[ 1.761547] musb-hdrc: 28/31 max ep, 16384/16384 memory
[ 1.761691] musb-hdrc musb-hdrc.1.auto: *** mode=1
[ 1.766749] musb-hdrc musb-hdrc.1.auto: *** power=250
[ 1.772073] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[ 1.778580] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[ 1.787005] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[ 1.787126] usb usb1: default language 0x0409
[ 1.787183] usb usb1: udev 1, busnum 1, minor = 0
[ 1.787206] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.794414] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.802014] usb usb1: Product: MUSB HDRC host driver
[ 1.807239] usb usb1: Manufacturer: Linux 3.8.13-bone20 musb-hcd
[ 1.813554] usb usb1: SerialNumber: musb-hdrc.1.auto
[ 1.819569] usb usb1: usb_probe_device
[ 1.819597] usb usb1: configuration #1 chosen from 1 choice
[ 1.819670] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[ 1.819962] hub 1-0:1.0: usb_probe_interface
[ 1.819984] hub 1-0:1.0: usb_probe_interface - got id
[ 1.820016] hub 1-0:1.0: USB hub found
[ 1.824017] hub 1-0:1.0: 1 port detected
[ 1.828162] hub 1-0:1.0: standalone hub
[ 1.828180] hub 1-0:1.0: individual port power switching
[ 1.828197] hub 1-0:1.0: no over-current protection
[ 1.828212] hub 1-0:1.0: Single TT
[ 1.828231] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[ 1.828248] hub 1-0:1.0: power on to power good time: 10ms
[ 1.828292] hub 1-0:1.0: local power source is good
[ 1.828403] hub 1-0:1.0: enabling power on all ports
[ 1.829679] mousedev: PS/2 mouse device common for all mice
[ 1.837917] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[ 1.845750] i2c /dev entries driver
[ 1.850857] Driver for 1-wire Dallas network protocol.
[ 1.857914] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[ 1.865517] cpuidle: using governor ladder
[ 1.869850] cpuidle: using governor menu
[ 1.874375] of_get_named_gpio_flags: can't parse gpios property
[ 1.874393] of_get_named_gpio_flags: can't parse gpios property
[ 1.874408] of_get_named_gpio_flags: can't parse gpios property
[ 1.874489] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[ 1.881736] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[ 1.888171] omap_hsmmc mmc.4: unable to select pin group
[ 1.894086] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[ 1.901293] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[ 1.908657] mmc.4 supply vmmc_aux not found, using dummy regulator
[ 1.915336] omap_hsmmc mmc.4: pins are not configured from the driver
[ 1.929335] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[ 1.929420] hub 1-0:1.0: hub_suspend
[ 1.929462] usb usb1: bus auto-suspend, wakeup 1
[ 1.948878] of_get_named_gpio_flags: can't parse gpios property
[ 1.948901] of_get_named_gpio_flags: can't parse gpios property
[ 1.948915] of_get_named_gpio_flags: can't parse gpios property
[ 1.948966] gpio-rctrl rstctl.3: gpio_rctrl_request eMMC_RSTn
[ 1.955196] omap_hsmmc mmc.5: Got rstctl (gpio:#0 name eMMC_RSTn) label:eMMC_RSTn
[ 1.963115] gpio-rctrl rstctl.3: gpio_rctrl_deassert eMMC_RSTn
[ 1.969611] edma-dma-engine edma-dma-engine.0: allocated channel for 0:3
[ 1.976784] edma-dma-engine edma-dma-engine.0: allocated channel for 0:2
[ 1.984392] mmc.5 supply vmmc_aux not found, using dummy regulator
[ 1.991059] omap_hsmmc mmc.5: pins are not configured from the driver
[ 2.025613] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[ 2.037387] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[ 2.044715] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 2.053731] usb usb1: usb wakeup-resume
[ 2.053782] usb usb1: usb auto-resume
[ 2.053810] hub 1-0:1.0: hub_resume
[ 2.053864] hub 1-0:1.0: port 1: status 0101 change 0001
[ 2.054205] leds-gpio gpio-leds.8: pins are not configured from the driver
[ 2.061467] of_get_named_gpio_flags exited with status 53
[ 2.061489] of_get_named_gpio_flags exited with status 54
[ 2.061509] of_get_named_gpio_flags exited with status 55
[ 2.061528] of_get_named_gpio_flags exited with status 56
[ 2.061653] of_get_named_gpio_flags exited with status 53
[ 2.061918] of_get_named_gpio_flags exited with status 54
[ 2.062185] of_get_named_gpio_flags exited with status 55
[ 2.062363] of_get_named_gpio_flags exited with status 56
[ 2.062749] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.069605] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[ 2.076931] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[ 2.085581] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[ 2.091997] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[ 2.099178] mmc0: host does not support reading read-only switch. assuming write-enable.
[ 2.107838] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[ 2.116056] usbcore: registered new interface driver usbhid
[ 2.122025] usbhid: USB HID core driver
[ 2.126173] mmc0: new high speed SDHC card at address b368
[ 2.135489] of_get_named_gpio_flags exited with status 59
[ 2.136313] mmcblk0: mmc0:b368 SDU8G 7.41 GiB
[ 2.142998] davinci_evm sound.13: nxp-hdmi-hifi <-> 48038000.mcasp mapping ok
[ 2.150890] mmcblk0: p1 p2
[ 2.155969] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
[ 2.156047] hub 1-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[ 2.159470] TCP: cubic registered
[ 2.163185] NET: Registered protocol family 10
[ 2.169202] NET: Registered protocol family 17
[ 2.174358] Key type dns_resolver registered
[ 2.179220] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[ 2.187444] ThumbEE CPU extension supported.
[ 2.192011] Registering SWP/SWPB emulation handler
[ 2.198414] registered taskstats version 1
[ 2.205622] of_get_named_gpio_flags: can't parse gpios property
[ 2.205657] tilcdc 4830e000.fb: No power control GPIO
[ 2.245260] mmc1: BKOPS_EN bit is not set
[ 2.252138] mmc1: new high speed MMC card at address 0001
[ 2.258746] mmcblk1: mmc1:0001 MMC02G 1.78 GiB
[ 2.263629] usb 1-1: new full-speed USB device number 2 using musb-hdrc
[ 2.271423] mmcblk1boot0: mmc1:0001 MMC02G partition 1 1.00 MiB
[ 2.278095] mmcblk1boot1: mmc1:0001 MMC02G partition 2 1.00 MiB
[ 2.286745] mmcblk1: p1 p2
[ 2.292677] mmcblk1boot1: unknown partition table
[ 2.299945] mmcblk1boot0: unknown partition table
[ 2.326860] tilcdc 4830e000.fb: found TDA19988
[ 2.332409] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 2.339375] [drm] No driver support for vblank timestamp query.
[ 2.398445] usb 1-1: ep0 maxpacket = 8
[ 2.399970] usb 1-1: skipped 1 descriptor after interface
[ 2.399990] usb 1-1: skipped 1 descriptor after interface
[ 2.400142] usb 1-1: default language 0x0409
[ 2.400808] usb 1-1: udev 2, busnum 1, minor = 1
[ 2.400824] usb 1-1: New USB device found, idVendor=046d, idProduct=c52e
[ 2.400835] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.400846] usb 1-1: Product: USB Receiver
[ 2.400855] usb 1-1: Manufacturer: Logitech
[ 2.401451] usb 1-1: usb_probe_device
[ 2.401469] usb 1-1: configuration #1 chosen from 1 choice
[ 2.402199] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[ 2.402461] usbhid 1-1:1.0: usb_probe_interface
[ 2.402473] usbhid 1-1:1.0: usb_probe_interface - got id
[ 2.405201] input: Logitech USB Receiver as /devices/ocp.2/47400000.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.0/input/input1
[ 2.406022] hid-generic 0003:046D:C52E.0001: input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-musb-hdrc.1.auto-1/input0
[ 2.406201] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
[ 2.406449] usbhid 1-1:1.1: usb_probe_interface
[ 2.406461] usbhid 1-1:1.1: usb_probe_interface - got id
[ 2.414571] input: Logitech USB Receiver as /devices/ocp.2/47400000.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.1/input/input2
[ 2.416042] hid-generic 0003:046D:C52E.0002: input: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-musb-hdrc.1.auto-1/input1
[ 2.417044] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[ 2.417147] hub 1-0:1.0: port 1 enable change, status 00000103
[ 2.464362] tilcdc 4830e000.fb: Connected to an HDMI monitor with cea mode 8
[ 2.490571] Console: switching to colour frame buffer device 160x45
[ 2.585120] tilcdc 4830e000.fb: fb0: frame buffer device
[ 2.590797] tilcdc 4830e000.fb: registered panic notifier
[ 2.596491] [drm] Initialized tilcdc 1.0.0 20121205 on minor 0
[ 2.651891] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 2.658321] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[ 2.666067] libphy: 4a101000.mdio: probed
[ 2.670356] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[ 2.680213] Detected MACID = c8:a0:30:ab:84:fb
[ 2.684912] cpsw 4a100000.ethernet: NAPI disabled
[ 2.692026] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
[ 2.753388] tilcdc 4830e000.fb: timeout waiting for framedone
[ 2.767240] ALSA device list:
[ 2.770364] #0: TI BeagleBone Black
[ 2.805633] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 2.814270] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 2.825859] devtmpfs: mounted
[ 2.829395] Freeing init memory: 288K
[ 4.510755] udevd[196]: starting version 175
[ 8.963612] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 9.377307] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[ 15.482101] net eth0: initializing cpsw version 1.12 (0)
[ 15.489844] net eth0: phy found : id is : 0x7c0f1
[ 15.494770] libphy: PHY 4a101000.mdio:01 not found
[ 15.499777] net eth0: phy 4a101000.mdio:01 not found on slave 1
[ 15.511858] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 18.568328] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
[ 18.574320] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 20.163339] Key type cifs.spnego registered
[ 20.167911] Key type cifs.idmap registered
[ 25.668780] Bluetooth: Core ver 2.16
[ 25.673449] NET: Registered protocol family 31
[ 25.678324] Bluetooth: HCI device and connection manager initialized
[ 25.688146] Bluetooth: HCI socket layer initialized
[ 25.695837] Bluetooth: L2CAP socket layer initialized
[ 25.704181] Bluetooth: SCO socket layer initialized
[ 25.755828] Bluetooth: RFCOMM TTY layer initialized
[ 25.762616] Bluetooth: RFCOMM socket layer initialized
[ 25.768124] Bluetooth: RFCOMM ver 1.11
[ 25.814747] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 25.820411] Bluetooth: BNEP filters: protocol multicast
[ 25.833630] Bluetooth: BNEP socket layer initialized
[ 27.482076] tilcdc 4830e000.fb: timeout waiting for framedone
[ 57.827071] CIFS VFS: server 192.168.0.100 of type Samba 3.0.34 returned unexpected error on SMB posix open, disabling posix open support. Check if server update available.
[ 58.424554] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[ 826.451936] bone-capemgr bone_capemgr.9: part_number 'PyBBIO-ADC', version 'N/A'
[ 826.460463] bone-capemgr bone_capemgr.9: slot #6: generic override
[ 826.467012] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 6
[ 826.475012] bone-capemgr bone_capemgr.9: slot #6: 'Override Board Name,00A0,Override Manuf,PyBBIO-ADC'
[ 826.485564] bone-capemgr bone_capemgr.9: slot #6: Requesting part number/version based 'PyBBIO-ADC-00A0.dtbo
[ 826.498860] bone-capemgr bone_capemgr.9: slot #6: Requesting firmware 'PyBBIO-ADC-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[ 826.520698] bone-capemgr bone_capemgr.9: slot #6: dtbo 'PyBBIO-ADC-00A0.dtbo' loaded; converting to live tree
[ 826.532095] bone-capemgr bone_capemgr.9: slot #6: #1 overlays
[ 826.544026] ti_tscadc 44e0d000.tscadc: Initialized OK.
[ 826.557299] bone-capemgr bone_capemgr.9: slot #6: Applied #1 overlays.
[ 826.671996] bone-capemgr bone_capemgr.9: part_number 'PyBBIO-AIN0', version 'N/A'
[ 826.680826] bone-capemgr bone_capemgr.9: slot #7: generic override
[ 826.687371] bone-capemgr bone_capemgr.9: bone: Using override eeprom data at slot 7
[ 826.695373] bone-capemgr bone_capemgr.9: slot #7: 'Override Board Name,00A0,Override Manuf,PyBBIO-AIN0'
[ 826.708848] bone-capemgr bone_capemgr.9: slot #7: Requesting part number/version based 'PyBBIO-AIN0-00A0.dtbo
[ 826.719443] bone-capemgr bone_capemgr.9: slot #7: Requesting firmware 'PyBBIO-AIN0-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
[ 826.738784] bone-capemgr bone_capemgr.9: slot #7: dtbo 'PyBBIO-AIN0-00A0.dtbo' loaded; converting to live tree
[ 826.750116] bone-capemgr bone_capemgr.9: slot #7: #1 overlays
[ 826.762905] bone-capemgr bone_capemgr.9: slot #7: Applied #1 overlays.
[ 826.814042] bone-iio-helper PyBBIO-AIN0.14: Could not get AIN0 analog input
root@debian-armhf:/usr/local/lib/PyBBIO/examples#

from pybbio.

Looks like I have a similar issue:
Ubuntu 13.04, kernel 3.8.13-bone26, just installed PyBBIO as instructed above.
I'm trying both PyBBIO and Adafruit_BBIO 0.20, where I am able to use all four PWM pins but there setting the PWM frequency leads to issues.

analogWrite(PWM2A, 0) and analogWrite(PWM1A, 0) work fine.
analogWrite(PWM2B, 0) and analogWrite(PWM1B, 0) looks like the same error that bmillier postet:

analogWrite(PWM1B, 0)
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/bbio/platform/beaglebone/bone_3_8/pwm.py", line 28, in analogWrite
pwmEnable(pwm_pin)
File "/usr/local/lib/python2.7/dist-packages/bbio/platform/beaglebone/bone_3_8/pwm.py", line 98, in pwmEnable
if (sysfs.kernelFilenameIO('%s/%s' % (helper_path, PWM_RUN)) == '1\n'):
File "/usr/local/lib/python2.7/dist-packages/bbio/platform/beaglebone/sysfs.py", line 21, in kernelFilenameIO
fn = glob.glob(fn)[0]

What's the output of |# cat /sys/devices/bone_capemgr.*/slots|?

0: 54:PF---
1: 55:PF---
2: 56:PF---
3: 57:PF---
4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
7: ff:P-O-L Override Board Name,00A0,Override Manuf,PyBBIO-epwmss2
8: ff:P-O-L Override Board Name,00A0,Override Manuf,PyBBIO-ehrpwm2
9: ff:P-O-L Override Board Name,00A0,Override Manuf,bone_pwm_P8_19
10: ff:P-O-L Override Board Name,00A0,Override Manuf,bone_pwm_P8_13
11: ff:P-O-L Override Board Name,00A0,Override Manuf,am33xx_pwm
13: ff:P-O-L Override Board Name,00A0,Override Manuf,PyBBIO-epwmss1
14: ff:P-O-L Override Board Name,00A0,Override Manuf,PyBBIO-ehrpwm1
15: ff:P-O-L Override Board Name,00A0,Override Manuf,bone_pwm_P9_14
16: ff:P-O-L Override Board Name,00A0,Override Manuf,bone_pwm_P9_16

from pybbio.

Please post the full error traceback that you're getting.

from pybbio.

Hi Alexander
I replied to this email back when you sent it to me, with the info
attached in a file. I didn't hear back, and was reminded of this when I
was copied on a post by someone else with similar problems. I'm just
letting you know that I am still unable to use the lib. as mentioned in
earlier emails.

Brian Millier
Computer Interface Consultants
31 Three Brooks Drive
Hubley, N.S. B3Z 1A3
902 876-8645
Cell 902 473- 9499

On 05/08/2014 7:25 PM, Alexander Hiam wrote:

OK, everything is getting installed correctly, so capemgr must be
unable to load the overlays.

Do you have any other overlays loaded? What's the output of |# cat
/sys/devices/bone_capemgr.*/slots|?

Also post (or pastebin) the output of |# dmesg| after trying to run
|analog_test.py|.

—
Reply to this email directly or view it on GitHub
#18 (comment).

from pybbio.

@smaria, @bmillier: I'm closing this issue since the original problem has been solved, please both open a new issue and we'll go from there.

from pybbio.

I am running in to this issue with a Beaglebone black Rev C I just purchased, by default it came with:
Linux version 3.8.13-bone47 (gcc version 4.6.3 (Debian 4.6.3-14) )
Debian GNU/Linux 7.4 (wheezy)

It is not the Python library, I get this same error when setting PWM manually, P8 13 does not create run, duty, period, etc interface files.

I am about to learn how to build the kernel and reflash. Any steps anyone can provide for this? @alexanderhiam
I think the file is now in ti-linux-kernel-dev/patches/defconfig
CONFIG_PWM_TIEHRPWM=m
Thanks.

from pybbio.