I have downloaded and installed UDOObuntu 2.0 Beta 2 for UDOO Quad. Runs fine, but... I don't have any /sys/class/gpio/gpioXX files as described in http://www.udoo.org/tutorial/linux-gpio-manipulation/ How to control GPIO pins on UDOObuntu 2.0?
Dear psaitz, in the previous version those folder were exposed. The command to have those folder exposed is: where XX is a number related to the GPIO that can take from this image (check the number on the white label) http://udoo.org/download/files/pinout/Udoo_pinout_diagram.pdf
Thanks Andrea, echo XXX > export works fine. But after a reboot, the exported gpioXXX directories are lost and I have to export the required pins again. Another disadvantage is: export requires root priviledges and the created directory/files are assigned to root/root. So I have to chgrp and chmod too. Otherwise standard users have no access to GPIO pins.
This is the usual / standard way of dealing with GPIOs as seen on other boards. Perhaps it's not ideal but it's standard. If you change this, people will need to adjust/port existing scripts. I can imagine the anger
