rusefi-1/firmware
GitHub set-date Action 8518b60740 Update date 2021-05-11 00:58:30 +00:00
..
ChibiOS@948b015c9c enable CAN on H7 (#2393) 2021-03-09 18:54:01 -05:00
ChibiOS-Contrib@fe3cdf8314 fresh 2021-04-15 00:43:19 -04:00
bootloader Revert "lua on f407 (#2646)" 2021-05-09 18:25:50 -04:00
config Auto-generated configs and docs 2021-05-10 12:32:55 +00:00
console remove deprecated getEngineLoadT (#2676) 2021-05-10 08:30:41 -04:00
controllers Update date 2021-05-11 00:58:30 +00:00
development Revert "lua on f407 (#2646)" 2021-05-09 18:25:50 -04:00
docs
ext lua 5.4 (#2590) 2021-04-28 22:41:25 -04:00
ext_algo
hw_layer no sd if early fatal (#2680) 2021-05-10 14:31:40 -04:00
iar_egt
init Maf in sensor model (#2672) 2021-05-09 20:59:06 -04:00
integration remove deprecated getEngineLoadT (#2676) 2021-05-10 08:30:41 -04:00
tunerstudio Auto-generated configs and docs 2021-05-10 12:32:55 +00:00
util remove intermediate buffer (#2668) 2021-05-10 08:01:24 -04:00
.cproject
.gitattributes
.gitignore
.project
CHANGELOG.md Support STM32F7 1MB devices #2659 2021-05-09 10:10:00 -04:00
Doxyfile
DoxygenLayout.xml
Makefile same line twice 2021-05-07 22:03:28 -04:00
build-notes.txt
clean.bat
clean.sh
clean_build.bat
clean_compile_two_versions.bat
clean_compile_two_versions.sh
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_dfu.sh
flash_erase407.bat
flash_erase407.sh
flash_erase767.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 code duplication between hellen boards #2611 2021-05-01 19:45:09 -04:00
gen_config_board.bat
gen_config_board.sh NA6 ini is not uploaded fix #2649 2021-05-07 19:18:43 -04:00
gen_config_default.sh
gen_enum_to_string.bat
gen_enum_to_string.sh
gen_firing_order.bat
gen_fsio_example.bat
gen_fsio_example_reverse.bat
gen_live_documentation.bat
gen_live_documentation.sh
gen_ptrace_enums.bat
gen_signature.sh
gen_system_fsio.bat
gen_trigger_images.bat
generate_docs.bat
generate_memory_usage_report.bat
get_performance_trace.bat
global.h
globalaccess.h
kill_for_coverity.c
license.txt
main.cpp version check (#2673) 2021-05-09 20:26:53 -04:00
main_hardfault.c
make4.bat
os_access.h
readme.md
reboot_ecu.bat
run_hw_test.bat
rusefi.cpp prep for lua (#2589) 2021-04-27 07:57:08 -04:00
rusefi.h
rusefi.mk
rusefi_rules.mk
setup_linux_environment.sh +x (#2492) 2021-03-25 17:16:25 -04:00
svnversion.h poke 2021-03-13 16:33:05 -05:00
update_version.bat
update_version.sh
version_check.h version check (#2673) 2021-05-09 20:26:53 -04:00

readme.md

Doxygen

Q&A on source code

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.