fome-fw/firmware
Matthew Kennedy 71b40786ab status LED UI is dead! #35 2023-06-05 00:13:45 -07:00
..
ChibiOS@d46398838e
ChibiOS-Contrib@63b50e410c
bootloader
config include dirs 2023-06-05 00:06:08 -07:00
console remove config lookup entirely 2023-06-05 00:11:06 -07:00
controllers f407 disco 2023-06-04 23:53:58 -07:00
development get rid of FrontDirection too #55 2023-05-31 10:24:36 -07:00
docs
ext
ext_algo
hw_layer tooth_logger.h -> pch 2023-05-30 22:41:20 -07:00
init obd sensors very broken 2023-06-01 14:08:13 -07:00
integration status LED UI is dead! #35 2023-06-05 00:13:45 -07:00
libfirmware@163cee4279
pch tooth_logger.h -> pch 2023-05-30 22:41:20 -07:00
tunerstudio status LED UI is dead! #35 2023-06-05 00:13:45 -07:00
util
.cproject
.gitattributes
.gitignore
CHANGELOG.md log per-cylinder timing #76 2023-05-31 11:38:06 -07:00
CHANGELOG.rusefi.md
Doxyfile
DoxygenLayout.xml
Makefile
check.c
common.mk
cov_config.bat
cov_run.bat
coverity.yml
egt2can.cpp
exception.txt
gen_config.bat
gen_config.sh
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 x 2023-05-30 22:14:10 -07:00
gen_live_documentation.bat
gen_live_documentation.sh
gen_ptrace_enums.bat
gen_signature.sh
gen_trigger_images.bat
generate_docs.bat
get_performance_trace.bat
gitversion.mk
global.h
kill_for_coverity.c
main.cpp
main_hardfault.c
main_hardfault_asm.S
provide_gcc.sh
readme.md
release.md
rusefi.cpp
rusefi.h
rusefi.mk
rusefi_pch.mk
rusefi_rules.mk
setup_linux_environment.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.

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.