Groups
Groups
Sign in
Groups
Groups
BeagleBoard
Conversations
Labels
About
Send feedback
Help
Beagle Bone black debain gpio access denied
93 views
beaglebone-black
debian
linux
newbies
support
Skip to first unread message
Hemant Kapoor
unread,
Feb 2, 2018, 1:01:43 PM
2/2/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to BeagleBoard
Hello,
Yet another newbie question.
I have got latest debian image on my beagle bone black.
uname - r output: 4.9.45-ti-r57
and I noticed various gpio directory in /sys/class/gpio
when I tried
echo 69 > unexport
it gave me permission denied.
so I changed the permission of unexport file to be 666
and now when I try to use the same command it gives me an error:
-bash: echo: write error: Invalid argument
Can anyone please help...
Ultimately I want to develop a C++ project to toggle LED which is connected to one of the pins...
Any help regarding this matter is deeply appreciated.
Regards,
Hemant Kapoor
Jeff Andich
unread,
Feb 5, 2018, 2:46:12 PM
2/5/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to BeagleBoard
Switching to root before doing sysfs operations, (e.g. sudo su), typically seems to work for me..
Hemant Kapoor
unread,
Feb 13, 2018, 3:45:28 PM
2/13/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to BeagleBoard
Hello,
Thanks for the response...
I did manage to sort the issue by performing two steps:
a. Added a udev rule to make gpio accessible
b. Added user to gpio group...
Regards,
Hemant Kapoor
Reply all
Reply to author
Forward
0 new messages