Skip to content

Commit 996d72e

Browse files
hydrahydra
committed
Merge branch 'AlienWii32_defaults' of
https://github.com/MJ666/cleanflight into MJ666-AlienWii32_defaults Conflicts: src/main/target/NAZE/target.h
2 parents e7cac19 + 73869a7 commit 996d72e

File tree

8 files changed

+1737
-1590
lines changed

8 files changed

+1737
-1590
lines changed

‎JLinkSettings.ini

+31-31
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,31 @@
1-
[BREAKPOINTS]
2-
ShowInfoWin = 1
3-
EnableFlashBP = 2
4-
BPDuringExecution = 0
5-
[CFI]
6-
CFISize = 0x00
7-
CFIAddr = 0x00
8-
[CPU]
9-
OverrideMemMap = 0
10-
AllowSimulation = 1
11-
ScriptFile=""
12-
[FLASH]
13-
MinNumBytesFlashDL = 0
14-
SkipProgOnCRCMatch = 1
15-
VerifyDownload = 1
16-
AllowCaching = 1
17-
EnableFlashDL = 2
18-
Override = 0
19-
Device="AD7160"
20-
[GENERAL]
21-
WorkRAMSize = 0x00
22-
WorkRAMAddr = 0x00
23-
[SWO]
24-
SWOLogFile=""
25-
[MEM]
26-
RdOverrideOrMask = 0x00
27-
RdOverrideAndMask = 0xFFFFFFFF
28-
RdOverrideAddr = 0xFFFFFFFF
29-
WrOverrideOrMask = 0x00
30-
WrOverrideAndMask = 0xFFFFFFFF
31-
WrOverrideAddr = 0xFFFFFFFF
1+
[BREAKPOINTS]
2+
ShowInfoWin = 1
3+
EnableFlashBP = 2
4+
BPDuringExecution = 0
5+
[CFI]
6+
CFISize = 0x00
7+
CFIAddr = 0x00
8+
[CPU]
9+
OverrideMemMap = 0
10+
AllowSimulation = 1
11+
ScriptFile=""
12+
[FLASH]
13+
MinNumBytesFlashDL = 0
14+
SkipProgOnCRCMatch = 1
15+
VerifyDownload = 1
16+
AllowCaching = 1
17+
EnableFlashDL = 2
18+
Override = 0
19+
Device="AD7160"
20+
[GENERAL]
21+
WorkRAMSize = 0x00
22+
WorkRAMAddr = 0x00
23+
[SWO]
24+
SWOLogFile=""
25+
[MEM]
26+
RdOverrideOrMask = 0x00
27+
RdOverrideAndMask = 0xFFFFFFFF
28+
RdOverrideAddr = 0xFFFFFFFF
29+
WrOverrideOrMask = 0x00
30+
WrOverrideAndMask = 0xFFFFFFFF
31+
WrOverrideAddr = 0xFFFFFFFF

‎docs/Board - AlienWii32.md

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# Board - AlienWii32
2+
3+
The AlienWii32 is actually in prototype stage only a few samples exist. There is some more field testing ongoing. The information below is preliminary and will be updated as needed.
4+
5+
Here are the hardware specifications:
6+
7+
- STM32F103CBT6 MCU
8+
- MPU6050 accelerometer/gyro sensor unit
9+
- 8x 4.2A brushed ESCs, integrated, to run the strongest micro motors
10+
- extra-wide traces on the PCB, for maximum power throughput
11+
- USB port, integrated
12+
- (*) serial connection for external DSM2/DSMX sat receiver (e.g. Spektrum SAT, OrangeRx R100 or Lemon RX)
13+
- alternatively PPM receiver connection (i.e. Deltang Rx31)
14+
- ground and 3.3V for the receiver
15+
- hardware bind plug for easy binding
16+
- motor connections are at the corners for a clean look with reduced wiring
17+
- dimensions: 29x33mm
18+
- direct operation from an single cell lipoly battery
19+
20+
(*) Spektrum Compatible DSM2 satellites are supported out of the box. DSMX sat will work with DSM2 protocol with default settings (DSM2, 11bit, 11ms is preset).
21+
22+
Deltang receivers in serial mode will work like any other Spektrum satellite receiver (10bit, 22ms) only the bind process will be different.
23+
24+
The pin layout is very similar as the NAZE32 or the related clones (MW32, Flip32, etc.). The hardware bind pin is connected to pin 41 (PB5). The AlienWii32 firmware will be built with TARGET=NAZE and OPTIONS="AlienWii32". The firmware image will come with alternative default settings which will give the user a plug and play experience. There is no computer needed to get this into the air with an small Quadcopter. An preconfigured custom mixer for an Octocopter is part of the default settings to allow clean straight wiring with the AlienWii32. The mixer can be activated with "mixer custom" in the CLI. To use the AlienWii32 in an Hexa- or Octocopter or to do some more tuning additional configuration changes can be done as usual in the CLI or the Cleanflight configurator.

‎docs/Spektrum bind.md

+49
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# Spektrum bind support
2+
3+
Spektrum bind with hardware bind plug support.
4+
5+
The Spektrum bind code is actually enabled for the NAZE, NAZE32PRO, CJMCU, EUSTM32F103RC, SPARKY, CC3D targets.
6+
7+
## Configure the bind code
8+
9+
The following parameters can be used to enable and configure this in the related target.h file:
10+
11+
SPEKTRUM_BIND Enables the Spektrum bind code
12+
BIND_PORT GPIOA Defines the port for the bind pin
13+
BIND_PIN Pin_3 Defines the bind pin (the satellite receiver is connected to)
14+
15+
This is to activate the hardware bind plug feature
16+
17+
HARDWARE_BIND_PLUG Enables the hardware bind plug feature
18+
BINDPLUG_PORT GPIOB Defines the port for the hardware bind plug
19+
BINDPLUG_PIN Pin_5 Defines the hardware bind plug pin
20+
21+
## Hardware
22+
23+
The hardware bind plug will be enabled via defining HARDWARE_BIND_PLUG during building of the firmware. BINDPLUG_PORT and BINDPLUG_PIN also need to be defined (please see above). This is done automatically if the AlienWii32 firmware is build. The hardware bind plug is expected between the defined bind pin and ground.
24+
25+
## Function
26+
27+
The bind code will actually work for NAZE, NAZE32PRO, CJMCU, EUSTM32F103RC, SPARKY targets (USART2) and CC3D target (USART3, flex port). The spektrum_sat_bind CLI parameter is defining the number of bind impulses (1-10) send to the satellite receiver. Setting spektrum_sat_bind to zero will disable the bind mode in any case. The bind mode will only be activated after an power on or hard reset. Please refer to the table below for the different possible values.
28+
29+
If the hardware bind plug is configured the bind mode will only be activated if the plug is set during the firmware start-up. The value of the spektrum_sat_bind parameter will be permanently preserved. The bind plug should be always removed for normal flying.
30+
31+
If no hardware bind plug is used the spektrum_sat_bind parameter will trigger the bind process during the next hardware reset and will be automatically reset to "0" after this.
32+
33+
Please refer to the satellite receiver documentation for more details of the specific receiver in bind mode. Usually the bind mode will be indicated with some flashing LEDs.
34+
35+
## Table with spektrum_sat_bind parameter value
36+
37+
| Value | Receiver mode | Notes |
38+
| ----- | ---------------| -------------------|
39+
| 3 | DSM2 1024/22ms | |
40+
| 5 | DSM2 2048/11ms | default AlienWii32 |
41+
| 7 | DSMX 22ms | |
42+
| 9 | DSMX 11ms | |
43+
44+
More detailed information regarding the satellite binding process can be found here:
45+
http://wiki.openpilot.org/display/Doc/Spektrum+Satellite
46+
47+
### Supported Hardware
48+
49+
NAZE, NAZE32PRO, CJMCU, SPARKY, EUSTM32F103RC, CC3D targets (AlienWii32 with hardware bind plug)

0 commit comments

Comments
 (0)