don't setup (export/unexport) gpio pins on execution

This fixes the issue that the new firmware recreates the whole
gpio file structure on unexport/export so the ownership of all
files is root:root and the gpio group is dropped.

Because of this all unexport is removed from the calling scripts
and a setup script is added that needs to be invoked once after
startup.

lock

@@ -2,12 +2,7 @@
 . $(dirname $(readlink "$0"))/shared
 
 echo "Initializing Space Systems..."
-echo "22" > /sys/class/gpio/unexport
-echo "22" > /sys/class/gpio/export
-sleep 0.5
 echo "Securing Communication to Space Systems..."
-echo "out" > /sys/class/gpio/gpio22/direction
-sleep 0.5
 echo "Open Communication Channel..."
 # Silent, Output to /dev/null, Timeout after 5s and retry 12 times, each doubling the waitingtime until ten minutes.
 nohup curl -s -o /dev/null -m 5 --connect-timeout 5 --retry 12 "https://hamburg.ccc.de/dooris/status.php?apikey=${password}&action=close" >/dev/null 2>&1 &

setup

+#!/bin/sh
+
+echo "Setting up gpio: unlock"
+echo "27" > /sys/class/gpio/unexport
+echo "27" > /sys/class/gpio/export
+echo "out" > /sys/class/gpio/gpio27/direction
+chown -R root:gpio /sys/class/gpio/gpio27/*
+chmod g+w /sys/class/gpio/gpio27/*
+
+echo "Setting up gpio: lock"
+echo "27" > /sys/class/gpio/unexport
+echo "22" > /sys/class/gpio/unexport
+echo "22" > /sys/class/gpio/export
+echo "out" > /sys/class/gpio/gpio22/direction
+chown -R root:gpio /sys/class/gpio/gpio22/*
+chmod g+w /sys/class/gpio/gpio22/*

unlock

@@ -2,12 +2,7 @@
 . $(dirname $(readlink "$0"))/shared
 
 echo "Initializing Space Systems..."
-echo "27" > /sys/class/gpio/unexport
-echo "27" > /sys/class/gpio/export
-sleep 0.5
 echo "Securing Communication to Space Systems..."
-echo "out" > /sys/class/gpio/gpio27/direction
-sleep 0.5
 echo "Open Communication Channel..."
 nohup curl -s -o /dev/null -m 5 --connect-timeout 5 --retry 12 "https://hamburg.ccc.de/dooris/status.php?apikey=${password}&action=open" >/dev/null 2>&1 &
 echo "Unlocking Space..."