Sounds like it is time to "ping" the uboot maintainer perhaps . . .
On Mon, Sep 14, 2015 at 2:15 PM, Francisco Aguerre < [email protected]> wrote: > The help of the gpio command doesn't say much. > > gpio <input|set|clear|toggle> <pin> > - input/set/clear/toggle the specified pin > gpio status [-a] [<bank> | <pin>] - show [all/claimed] GPIOs > > On the previous version pin= 32*(gpio port number +1) + port pin > > Maybe now they are identified differently, but I could not find a > definition in the source code files. Also the command "gpio status -a" > doesn't return anything. > > Regards, > > Francisco > > > > On Monday, September 14, 2015 at 5:27:24 PM UTC-3, William Hermans wrote: >> >> Only thing I could find on short notice in regard to error -22 . . . >> >> *Regarding errors -32 and -22 - those are low-level errors and doesn't >>> tell much to end user.* >>> *-32 means EPIPE (broken pipe)* >>> *-22 means EINVAL (invalid argument)* >> >> >> So perhaps check the uboot gpio command ( help gpio - or however it works >> in uboot ). To make sure you are using the command correctly. e.g. maybe it >> has changed more recently ? >> >> On Mon, Sep 14, 2015 at 1:16 PM, Francisco Aguerre <[email protected] >> > wrote: >> >>> Hello, >>> >>> I have a rev B BeagleBone Black which I have been using for over a year >>> as a development platform for a pseudo-clone board we are developing. We >>> are using QNX as our OS. >>> >>> Lately I have been tinkering with U-Boot to learn how the boot process >>> works and configure our board properly. I cloned the U-boot git repository >>> and built the 2015.10-rc2 version. The board boots fine and now the MPU >>> frequency gets configured at 1GHz, but the thing is that the gpio console >>> command doesn't seem to work anymore. >>> >>> Previously I used the 2013.04 version of U-Boot and could toggle leds >>> using the gpio comand (i.e. "gpio toggle 54" ), but now the same command >>> just returns an error message "Command 'gpio' failed: Error -22". >>> >>> Is there anything I've missed to make this command work properly? For >>> building u-boot I used the following commands: >>> >>> $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- distclean >>> $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- >>> am335x_boneblack_defconfig >>> $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- >>> >>> Any help will be appreciated! If you need aditional information, please >>> ask! >>> >>> Regards, >>> >>> Francisco >>> >>> -- >>> 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]. >>> 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]. > 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]. For more options, visit https://groups.google.com/d/optout.
