From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: "Eric Bénard" <eric@eukrea.com>
Cc: barebox@lists.infradead.org
Subject: Re: how to read GPIO values from command line?
Date: Thu, 9 Feb 2012 13:37:34 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1202091336340.2680@oneiric> (raw)
In-Reply-To: <20120209174519.4d0ae559@eb-e6520>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1147 bytes --]
On Thu, 9 Feb 2012, Eric Bénard wrote:
> Le Thu, 9 Feb 2012 11:34:55 -0500 (EST),
> "Robert P. J. Day" <rpjday@crashcourse.ca> a écrit :
> > so what exactly does one do to read those values? i tried:
> >
> > barebox@Texas Instrument's Beagle:/ gpio_direction_input 171
> > barebox@Texas Instrument's Beagle:/ gpio_get_value 171
> >
> > but what do i check? the shell variable $? i'm not sure what i
> > should do next.
> >
> you can check the mux of the pins to be sure they are in GPIO mode.
how do i do that from the barebox prompt? i can see the
gpio-related commands for setting direction and getting/setting
values, but how does one check if those pins are properly in gpio
mode?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-02-09 18:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 16:34 Robert P. J. Day
2012-02-09 16:45 ` Eric Bénard
2012-02-09 17:32 ` Robert P. J. Day
2012-02-09 18:37 ` Robert P. J. Day [this message]
2012-02-09 18:43 ` Eric Bénard
2012-02-09 18:54 ` Robert P. J. Day
2012-02-10 7:34 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1202091336340.2680@oneiric \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=eric@eukrea.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox