rusefi-1/firmware
rusefillc 5afed85479 We have working runtime RAM detection - we shall use it for Lua #3970 2022-03-27 19:39:40 -04:00
..
ChibiOS@8f0926be79 Catch up with Chibios 20.3 #2555 2022-01-15 21:04:34 -05:00
ChibiOS-Contrib@63b50e410c pointing at offical eeprom fix 2022-02-08 10:44:37 -05:00
bootloader more copy-pasta :( 2022-02-06 22:00:49 -05:00
config Auto-generated configs and docs 2022-03-27 22:53:50 +00:00
console We have working runtime RAM detection - we shall use it for Lua #3970 2022-03-27 19:39:40 -04:00
controllers Auto-generated configs and docs 2022-03-27 22:53:50 +00:00
development migrating to SensorType::Rpm API 2022-01-20 22:38:08 -05:00
docs
ext MMC reads rtc (#3945) 2022-02-18 19:35:28 -05:00
ext_algo
hw_layer We have working runtime RAM detection - we shall use it for Lua #3970 2022-03-27 19:39:40 -04:00
init aux linear sensors (#4005) 2022-03-20 20:13:04 -04:00
integration output channel tweaks (#4023) 2022-03-24 08:58:55 -04:00
pch
tunerstudio Auto-generated configs and docs 2022-03-27 22:53:50 +00:00
util output channel tweaks (#4023) 2022-03-24 08:58:55 -04:00
.cproject
.gitattributes
.gitignore
.project
CHANGELOG.md new VVT trigger shape? 4-1 Toyota fix #1847 2022-03-23 19:47:10 -04:00
Doxyfile
DoxygenLayout.xml
Makefile we have other places to set these MCU values (#3875) 2022-02-01 18:18:16 -05:00
build-notes.txt
check.c
clean.bat
clean.sh
clean_build.bat
clean_compile_two_versions.bat
clean_compile_two_versions.sh
common.mk
compile.bat
compile_and_program.bat
cov_config.bat
cov_run.bat
coverity.yml
dump.bat
dump_release.bat
egt2can.cpp
exception.txt
flash.bat
flash_can.sh typo, header, +x (#3951) 2022-02-20 08:40:10 -05:00
flash_dfu.bat why does this not work? sad face 2022-03-27 18:45:39 -04:00
flash_dfu.sh UPS: no need to define load addr for dfu file (#3800) 2022-01-17 16:38:23 -05:00
flash_dfu_erase.sh typo, header, +x (#3951) 2022-02-20 08:40:10 -05:00
flash_dfu_openblt_only.sh typo, header, +x (#3951) 2022-02-20 08:40:10 -05:00
flash_erase407.bat
flash_erase407.sh
flash_erase767.bat
flash_erase_dfu.bat
flash_openocd407.bat
flash_openocd407.sh
flash_openocd767.bat
flash_openocd_h7.bat
flash_reboot_dfu.bat why does this not work? sad face 2022-03-27 18:45:39 -04:00
flash_release.bat
gen_config.bat
gen_config.sh core8 2022-02-10 19:53:25 -05:00
gen_config_board.bat
gen_config_board.sh
gen_config_common.sh +x 2022-02-21 11:29:46 -05:00
gen_config_default.sh
gen_enum_to_string.bat
gen_enum_to_string.sh
gen_live_documentation.bat
gen_live_documentation.sh
gen_output_channels.sh
gen_ptrace_enums.bat
gen_signature.sh
gen_trigger_images.bat
generate_docs.bat
generate_memory_usage_report.bat
generate_memory_usage_report.sh +x 2022-02-21 11:29:46 -05:00
get_performance_trace.bat
global.h
globalaccess.h
kill_for_coverity.c
license.txt
main.cpp
main_hardfault.c
make4.bat
openblt.mk OpentBLT: fix for STM32F4/H7 (#3796) 2022-01-16 15:24:23 -05:00
os_access.h
readme.md
reboot_dfu.sh reboot_dfu 2022-03-17 21:55:19 -04:00
reboot_ecu.bat
run_hw_test.bat
rusefi.cpp migrating to SensorType::Rpm API 2022-01-20 22:22:52 -05:00
rusefi.h
rusefi.mk User board-specific terms in error messages #3886 2022-02-03 14:27:47 -05:00
rusefi_pch.mk
rusefi_rules.mk
send_command.bat
setup_linux_environment.sh docs 2022-02-12 09:56:59 -05:00
svnversion.h Update date 2022-03-27 00:19:30 +00:00
update_version.bat
update_version.sh invoke update_version.sh while updating date because why not 2022-01-31 00:17:07 -05: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.

See setup_linux_environment.sh

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.