Hi Niv- I've been looking at the kernel 4 implementation of device trees today. Here are a couple of things which may help.
cd to this directory: /sys/devices/platform/ocp/ocp:cape-universal ls and you should see a file called status. cat status This should give you a listing of the currently enabled GPIOs. "ocp" means "on chip peripheral". A GPIO is one of several types of ocp. Here is the first few lines of what I see on my BBB: 0 P9_92 114 IN 0 1 P9_42 7 IN 0 2 P9_91 116 IN 0 3 P9_30 112 IN 0 4 P9_27 115 IN 0 5 P9_26 14 IN 0 6 P9_24 15 IN 0 7 P9_23 49 IN 0 8 P9_22 2 IN 0 9 P9_21 3 IN 0 This continues on and shows GPIOs enabled on the P8 header as well. So just taking an example P9_27: config-pin -q P9_27 P9_27 Mode: default Direction: in Value: 0 The command runs successfully. Now, try the command on a pin which is not listed in the status file: config-pin -q P9_28 P9_28 pinmux file not found! cape-universala overlay not found run "config-pin overlay cape-universala" to load the cape So I reproduce the a similar result as what you see for P8_43. There is no overlay cape-universala being compiled by Robert's script. The command config-pin was written by another person and is described here: https://github.com/cdsteinkuehler/beaglebone-universal-io I suspect the error message being emitted by config-pin needs to be updated. Otherwise, the first part of the error message is correct in that the GPIO is not active on the pin. The pin you need as a GPIO P8_43 needs to be designated as such by the overlay file. Now, the question is, does one of the existing overlay files have this pin designated as GPIO? Regards, Greg -- 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.
