rusefi/firmware
rusefillc 98049d326c M62T vanos support #2243 2021-02-01 05:39:25 -05:00
..
ChibiOS@0b4897475a Chibi os 20 (#2212) 2021-01-19 15:20:35 -05:00
ChibiOS-Contrib@61baa6b036 Chibi os 20 (#2212) 2021-01-19 15:20:35 -05:00
bootloader -g3 to -g (#2256) 2021-01-31 14:13:55 -05:00
config Auto-generated configs and docs 2021-01-31 22:21:02 +00:00
console Limp handles inj/ign disable (#2245) 2021-01-27 21:28:53 -05:00
controllers Merge remote-tracking branch 'origin/master' into master 2021-02-01 00:25:43 -05:00
development gpio helper (#2195) 2021-01-08 20:01:26 -05:00
docs Migrate to newer ChibiOS #710 2021-01-10 12:30:10 -05:00
ext
ext_algo
hw_layer vvt/cam events to pass index 2021-01-31 22:24:45 -05:00
iar_egt
init Fix master fatal error (#2206) 2021-01-09 15:13:43 -05:00
integration M62T vanos support #2243 2021-02-01 05:39:25 -05:00
tunerstudio Auto-generated configs and docs 2021-01-31 22:21:02 +00:00
util Add fallback map table (#2248) 2021-01-31 17:19:06 -05:00
.cproject
.gitattributes
.gitignore
.project
CHANGELOG.md ### 2021 Printing Ink Day 2021-01-19 15:19:31 -05:00
Doxyfile
DoxygenLayout.xml
Makefile -g3 to -g (#2256) 2021-01-31 14:13:55 -05: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_reboot_dfu.bat
flash_release.bat
gen_config.bat
gen_config.sh Hellen72 config (#2200) 2021-01-08 12:50:13 -05:00
gen_config_board.bat
gen_config_board.sh New board pin-mapping system (#2231) 2021-01-22 12:03:14 -05:00
gen_config_default.sh
gen_enum_to_string.bat
gen_enum_to_string.sh
gen_firing_order.bat
gen_fsio_example.bat decompile_fsio_line 2020-12-12 10:40:55 -05:00
gen_fsio_example_reverse.bat decompile_fsio_line 2020-12-12 10:40:55 -05:00
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 clang warnings again #2055 2020-12-11 10:33:00 -05:00
globalaccess.h
kill_for_coverity.c
license.txt rusEFI is not approved for manned aircraft applications. 2020-12-16 12:58:34 -05:00
main.cpp
main_hardfault.c
make4.bat
os_access.h
readme.md
reboot_ecu.bat
run_hw_test.bat
rusefi.cpp IGNORE_FLASH_CONFIGURATION 2021-01-28 19:40:51 -05:00
rusefi.h
rusefi.mk
rusefi_rules.mk
svnversion.h poke 2021-01-07 08:59:33 -05:00
update_version.bat
update_version.sh

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.