rusefi/firmware
rusefi 1012df4511 progress towards start/stop 2020-03-18 16:32:03 -04:00
..
.vscode
ChibiOS@85cf4582a9
ChibiOS-Contrib@8f7c2d187b
bootloader bootloader ci (#1189) 2020-03-13 22:12:52 -04:00
config progress towards start/stop 2020-03-18 15:56:17 -04:00
console In case of incompatible firmware and console we have a vague error message fix #1180 2020-03-10 19:12:37 -04:00
controllers progress towards start/stop 2020-03-18 16:32:03 -04:00
development fix icu trigger polarity (#1177) 2020-03-08 08:57:21 -04:00
docs
ext
ext_algo
hw_layer proteus-f4 was requested 2020-03-18 11:37:53 -04:00
iar_egt
init warnings (#1169) 2020-03-03 08:37:02 -05:00
integration progress towards start/stop 2020-03-18 15:56:17 -04:00
tunerstudio progress towards start/stop 2020-03-18 15:56:17 -04:00
util split out scaled channel header (#1156) 2020-02-24 16:47:10 -05:00
.cproject
.gitignore
.project
Doxyfile
DoxygenLayout.xml
Makefile proteus-f4 was requested 2020-03-18 11:37:53 -04:00
build-notes.txt
clean.bat
clean_build.bat
clean_compile_two_versions.bat Remove chibios trace flag (#1037) 2019-12-02 19:11:07 -05: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 notes to self 2019-12-16 01:47:34 -05:00
flash_dfu.sh A Unix shell script matching the functionality flash_dfu.bat 2019-11-11 20:25:55 -05:00
flash_erase407.bat
flash_erase767.bat
flash_openocd407.bat
flash_openocd767.bat
flash_release.bat
gen_config.bat more Proteus CI 2020-02-02 08:42:05 -05:00
gen_config.sh scripts: add gen_config, gen_config_board and gen_enum_to_string for Linux (#1081) 2020-01-02 18:58:28 -05:00
gen_config_board.bat
gen_config_board.sh scripts: add gen_config, gen_config_board and gen_enum_to_string for Linux (#1081) 2020-01-02 18:58:28 -05:00
gen_enum_to_string.bat
gen_enum_to_string.sh scripts: add gen_config, gen_config_board and gen_enum_to_string for Linux (#1081) 2020-01-02 18:58:28 -05:00
gen_firing_order.bat firing order tool integration 2019-11-24 23:49:05 -05:00
gen_fsio_example.bat
gen_live_documentation.bat better script name 2020-02-22 15:38:21 -05:00
gen_ptrace_enums.bat PerfTraceTool 2019-11-25 00:57:36 -05:00
gen_system_fsio.bat
gen_trigger_images.bat
generate_docs.bat
generate_memory_usage_report.bat
global.h Dont cache dma buffers (#1110) 2020-01-29 00:32:43 -05:00
globalaccess.h happy new year 2020-01-08 00:02:40 -05:00
kill_for_coverity.c
license.txt
main.cpp happy new year unification 2020-01-13 21:57:43 -05:00
main_hardfault.c
make4.bat
os_access.h happy new year 2020-01-08 00:02:40 -05:00
readme.md
reboot_ecu.bat
run_hw_test.bat docs :( 2019-12-21 19:50:16 -05:00
rusefi.cpp happy new year unification 2020-01-13 21:57:43 -05:00
rusefi.h code style 2020-01-26 13:58:47 -05:00
rusefi.mk remove (#1188) 2020-03-13 17:19:29 -04:00
rusefi_rules.mk Fix master (#1134) 2020-02-08 16:34:29 -05:00
svnversion.h poke CI 2020-02-21 19:50:43 -05:00
update_version.bat

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.