@JPMontero_Intel
Thanks for all of the details!
Presumably, `system` is being used in a sketch? This is out of scope for the project I'm working on, which is a node.js module for controlling the Galileo's GPIO (rwaldron/galileo-io · GitHub)—that is to say that there is no sketch involved.
Also you can use this function to control pin 13, for this you would have to program gpio55 to mux the gpio39, if this is not clear take a look at Sergey’s bloghttp://www.malinov.com/Home/sergey-s-blog/intelgalileo-programminggpiofromlinux , right where it says GPIO Mapping in Galileo, take a look at the picture and look for the pin 13, you'll see that the gpio55 control the gpio39 or the SPI1_SCK. If you program this three GPIOs 3, 55 and 39 you would be able to use the LED and pin 13 one independent from the other.
Yes, thank you—this is what I followed to design the GPIO mapping and muxing system. I think what I actually want to do is control them as one, because user code will expect writes to pin 13 to behave the same as they do in sketches. When the Galileo is running the Blink.ino sketch, how does it know that user code:
int led = 13;
void setup() {
pinMode(led, OUTPUT);
}
void loop() {
digitalWrite(led, HIGH);
delay(1000);
digitalWrite(led, LOW);
delay(1000);
}
...referring to pin 13 actually means "write to the onboard led*, not the actual pin 13**"
* gpio3
** gpio55 mux to gpio39