Odroid C1/C1+ GPIO Export Not Working #298

savageautomate opened this Issue Dec 29, 2016 · 1 comment


None yet

1 participant


Original Issue Thread:

Hi, I am having issues getting to run my application on an Odroid C1+ board running Ubuntu 14.04. The same error happens even when I run the GPIO input example provided.

Exception in thread "main" java.lang.RuntimeException: Unable to open GPIO export interface: No such file or directory

at com.pi4j.wiringpi.GpioUtil.export(Native Method)
at com.pi4j.io.gpio.WiringPiGpioProviderBase.export(WiringPiGpioProviderBase.java:108)
at com.pi4j.io.gpio.OdroidGpioProvider.export(OdroidGpioProvider.java:157)
at com.pi4j.io.gpio.impl.GpioPinImpl.export(GpioPinImpl.java:158)
at com.pi4j.io.gpio.impl.GpioControllerImpl.provisionPin(GpioControllerImpl.java:565)
at com.pi4j.io.gpio.impl.GpioControllerImpl.provisionPin(GpioControllerImpl.java:538)
at com.pi4j.io.gpio.impl.GpioControllerImpl.provisionDigitalInputPin(GpioControllerImpl.java:639)
at com.pi4j.io.gpio.impl.GpioControllerImpl.provisionDigitalInputPin(GpioControllerImpl.java:667)
at com.pi4j.io.gpio.impl.GpioControllerImpl.provisionDigitalInputPin(GpioControllerImpl.java:679)
at odroid.c1.GpioInputExample.main(GpioInputExample.java:110)

I looks like newer kernel builds have replaced the "aml_gpio" kernel module in favor of the standard GPIO file system interface. (sometime after v3.10.96-143).

Pi4J native sources need to be modified to use the standard /sys/class/gpio pseudo file system interfaces rather than /sys/class/aml_gpio

@savageautomate savageautomate added the bug label Dec 29, 2016
@savageautomate savageautomate added this to the RELEASE 1.2 milestone Dec 29, 2016
@savageautomate savageautomate self-assigned this Dec 29, 2016
@savageautomate savageautomate added a commit that closed this issue Dec 29, 2016
@savageautomate savageautomate fixed #298; Pi4J native sources updated to use the standard "/sys/cla…
…ss/gpio" pseudo file system interface rather than ""/sys/class/aml_gpio" for Odroid C1/C1+ platform.

This fix is now available in the latest 1.2-SNAPSHOT build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment