px4io: moving mixing to FMU side

Using mixers on the IO side had a remote benefit of being able to
override all control surfaces with a radio remote on a fixed wing.
This ended up not being used that much and since the original design
10 years ago (2011) we have been able to convince ourselves that the
overall system stability is at a level where this marginal benefit,
which is not present on multicopters, is not worth the hazzle.

Co-authored-by: Beat Küng <beat-kueng@gmx.net>
Co-authored-by: Daniel Agar <daniel@agar.ca>

ROMFS/px4fmu_test/init.d/rcS

@@ -70,14 +70,6 @@ then
 	set io_file /etc/extras/px4_io-v2_default.bin
 fi
 
-if px4io start
-then
-	echo "PX4IO OK"
-else
-	set unit_test_failure 1
-	set unit_test_failure_list "${unit_test_failure_list} px4io_start"
-fi
-
 if px4io checkcrc $io_file
 then
 	echo "PX4IO CRC OK"
@@ -104,6 +96,15 @@ else
 	fi
 fi
 
+if px4io start
+then
+	echo "PX4IO OK"
+else
+	set unit_test_failure 1
+	set unit_test_failure_list "${unit_test_failure_list} px4io_start"
+fi
+
+
 #
 # The presence of this file suggests we're running a mount stress test
 #