6f9ed5205d
|
||
|---|---|---|
| .. | ||
| .vscode | ||
| ChibiOS@85cf4582a9 | ||
| ChibiOS-Contrib@8f7c2d187b | ||
| bootloader | ||
| config | ||
| console | ||
| controllers | ||
| development | ||
| docs | ||
| ext | ||
| ext_algo | ||
| hw_layer | ||
| iar_egt | ||
| init | ||
| integration | ||
| tunerstudio | ||
| util | ||
| .cproject | ||
| .gitignore | ||
| .project | ||
| Doxyfile | ||
| DoxygenLayout.xml | ||
| Makefile | ||
| build-notes.txt | ||
| clean.bat | ||
| clean_build.bat | ||
| clean_compile_two_versions.bat | ||
| compile.bat | ||
| compile_and_program.bat | ||
| cov_config.bat | ||
| cov_run.bat | ||
| coverity.yml | ||
| dump.bat | ||
| dump_iar.bat | ||
| dump_release.bat | ||
| egt2can.cpp | ||
| exception.txt | ||
| flash.bat | ||
| flash_dfu.bat | ||
| flash_erase407.bat | ||
| flash_erase767.bat | ||
| flash_openocd407.bat | ||
| flash_openocd767.bat | ||
| flash_release.bat | ||
| gen_config.bat | ||
| gen_config2.bat | ||
| gen_config_board.bat | ||
| gen_enum_to_string.bat | ||
| gen_fsio_example.bat | ||
| gen_system_fsio.bat | ||
| gen_trigger_images.bat | ||
| generate_docs.bat | ||
| generate_memory_usage_report.bat | ||
| global.h | ||
| globalaccess.h | ||
| kill_for_coverity.c | ||
| license.txt | ||
| main.cpp | ||
| main_hardfault.c | ||
| make4.bat | ||
| os_access.h | ||
| readme.md | ||
| reboot_ecu.bat | ||
| rusefi.cpp | ||
| rusefi.h | ||
| rusefi.mk | ||
| svnversion.h | ||
| update_version.bat | ||
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.
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.
Expected Future Changes
The firmware build is moving toward a system that separates board features from processor features. This will require specifying both the board type and specific processor.
The existing system evolved based on the original RusEFI boards. Those used 'STM32 Discovery' development boards plugged into base boards that held the ECU-specific chips. That approach resulted in hard-coded assumption about pin assignments, and associations of hardware with a specific processor variant. That legacy is slowly being cleaned up, but is still evident in some settings and limitations.