From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from astoria.ccjclearline.com ([64.235.106.9]) by casper.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1RvZ8F-0004WE-HU for barebox@lists.infradead.org; Thu, 09 Feb 2012 18:54:13 +0000 Date: Thu, 9 Feb 2012 13:54:01 -0500 (EST) From: "Robert P. J. Day" In-Reply-To: <20120209194301.75adb5dc@eb-e6520> Message-ID: References: <20120209174519.4d0ae559@eb-e6520> <20120209194301.75adb5dc@eb-e6520> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-984223648-1328813646=:3047" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: barebox-bounces@lists.infradead.org Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: how to read GPIO values from command line? To: =?ISO-8859-15?Q?Eric_B=E9nard?= Cc: barebox@lists.infradead.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-984223648-1328813646=:3047 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 9 Feb 2012, Eric B=E9nard wrote: > Le Thu, 9 Feb 2012 13:37:34 -0500 (EST), > "Robert P. J. Day" a =E9crit : > > > On Thu, 9 Feb 2012, Eric B=E9nard wrote: > > > > > Le Thu, 9 Feb 2012 11:34:55 -0500 (EST), > > > "Robert P. J. Day" a =E9crit : > > > > 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? > > > see the corresponding registers with md never mind, i think i just figured out i have a lot more work ahead of me. i popped into the panda directory, and noticed that honking big mux.c file, which i'm guessing i'll have for the beagle as well, and that's a bit over my head at the moment. rday --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --8323329-984223648-1328813646=:3047 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox --8323329-984223648-1328813646=:3047--