a5f793a6bd
|
||
|---|---|---|
| .. | ||
| ChibiOS@d46398838e | ||
| ChibiOS-Contrib@63b50e410c | ||
| bootloader | ||
| config | ||
| console | ||
| controllers | ||
| development | ||
| docs | ||
| ext | ||
| ext_algo | ||
| hw_layer | ||
| init | ||
| integration | ||
| libfirmware@163cee4279 | ||
| pch | ||
| tunerstudio | ||
| util | ||
| .cproject | ||
| .gitattributes | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CHANGELOG.rusefi.md | ||
| Doxyfile | ||
| DoxygenLayout.xml | ||
| Makefile | ||
| check.c | ||
| common.mk | ||
| cov_config.bat | ||
| cov_run.bat | ||
| coverity.yml | ||
| egt2can.cpp | ||
| exception.txt | ||
| gen_config.bat | ||
| gen_config.sh | ||
| gen_config_board.bat | ||
| gen_config_board.sh | ||
| gen_config_common.sh | ||
| gen_config_default.sh | ||
| gen_default_everything.sh | ||
| gen_enum_to_string.bat | ||
| gen_enum_to_string.sh | ||
| gen_live_documentation.bat | ||
| gen_live_documentation.sh | ||
| gen_ptrace_enums.bat | ||
| gen_signature.sh | ||
| gen_trigger_images.bat | ||
| generate_docs.bat | ||
| get_performance_trace.bat | ||
| gitversion.mk | ||
| global.h | ||
| kill_for_coverity.c | ||
| main.cpp | ||
| provide_gcc.sh | ||
| readme.md | ||
| release.md | ||
| rusefi.cpp | ||
| rusefi.h | ||
| rusefi.mk | ||
| rusefi_pch.mk | ||
| rusefi_rules.mk | ||
| setup_linux_environment.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.