This message was posted on behalf of Intel Corporation
What image are you using, ubclibc or eglibc? Using your current libraries and daemons are you able to run the code for every GPIO except GPIO2?
What MRAA version are you using?
In case you haven’t done this yet, look at the steps for installing MRAA & UPM Library on Intel IoT Platform with IoTDevKit Linux* image
1. echo "src maa-upm http://iotdk.intel.com/repos/1.1/intelgalactic" > /etc/opkg/intel-iotdk.conf
2. opkg update
3. opkg upgrade
there was a bug related only with GPIO2 of Galileo Gen2 board.It is already fixed in MRAA version 1.0.0 on May 20, 2016.
A MRAA version 1.0.0 build compiled from the source before May 20, 2016 will have a problem.
So, need to update MRAA to the latest MRAA build created after May 20, 2016.
Now it looks like:
A possible solution is to build MRAA from the source.
there are about 14 different subversions of MRAA version 1.0.0.
As I have already mentioned above not all of them have a fixed GPIO2 issue.
The source means a source code located at GitHub - intel-iot-devkit/mraa: Low Level Skeleton Library for IO Communication on GNU/Linux platforms
If you are not familiar with a MRAA compilation, it is better to use the previous MRAA version or wait when a new MRAA build will be available.
PS: as you may find http://iotdk.intel.com/repos/3.0/intelgalactic/opkg/i586 has MRAA build with a date
- mraa_1.0.0_i586.ipk (md5: aa82c905113ccaec0952c269331e5ba7, size: 342534 bytes, last modified: Thu, 28 Apr 2016 08:08:24 -0700)
It means that commands like
echo "src mraa-upm http://iotdk.intel.com/repos/3.0/intelgalactic-dev/opkg/i586" > /etc/opkg/mraa-upm.conf opkg update opkg install mraa
will not help to fix the GPIO2 issue.