Ok, first I'm not an EE, so if I make a statement that's obviously wrong
from that perspective. . .

Anyway . . . I have a custom cape with several LED's on it here. Connected
to a Beagelbone green.

LED is on:
william@beaglebone:~$ cat /sys/class/gpio/gpio110/value
1

LED goes off:
william@beaglebone:~$ sudo sh -c "echo '0' > /sys/class/gpio/gpio110/value"
william@beaglebone:~$ cat /sys/class/gpio/gpio110/value
0

LED comes back on:
william@beaglebone:~$ sudo sh -c "echo '1' > /sys/class/gpio/gpio110/value"

unexport does not work for me:
william@beaglebone:~$ sudo sh -c "echo '110' > /sys/class/gpio/unexport"
sh: echo: I/O error

Maybe I'm doing this wrong, because honestly I have not been using the
sysfs gpio file directly in around . . .I do not know, maybe 6 months. I've
been using config-pin with universal IO. But it is my assumption that I am
unable to unexport because of something related to universal IO, and my
custom cape / overlay.

But yes, the pins on a beaglebone are all set to come up as inputs by
default. Then they can be used as gpio without any overlay, just by
exporting the pins, then configurering them the way you want. Through the
sysfs gpio file structure.

So why don't you copy paste what you're attempting from the command line,
along with the errors you're getting if any. If you're not getting any
errors, but no physical feedback through the LED going off and on. Then
you're probably connected to the wrong pin out of the header.

Another thing that comes to mind, is that possibly your circuit there is
reverse logic.

By the way, I have the book, but this is not an issue with Derrek's book, I
know that for a fact. You're doing something differently, or wrong for your
situation. Maybe something has changed, but you're most likely using a
3.8.11-bone47 kernel. Which should be exactly the same kernel Derek was
using.


On Mon, Oct 24, 2016 at 1:19 PM, mzimmers <[email protected]> wrote:

> Hi, William - thanks for the quick reply. The system is whatever the BBB
> came with (I got it about a month ago). The uname command suggests it was
> built Oct 13 2015. I've done no other setup other than build the circuit
> and follow the instructions on page 205 of The Book.
>
> So, if deleting the entry for gpio49 doesn't do anything, do I correctly
> infer that the "default" state of the hardware is a closed circuit (LED on)?
>
> Thanks for the help.
>
> mz
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/12bf0dde-280e-4212-9b66-fa3f886801a1%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/12bf0dde-280e-4212-9b66-fa3f886801a1%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORrvWnOyau0Rf%3D%2BFVgfsZ%3DYq7TEAh1RfNURLcgdSY%2B3tYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to