Dan.

I haven’t tried it yet, but apparently the Cloud9 and bonescript packages are available for the Beagleboard if you install a 2012 Angstrom image. See this post in Beagleboard Google Groups: http://groups.google.com/group/beagleboard/browse_thread/thread/742c5f7a55039d3c/25c9c3816b810a33?lnk=gst&q=beagleboard+cloud9#25c9c3816b810a33

If the kernel in that image includes support for accessing the GPIO pins through the filesystem (i.e. omapmux etc) then much of bonescript would be usable.

My Beagleboard Rev C is running an old version of Ubuntu – I’ll have to try out a new Angstrom build to see what is possible.

Dan.

I get the same results if I set gpmc_ad7 to mode 7: the signals line seems to indicate it isn’t supported.

However, most of the GPIO pins indicate “NA” for Mode 7, but most work correctly in this mode. This post in the Beagleboard Google Groups forum indicates that it’s a known problem which (I think) only affects the output of the signals line, not the behaviour of the pin:

http://groups.google.com/group/beagleboard/browse_thread/thread/6c665c087c07c2b2/8126e0d4afe2a2b3?lnk=gst&q=beaglebone+user+leds#8126e0d4afe2a2b3

However, gpmc_ad7 (Pin 4 on Port 8 ) has another problem: if you try to interact with it through the file system, you’ll likely get an error…

root@gigamegabone:/sys/class/gpio# echo 39 > export
sh: write error: Device or resource busy

I haven’t found an explanation for this. I can only assume that the pin really is in use by some other software.

I’ve found that the next 2 pins on Port 8 (5 and 6) work as expected as GPIO pins, when put in mode 7 (they are in mode 0 by default). These are gpmc_ad2 (GPIO 34) and gpmc_ad3 (GPIO 35).

HTH,

Dan.

Question, I am able to get P8_3 working as you describe in the tutorial, but I cannot seem to get the GPIO to work on any other pins. For gpmc_ad6 it shows gpio1_6 which matches the BeagleBone manual. For P8_4, however, gpmc_ad7 should have gpio1_7, but instead shows “NA” as shown below.


cat /sys/kernel/debug/omap_mux/gpmc_ad6
name: gpmc_ad6.gpio1_6 (0x44e10818/0x818 = 0x0037), b NA, t NA
mode: OMAP_PIN_OUTPUT | OMAP_MUX_MODE7
signals: gpmc_ad6 | mmc1_dat6 | NA | NA | NA | NA | NA | gpio1_6

/sys/kernel/debug/omap_mux/gpmc_ad7
name: gpmc_ad7.(null) (0x44e1081c/0x81c = 0x0037), b NA, t NA
mode: OMAP_PIN_OUTPUT | OMAP_MUX_MODE7
signals: gpmc_ad7 | mmc1_dat7 | NA | NA | NA | NA | NA | NA


Is there something special I need to do to make this pin accessible as GPIO, or can it not be configured that way? Any help would be greatly appreciated. Thanks.