GPIO example does not working under Angstrom current version about adafruit-beaglebone-io-python HOT 3 CLOSED

Can you try running the test suite included with the library? The README explains how to set that up. It's the best way to test this out.

Yea, if you don't cleanup, you should see the exported GPIO files in the /sys/class/gpio.

The number with bone_capemgr.* is dynamic based on how the overlays are loaded. The library should handle this properly, and doesn't use a hardcoded value to find that directory.

from adafruit-beaglebone-io-python.

Justin,
Hrrrr typical newbie error.

I was writing the commands in a .py program when the program terminated old
setup was ripped down and the GPIO lines went blank. I executed the
commands interactively the library behaved as expected.

From some comments in the forums I realize that others are having the same
problem.

Do I withdraw the bug report with a comment?

I'll post my great discovery on one of the forum posts where I believe
someone else is having the same problem.

Thanks for getting back so quick,
-jay

On Wed, Sep 18, 2013 at 12:54 PM, Justin Cooper [email protected]:

Can you try running the test suite included with the library? The README
explains how to set that up. It's the best way to test this out.

Yea, if you don't cleanup, you should see the exported GPIO files in the
/sys/class/gpio.

The number with bone_capemgr.* is dynamic based on how the overlays are
loaded. The library should handle this properly, and doesn't use a
hardcoded value to find that directory.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-24694131
.

from adafruit-beaglebone-io-python.

Glad it's working for you.

I can close this. Thanks!

from adafruit-beaglebone-io-python.