529fd4128c
* exti default * s * skip late events * there are more hellens now * oof * science * kick * kick * I do not understand how computers * science * science * no workflows to speed loop * use existing subtraction * extract function because I don't understand computers * well, let's just dump the stack nearby * is flipped condition still broken? * different behavior * what if we don't optimize * mass storage overflows * ok fine optimize a little bit * we are just unable to print 64b apparently * angry integers * track which wheel/value was last * signal instead of both * try a queue * Revert "no workflows to speed loop" This reverts commit 0637a7d7ab39a3fb2af1a01eef6123b7269559a4. * s * print new timestamp too * don't overrun the error buffer * try to see where the event came from * s * does it help if we abort while self stim is enabled? * do it in hwHandle * what if we disable the pins * include * run with the safeties off in the name of science * s * d * fix configs * s * s * remove duct tape * put the test back too.... Co-authored-by: Matthew Kennedy <makenne@microsoft.com> |
||
---|---|---|
.. | ||
ChibiOS@8f0926be79 | ||
ChibiOS-Contrib@63b50e410c | ||
bootloader | ||
config | ||
console | ||
controllers | ||
development | ||
docs | ||
ext | ||
ext_algo | ||
hw_layer | ||
init | ||
integration | ||
pch | ||
tunerstudio | ||
util | ||
.cproject | ||
.gitattributes | ||
.gitignore | ||
.project | ||
CHANGELOG.md | ||
Doxyfile | ||
DoxygenLayout.xml | ||
Makefile | ||
build-notes.txt | ||
check.c | ||
clean.bat | ||
clean.sh | ||
clean_build.bat | ||
clean_compile_two_versions.bat | ||
clean_compile_two_versions.sh | ||
common.mk | ||
compile.bat | ||
compile_and_program.bat | ||
cov_config.bat | ||
cov_run.bat | ||
coverity.yml | ||
dump.bat | ||
dump_release.bat | ||
egt2can.cpp | ||
exception.txt | ||
flash.bat | ||
flash_can.sh | ||
flash_dfu.bat | ||
flash_dfu.sh | ||
flash_dfu_bin.bat | ||
flash_dfu_erase.sh | ||
flash_dfu_openblt_only.sh | ||
flash_erase407.bat | ||
flash_erase407.sh | ||
flash_erase767.bat | ||
flash_erase_dfu.bat | ||
flash_openocd407.bat | ||
flash_openocd407.sh | ||
flash_openocd767.bat | ||
flash_openocd_h7.bat | ||
flash_reboot_dfu.bat | ||
flash_release.bat | ||
gen_config.bat | ||
gen_config.sh | ||
gen_config_board.bat | ||
gen_config_board.sh | ||
gen_config_common.sh | ||
gen_config_default.sh | ||
gen_enum_to_string.bat | ||
gen_enum_to_string.sh | ||
gen_live_documentation.bat | ||
gen_live_documentation.sh | ||
gen_output_channels.sh | ||
gen_ptrace_enums.bat | ||
gen_signature.sh | ||
gen_trigger_images.bat | ||
generate_docs.bat | ||
generate_memory_usage_report.bat | ||
generate_memory_usage_report.sh | ||
get_performance_trace.bat | ||
global.h | ||
globalaccess.h | ||
kill_for_coverity.c | ||
license.txt | ||
main.cpp | ||
main_hardfault.c | ||
make4.bat | ||
os_access.h | ||
readme.md | ||
reboot_dfu.sh | ||
reboot_ecu.bat | ||
run_hw_test.bat | ||
rusefi.cpp | ||
rusefi.h | ||
rusefi.mk | ||
rusefi_pch.mk | ||
rusefi_rules.mk | ||
send_command.bat | ||
setup_linux_environment.sh | ||
svnversion.h | ||
update_version.bat | ||
update_version.sh |
readme.md
See also ../unit_tests
This directory contains the source code for the RusEFI firmware.
The ideal is that typical end users should be able to use pre-built firmware. They should not need to modify or even rebuild from the source code for basic use, but building from the source code provides the opportunity for optimization, supporting unexpected engine configurations, and specialized enhancements.
TL;DR
make PROJECT_BOARD=microrusefi PROJECT_CPU=ARCH_STM32F4
Environment
Rebuilding from source code requires this firmware, a modern C/C++ compiler for embedded ARM systems, and a platform that supports 'make' based builds.
See setup_linux_environment.sh
While many compilers have the potential to work, we suggest using the official ARM version of GCC available at launchpad.net.
Linux and MacOS systems should have the software development tools, primarily 'make', pre-installed or readily installed. MS-Windows requires selecting and installing a Unix-compatible system environment.
Note that the developers are volunteers, with varied motivations. These motivations often include using leading-edge language and build system concepts, requiring recent versions of tools. Should you encounter build problems, review the latest version of this document.