FOME-Tech
/
fome-fw
mirror of https://github.com/FOME-Tech/fome-fw.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
10,049 Commits 30 Branches 13 Tags 626 MiB
Commit Graph

25 Commits

Author SHA1 Message Date
Matthew Kennedy 4703b4be6d guard perf track lock hooks (#1591) 
Co-authored-by: Matthew Kennedy <makenne@microsoft.com>
 2020-07-11 00:16:36 -04:00
Matthew Kennedy 1a0cad431b trace global lock/unlock (#1582) 
* trace global lock/unlock

* bootloader stub

* add to java

Co-authored-by: Matthew Kennedy <makenne@microsoft.com>
 2020-07-10 23:27:27 -04:00
Matthew Kennedy a2313a853c switch some firmware warnings to errors (#1465) 
* warnings as errors

* throw instead of exit

* test massaging

Co-authored-by: Matthew Kennedy <makenne@microsoft.com>
 2020-05-23 10:46:28 -04:00
rusefi e063aa492a build and board info into critical error message 2020-05-22 16:45:13 -04:00
rusefi a88b41a8d0 refactoring related to RED FATAL/CRITICAL LED is a bit dim when it should be OFF 
#157
 2020-05-11 18:22:51 -04:00
rusefi cfd8889236 class constructors are a great way to have simple initialization sequence 2020-05-03 10:58:52 -04:00
rusefi 6bf8e0deed different take on remove warning message in tune #1347 2020-04-22 19:07:42 -04:00
rusEfi 35ffb13ca4 TS to show warning text 2020-04-19 21:42:00 -04:00
rusefi 84e0e1b6e9 critical error usability improvements 2020-03-28 21:28:32 -04:00
rusefi 79e5059c5a critical error usability improvements 2020-03-28 20:14:17 -04:00
rusefi 4d617aa0fe random header clean-up 2020-03-23 09:00:57 -04:00
rusefi 63e3e84e08 happy new year 2020-01-08 00:02:40 -05:00
Matthew Kennedy 34ffe7f6b3 Make sure #798 is good and dead (#1028) 
* Revert "CI instability: FATAL error: warn stream not initialized for 6039 - maybe buffer overrun? #798"

This reverts commit 45646f23bd.

* Revert "CI instability: FATAL error: warn stream not initialized for 6039 #798"

This reverts commit 1f8176ac7e.

* fix correctly

* use correct function
 2019-11-23 21:25:29 -05:00
rusefi 1f8176ac7e CI instability: FATAL error: warn stream not initialized for 6039 #798 2019-11-23 17:07:13 -05:00
rusefi 45646f23bd CI instability: FATAL error: warn stream not initialized for 6039 - maybe buffer overrun? #798 2019-11-23 16:41:59 -05:00
rusefi d99d576e2b CI instability: FATAL error: warn stream not initialized fix #798 2019-11-03 22:15:49 -05:00
rusefi d4b9c7217e fatalErrorPin setting is not used #926 
reducing configuration fragility
 2019-09-09 21:44:48 -04:00
rusefi ef5a1447e9 CI instability: FATAL error: warn stream not initialized for 6039 
also some refactoring
fix #798
 2019-08-04 13:48:10 -04:00
rusefi 89557373e9 order of includes consistency 2019-07-05 20:03:32 -04:00
rusefi e309e223aa Refactoring: OS access should be explicit #867 2019-07-04 03:57:21 -04:00
rusefi 777eb532dc Refactoring: OS access should be explicit #867 2019-07-03 21:48:04 -04:00
rusefi f89c326579 todo 2019-05-10 22:10:40 -04:00
rusefi 8a90297160 refactoring: better method name 2019-05-07 19:32:08 -04:00
rusefi 884c54a185 defined(__DOXYGEN__) ? #748 2019-04-12 22:07:03 -04:00
rusefi 4011372da8 The Big Refactoring of 2019: folder structure #723 2019-04-09 23:17:09 -04:00