rusefi-1/firmware
rusefi f7da86983a EFI_IDLE_INCREMENTAL_PID_CIC should be a runtime parameter #806 2020-07-12 21:13:04 -04:00
..
ChibiOS@1a2c5967dc
ChibiOS-Contrib@8f7c2d187b
bootloader trace global lock/unlock (#1582) 2020-07-10 23:27:27 -04:00
config Auto-generated configs and docs 2020-07-12 21:36:03 +00:00
console EFI_IDLE_INCREMENTAL_PID_CIC should be a runtime parameter #806 2020-07-12 18:11:10 -04:00
controllers EFI_IDLE_INCREMENTAL_PID_CIC should be a runtime parameter #806 2020-07-12 21:13:04 -04:00
development trace global lock/unlock (#1582) 2020-07-10 23:27:27 -04:00
docs
ext
ext_algo
hw_layer SD logging 2020-07-09 20:08:18 -04:00
iar_egt better file name 2020-05-25 13:02:05 -04:00
init better file name 2020-05-25 13:02:05 -04:00
integration EFI_IDLE_INCREMENTAL_PID_CIC should be a runtime parameter #806 2020-07-12 17:34:19 -04:00
tunerstudio Auto-generated configs and docs 2020-07-12 21:36:03 +00:00
util Stefan, I want to drink from the same fountain of patience 2020-07-12 15:00:44 -04:00
.cproject
.gitattributes is this the problem? 2020-06-16 14:19:40 -04:00
.gitignore
.project
Doxyfile
DoxygenLayout.xml
Makefile Makefile clean-up 2020-05-25 13:42:55 -04:00
build-notes.txt
clean.bat Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
clean.sh Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
clean_build.bat
clean_compile_two_versions.bat Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
clean_compile_two_versions.sh Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
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 Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
flash_erase407.bat Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
flash_erase407.sh Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
flash_erase767.bat
flash_openocd407.bat Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
flash_openocd407.sh Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
flash_openocd767.bat
flash_reboot_dfu.bat
flash_release.bat
gen_config.bat Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
gen_config.sh Fix kinetis (#1589) 2020-07-10 22:28:38 -04:00
gen_config_board.bat Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
gen_config_board.sh Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
gen_enum_to_string.bat Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
gen_enum_to_string.sh Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
gen_firing_order.bat
gen_fsio_example.bat
gen_live_documentation.bat Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
gen_live_documentation.sh Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
gen_ptrace_enums.bat
gen_signature.sh generated folder 2020-07-06 01:01:30 -04:00
gen_system_fsio.bat
gen_trigger_images.bat
generate_docs.bat
generate_memory_usage_report.bat
global.h nope, unit tests did not just fix themselves 2020-06-17 08:42:37 -04:00
globalaccess.h
kill_for_coverity.c
license.txt
main.cpp
main_hardfault.c
make4.bat
os_access.h
readme.md
reboot_ecu.bat
run_hw_test.bat
rusefi.cpp a few unneeded properties 2020-06-13 22:46:10 -04:00
rusefi.h
rusefi.mk
rusefi_rules.mk
svnversion.h poke 2020-07-11 22:38:22 -04:00
update_version.bat Switch to Bash (#1585) 2020-07-09 10:27:20 -04:00
update_version.sh Switch to Bash (#1585) 2020-07-09 10:27:20 -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.