Merging all recent commits

.gitattributes

@@ -1,13 +1,30 @@
-*.md text
-*.c text
-*.h text
-*.cc text
-*.S text
-*.s text
+LICENSE text eol=lf
+*.md text eol=lf
+*.c text eol=lf
+*.cc text eol=lf
+*.h text eol=lf
+*.cc text eol=lf
+*.S text eol=lf
+*.s text eol=lf
 *.hex -crlf -diff
 *.elf -crlf -diff
-*.ld text
-Makefile text
-*.bat eol=crlf
-*.txt text
-*.sh text
+*.ld text eol=lf
+Makefile text eol=lf
+*.mk text eol=lf
+*.nomk text eol=lf
+*.pl text eol=lf
+*.js text eol=lf
+*.json text eol=lf
+*.html text eol=lf
+*.css text eol=lf
+*.svg text eol=lf
+*.png -crlf -diff
+*.yml text eol=lf
+*.xml text eol=lf
+*.mcm text eol=lf
+*.nsi text eol=lf
+*.nsh text eol=lf
+*.lua text eol=lf
+*.txt text eol=lf
+*.sh text eol=lf
+*.config text eol=lf

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+custom: https://www.paypal.me/mrcleanflight
+patreon: cleanflight
+github: [hydra]

.github/ISSUE_TEMPLATE/configuration-issue.md

@@ -0,0 +1,9 @@
+---
+name: Configuration Issue
+about: Find help if you are struggling with configuring Cleanflight
+
+---
+
+**Important: This is not the right place to get help with configuration issues. Your issue will be closed without further comment.**
+
+Please get help from other user support options such as asking the manufacturer of the hardware you are using, RCGroups: https://www.rcgroups.com/forums/showthread.php?2249574, or Slack (registration at http://cleanflight.com/slack/) or other user support forums & groups (e.g. Facebook).

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,19 @@
+---
+name: Feature Request
+about: Suggest an idea for for a new feature
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+
+Please note that feature requests are not 'fire and forget'. It is a lot more likely that the feature you would like to have will be implemented if you keep watching your feature request, and provide more details to developers looking into implementing your feature, and help them with testing.

.github/ISSUE_TEMPLATE/firmware-bug-report.md

@@ -0,0 +1,29 @@
+---
+name: Firmware Bug Report
+about: Create a report to help us fix bugs in the firmware
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Flight controller configuration**
+Create a `diff` and post it here in a code block. Put ``` (three backticks) at the start and end of the `diff` block.
+
+To create a `diff` go to the CLI in the configurator, type in `diff` and press enter, then save the result to a file.
+
+Use `resource show all` to create a resource allocation list and post it here in a code block. Put ``` (three backticks) at the start and end of the output block.
+
+**Setup / Versions**
+ - Flight controller [what type is it, where was it bought from];
+ - Other components [RX, VTX, brand / model for all of them, firmware version where applicable];
+ - how are the different components wired up.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/hardware-problem-report.md

@@ -0,0 +1,9 @@
+---
+name: Hardware Problem Report
+about: Report problems with faulty / broken hardware
+
+---
+
+**Important: This is not the right place to report faulty / broken hardware. Your issue will be closed without further comment.**
+
+Contact the manufacturer or supplier of your hardware, or check RCGroups https://rcgroups.com/forums/showthread.php?t=2464844 to see if others with the same problem have found a solution.

.github/issue_template.md

@@ -1,45 +1,13 @@
 # 1. ARE YOU REQUESTING SUPPORT?
 
--- YES / NO --
-
-# 2. If you answered YES to the above question go here instead:
-
-https://www.rcgroups.com/forums/showthread.php?2249574-Cleanflight-firmware-for-STM32F3-based-FCBs-Check-First-Post-Please%21%21
-
-Alternatively use other forums, slack or IRC for support.
-
-# 3. If you answered NO to the first question.  Delete everything above this line, read the guidelines (see link above this form) and continue.
-
-# A - Description
-
--- replace this line with a summary of the issue/problem/feature
-
-# B - Steps To Repeat
-
--- replace this line with a list of steps to repeat your problem
-
-# C - Video Links
-
--- provide a link to a video showing your problem, as applicable --
-
-# D - Forum post links
-
--- provide links to forum posts if you have discussed this with others --
-
-# E - Version Information
-
-Cleanflight: vX.X.X or commit SHA
-Configurator: vX.X.X or commit SHA
-
-# E - Other information
-
--- provide additional information such as.
--- flight controller make/model
--- config dump + diff
--- esc make/model/config
--- receiver make/model/config
--- transmitter make/model/config
--- schematics
--- diagrams
--- operating system
--- etc.
+## Please consider using other user support options such as asking the manufacturer of the hardware you are using, RCGroups: https://rcgroups.com/forums/showthread.php?2249574, or Slack (registration at http://cleanflight.com/slack/) or other user support forums & groups (e.g. Facebook).
+
+## If you believe there is an issue with the firmware itself please follow these steps:
+1. Describe your problem;
+2. Include ways to reproduce the problem;
+3. Provide as much information as possible about your hardware and software, including:
+- what hardware / software you are using;
+- the version of all the software used;
+- how things are connected / wired up.
+4. Create a `diff` and post it here in a code block. Put ``` (three backticks) at the start and end of the `diff` block;
+5. Remove this Text :).

.github/no-response.yml

@@ -0,0 +1,12 @@
+# Configuration for probot-no-response - https://github.com/probot/no-response
+
+# Number of days of inactivity before an Issue is closed for lack of response
+daysUntilClose: 1
+# Label requiring a response
+responseRequiredLabel: Missing Information
+# Comment to post when closing an Issue for lack of response. Set to `false` to disable
+closeComment: >
+  This issue has been automatically closed because the information we asked
+  to be provided when opening it was not supplied by the original author.
+  With only the information that is currently in the issue, we don't have
+  enough information to take action.

.github/pull_request_template.md

@@ -1,9 +1,23 @@
-## Important considerations when opening a pull request:
+## Read this before opening a pull request:
 
-1.) Pull requests will only be accepted if they are opened against the `master` branch. Pull requests opened against other branches without prior consent from the maintainers will be closed;
+1. Make sure you do not make the changes you want to open a pull request for on the `master` branch of your fork, or open the pull request from the `master` branch of your fork. Some of our integrations will fail if you do this, resulting in your pull request not being accepted. If this is your first pull request, it is probably a good idea to first read up on how opening pull requests work (https://opensource.com/article/19/7/create-pull-request-github is a good introduction);
 
-2.) Please follow the coding style guidlines: https://github.com/cleanflight/cleanflight/blob/master/docs/development/CodingStyle.md
+2. Pull requests will only be accepted if they are opened against the `master` branch of our repository. Pull requests opened against other branches without prior consent from the maintainers will be closed;
 
-3.) If your pull request is a fix for one or more issues that are open in GitHub, add their numbers in the form `Fixes #<issue number>`. This will cause the issues to be closed when the pull request is merged;
+3. Please follow the coding style guidelines: https://github.com/cleanflight/cleanflight/blob/master/docs/development/CodingStyle.md
 
-4.) Remove this Text :).
+4. Keep your pull requests as small and concise as possible. One pull request should only ever add / update one feature. If the change that you are proposing has a wider scope, consider splitting it over multiple pull requests. In particular, pull requests that combine changes to features and one or more new targets are not acceptable.
+
+5. Ideally, a pull request should contain only one commit, with a descriptive message. If your changes use more than one commit, rebase / squash them into one commit before submitting a pull request. If you need to amend your pull request, make sure that the additional commit has a descriptive message, or - even better - use `git commit --amend` to amend your original commit.
+
+6. All pull requests are reviewed. Be ready to receive constructive criticism, and to learn and improve your coding style. Also, be ready to clarify anything that isn't already sufficiently explained in the code and text of the pull request, and to defend your ideas.
+
+7. If your pull request is for a new target or an update to an existing target, please be aware that all targets have to be submitted as Unified Target configurations if a Unified Target for the MCU type is available. Read and follow [these instructions](https://github.com/cleanflight/cleanflight/blob/master/docs/TargetMaintenance/CreatingAUnifiedTarget.md).
+
+8. We use continuous integration (CI) with [Travis](https://travis-ci.com/cleanflight) to build all targets and run the test suite for every pull request. Pull requests that fail any of the builds or fail tests will most likely not be reviewed before they are fixed to build successfully and pass the tests. In order to get a quick idea if there are things that need fixing **before** opening a pull request or pushing an update into an existing pull request, run `make pre-push` to run a representative subset of the CI build. _Note: This is not an exhaustive test (which will take hours to run on any desktop type system), so even if this passes the CI build might still fail._
+
+9. If your pull request is a fix for one or more issues that are open in GitHub, add a comment to your pull request, and add the issue numbers of the issues that are fixed in the form `Fixes #<issue number>`. This will cause the issues to be closed when the pull request is merged;
+
+10. If your pull request contains a change that can be tested by other users, please build a set of test firmware files for all Unified Targets and attach them to the pull request. The required firmware files can be built in zipped form ready for upload to GitHub with `make unified_zip`. When attaching test firmware files, you can point users to this video for instructions on how to install the test firmware: https://youtu.be/I1uN9CN30gw
+
+11. Remove this Text :).

.github/stale.yml

@@ -0,0 +1,57 @@
+# Configuration for probot-stale - https://github.com/probot/stale
+
+# Number of days of inactivity before an Issue or Pull Request becomes stale
+daysUntilStale: 30
+
+# Number of days of inactivity before a stale Issue or Pull Request is closed.
+# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+daysUntilClose: 7
+
+# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+exemptLabels:
+  - BUG
+  - Feature Request
+  - Pinned
+  - Idea
+  - Task
+
+# Set to true to ignore issues in a project (defaults to false)
+exemptProjects: false
+
+# Set to true to ignore issues in a milestone (defaults to false)
+exemptMilestones: true
+
+# Label to use when marking as stale
+staleLabel: Inactive
+
+# Comment to post when marking as stale. Set to `false` to disable
+markComment: >
+  This issue / pull request has been automatically marked as stale because it
+  has not had recent activity. It will be closed if no further activity occurs
+  within a week.
+
+# Comment to post when removing the stale label.
+# unmarkComment: >
+#   Your comment here.
+
+# Comment to post when closing a stale Issue or Pull Request.
+closeComment: >
+  Automatically closing as inactive.
+
+# Limit the number of actions per hour, from 1-30. Default is 30
+limitPerRun: 30
+
+# Limit to only `issues` or `pulls`
+# only: issues
+
+# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
+# pulls:
+#   daysUntilStale: 30
+#   markComment: >
+#     This pull request has been automatically marked as stale because it has not had
+#     recent activity. It will be closed if no further activity occurs. Thank you
+#     for your contributions.
+
+# issues:
+#   exemptLabels:
+#     - confirmed

.gitignore

@@ -34,6 +34,9 @@ stm32.mak
 # eclipse launch configurations
 /support/eclipse
 
+# ozone launch configurations
+/support/ozone
+
 # artefacts for Visual Studio Code
 /.vscode/
 
@@ -43,3 +46,7 @@ stm32.mak
 
 .vagrant
 ubuntu*.log
+/.vs
+
+# EEPROM image file (created by SITL)
+eeprom.bin

.travis.sh

@@ -10,7 +10,7 @@ TRAVIS_REPO_SLUG=${TRAVIS_REPO_SLUG:=$USER/undefined}
 BUILDNAME=${BUILDNAME:=travis}
 TRAVIS_BUILD_NUMBER=${TRAVIS_BUILD_NUMBER:=undefined}
 
-MAKE="make EXTRA_FLAGS=-Werror V=0"
+MAKE="make EXTRA_FLAGS=-Werror"
 
 CURL_BASEOPTS=(
 	"--retry" "10"
@@ -66,16 +66,22 @@ elif [ $TARGET ] ; then
 	fi
 
 elif [ $GOAL ] ; then
+    if [ "test-all" == "$GOAL" ] ; then
+        $MAKE checks || exit $?
+    else
+	 export V=0
+    fi
+
     $MAKE $GOAL || exit $?
 
-  if [ $PUBLISHCOV ] ; then
-    if [ "test" == "$GOAL" ] ; then
-        lcov --directory . -b src/test --capture --output-file coverage.info 2>&1 | grep -E ":version '402\*', prefer.*'406\*" --invert-match
-        lcov --remove coverage.info 'lib/test/*' 'src/test/*' '/usr/*' --output-file coverage.info # filter out system and test code
-        lcov --list coverage.info # debug before upload
-        coveralls-lcov coverage.info # uploads to coveralls
+    if [ $PUBLISHCOV ] ; then
+        if [ "test-all" == "$GOAL" ] ; then
+            lcov --directory . -b src/test --capture --output-file coverage.info 2>&1 | grep -E ":version '402\*', prefer.*'406\*" --invert-match
+            lcov --remove coverage.info 'lib/test/*' 'src/test/*' '/usr/*' --output-file coverage.info # filter out system and test code
+            lcov --list coverage.info # debug before upload
+            coveralls-lcov coverage.info # uploads to coveralls
+        fi
     fi
-  fi
 else
     $MAKE all
 fi