Merge branch 'master' of https://github.com/rusefi/rusefi

README.md

@@ -22,6 +22,7 @@ Important note - we now use submodules:
  * [Unit Tests](/unit_tests) Unit tests of firmware pieces
  * [Misc tools](/java_tools) Misc development utilities
  * [misc/Jenkins](/misc/jenkins) Jenkins Continues Integration scripts
+ * [Software Development process](misc/SoftwareDevelopmentProcess.md)
  * [Work in progress status](work_in_progress.md)
 
 # External Links

firmware/bootloader/src/rusefi_stubs.cpp

@@ -31,6 +31,8 @@ LoggingWithStorage::LoggingWithStorage(const char *name) : Logging(name, DEFAULT
 
 // this is supposed to be taken from chconf_common.h but it does not work? I am not sure why :(
 // TODO: make this be defined by chconf_common.h?
-void irqEnterHook() {}
-void irqExitHook() {}
-void contextSwitchHook() {}
+#if ! ENABLE_PERF_TRACE
+//void irqEnterHook() {}
+//void irqExitHook() {}
+//void contextSwitchHook() {}
+#endif /* ENABLE_PERF_TRACE */

firmware/config/stm32f4ems/chconf.h

@@ -52,7 +52,7 @@
 
 #if !defined(ENABLE_PERF_TRACE) || defined(__DOXYGEN__)
 // looks like this value could not be defined in efifeatures.h - please define either externally or just change the value here
- #define ENABLE_PERF_TRACE TRUE
+ #define ENABLE_PERF_TRACE FALSE
 #endif /* ENABLE_PERF_TRACE */
 
 #include "chconf_common.h"

misc/SoftwareDevelopmentProcess.md

@@ -0,0 +1,20 @@
+
+
+rusEfi firmware development model is "stable master". We do not have release branches, we only have master with 
+continues integration and *limited* automated testing.
+
+By default, each Pull Request is expected to be complete and expected to not break existing functionality.
+If a Pull Request is a work-in-progress or draft or not intended for merge yet, it should be clearly marked with "[WIP]" prefix in the title.
+
+Pull Requests which are not complete, not marked WIP or fail gate check should be closed to reduce a chance of confusion.
+It is usually helpful to discuss proposed changes prior to Pull Requests - we have Slack to collaborate and coordinate so let's use!
+
+
+
+TODO: we have an urgent need to make gate check more reliable & expand what's included into gate check
+
+The primary hardware platform for rusEfi is stm32f4 - as of November 2019, only stm32f4 has hardware test continues integration.
+
+    
+
+See also [Functional tests CI info](jenkins/functional_test_and_build_bundle/readme.md)

misc/jenkins/functional_test_and_build_bundle/readme.md

@@ -1,3 +1,8 @@
 
+This configuration
+1) builds bootloader from firmware/bootload just to validate that it builds (TODO: extract to separate job?)
+1) compiles two versions of F4 version of firmware - with and without asserts, _fast_ and _debug_.
+1) flashes _debug_ version of F4 into stm32f4discovery and runs a suite of tests against it. The source code
+of tests is embedded into rusEfi console by the way (TODO: nicer UI for console to test F4 outside of Jenkins?)
 
 ```misc/jenkins/functional_test_and_build_bundle/run.bat```

work_in_progress.md

@@ -1,3 +1,7 @@
+Nov, 19 2019 status:
+* top priority is https://github.com/rusefi/rusefi/issues/1011 Fix and expand commit gate check
+* [DONE] https://github.com/rusefi/rusefi/issues/796 Missing dwell altogether in some corner cases still should be addressed
+
 Sep, 19 2019 status:
 * https://github.com/rusefi/rusefi/issues/796 Missing dwell altogether in some corner cases still should be addressed
 * Ion Sense https://rusefi.com/forum/viewtopic.php?f=4&t=963 is now somewhere on top of the list!