Adding documentaion and fix

Board - AlienWii32.md
Spectrum bind.md
Adding Feature failsave

docs/Board - AlienWii32.md

@@ -0,0 +1,24 @@
+# Board - AlienWii32
+
+The AlienWii32 is actually in prototype stage only a few sample exist. There is some more field testing ongoing. The information below is preliminary an will be updated as needed.
+
+Here are the Hardware specifications:
+
+- STM32F103CBT6 MCU
+- MPU6050 accelerometer/gyro sensor unit
+- 8x 4.2A brushed ESCs, integrated, to run the strongest micro motors
+- extra-wide traces on the PCB, for maximum power throughput
+- USB port, integrated (subject to change)
+- * serial connection for external DSM2/DSMX sat receiver (e.g. Spektrum SAT, OrangeRx R100 or Lemon RX)
+- alternatively PPM receiver connection (i.e. Deltag Rx31)
+- ground and 3.3V for the receiver
+- hardware bind plug for easy binding
+- motor connections are at the corners for a clean look with reduced wiring
+- dimensions: 30x32mm
+- direct operation from an single cell lipoly battery
+
+*  Spektrum Compatible DSM2 satellites are supported out of the box. DSMX sat will work with DSM2 protocol wit default settings. Changes can be done as usual via CLI or the Cleanflight configurator.
+
+The pin layout is similar as the NAZE32 or the related clones. The hardware bind pin is connected to pin 41 (PB5). The AlienWii32 firmware will be build with TARGET=NAZE and OTIONS="AlienWii32".
+The firmware image will come with alternative default settings which will give a plug and play experience. There is no computer need to get this into the air with an smAL quadcopter.
+anyhow to use this in an Hexa- or Octocopter or to do some more tuning additional CLI changes are required as usual.

docs/Spektrum bind.md

@@ -0,0 +1,35 @@
+# Spektrum bind support
+
+Spektrum bind with hardware bind plug support.
+ 
+## Hardware
+
+The hardware bind plug will be enabled via defining HARDWARE_BIND_PLUG during building of the firmware.
+This is done automatically if the AlienWii32 firmware is build. The bind plug is expected between pin 41
+(PB5 STM32F103CBT6) and ground. The bind code will actually work for USART2 (PA3 STM32F103CBT6).
+
+## Function
+
+If the bind plug is set the bind mode will be permanently activated during the firmware start-up. The
+spektrum_sat_bind CLI parameter is defining the number of bind impulses (1-10) send to the satellite receiver.
+If there is no hardware bind plug present the bind code will be executed ones after the next start (hardware
+reset or power on) of the firmware and the spektrum_sat_bind parameter will be reset to 0 when done. The bind
+code will not be executed during an soft rest of the MCU. Please refer to your receiver documentation for more
+details of the specific receiver in bind mode. Usually the bind mode will be indicated with some flashing LED’s.
+The Bind plug should be always removed for normal flying.
+
+## Table with spektrum_sat_bind parameter Value
+
+| Value | Receiver mode  |
+| ----- | ---------------|
+| 3     | DSM2 1024/22ms |
+| 5     | DSM2 2048/11ms |
+| 7     | DSMX 22ms      |
+| 9     | DSMX 11ms      |
+
+More detailed information regarding the sattelite binding process can be found here:
+http://wiki.openpilot.org/display/Doc/Spektrum+Satellite
+
+### Supported Hardware
+
+all NAZE Targets (NAZE32, Flip32, AlienWii32 with hardware bind pin)

src/main/config/config.c

@@ -439,6 +439,7 @@ static void resetConf(void)
 #ifdef ALIENWII32
     featureSet(FEATURE_RX_SERIAL);
     featureSet(FEATURE_MOTOR_STOP);
+    featureSet(FEATURE_FAILSAVE);
     masterConfig.serialConfig.serial_port_scenario[1] = lookupScenarioIndex(SCENARIO_SERIAL_RX_ONLY);
     masterConfig.rxConfig.serialrx_provider = 1;
     masterConfig.rxConfig.spektrum_sat_bind = 5;