rusefi/firmware
rusefillc 65dcdb86ec Too many bench test buttons are broken #5327 2023-06-15 11:46:39 -04:00
..
ChibiOS@e175c3781b only: fresh Chibi 2023-06-04 19:26:42 -04:00
ChibiOS-Contrib@63b50e410c
bootloader rename obd_code_e -> ObdCode 2023-04-29 00:44:00 -04:00
config Auto-generated configs and docs 2023-06-15 04:59:25 +00:00
console reducing magic constant 2023-06-12 20:07:48 -04:00
controllers Too many bench test buttons are broken #5327 2023-06-15 11:46:39 -04:00
development
docs enable LSE (via: LSE max wait patches) (#4944) 2023-02-12 16:01:03 -05:00
ext
ext_algo
hw_layer CJ125 is dead 2023-06-14 08:50:51 -04:00
init semi-secret brz/frs pedal mode 2023-06-11 20:30:44 -04:00
integration Dashpot for return-to-idle from coasting fix #5303 2023-06-15 00:57:28 -04:00
libfirmware@163cee4279
pch tooth_logger.h -> pch 2023-05-31 15:59:02 -04:00
tunerstudio Auto-generated configs and docs 2023-06-15 04:59:25 +00:00
util console "spark 1" bench hands up proteus #5320 2023-06-11 23:23:17 -04:00
.cproject
.gitattributes
.gitignore
.project
CHANGELOG.md Dashpot for return-to-idle from coasting #5303 2023-06-13 22:44:07 -04:00
Doxyfile
DoxygenLayout.xml
Makefile
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_bin.bat
flash_can.sh
flash_dfu.bat
flash_dfu.sh
flash_dfu_bin.bat
flash_dfu_erase.sh
flash_dfu_openblt_only.sh
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
flash_release.bat
gen_config.bat
gen_config.sh small can board 2023-06-06 20:41:59 -04:00
gen_config_board.bat
gen_config_board.sh
gen_config_common.sh
gen_config_default.sh
gen_default_everything.sh
gen_enum_to_string.bat
gen_enum_to_string.sh
gen_live_documentation.bat
gen_live_documentation.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
get_performance_trace.bat
global.h reducing code duplication 2023-06-11 23:36:38 -04:00
kill_for_coverity.c
license.txt
main.cpp
main_hardfault.c
main_hardfault_asm.S
make4.bat
provide_gcc.sh echo 2023-06-08 17:54:09 -04:00
readme.md
reboot_dfu.sh
reboot_ecu.bat
run_hw_test.bat
rusefi.cpp conditional EFI_DFU_JUMP 2023-05-24 09:58:22 -04:00
rusefi.h
rusefi.mk PROJECT_CPU did not work maybe because command line argument value could not be changed? 2023-05-23 17:58:47 -04:00
rusefi_pch.mk only: Cleaning-BLT into 'make clean' 2023-06-04 19:25:49 -04:00
rusefi_rules.mk
send_command.bat
setup_linux_environment.sh add missing dependencies for tests/sim builds (#4860) 2022-12-01 07:06:48 -05:00
svnversion.h
update_version.bat
update_version.sh

readme.md

Doxygen <<< landing page has best implementation introduction.

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.