rusefi/firmware
rusefillc 8745be3213 progress? 2021-05-20 19:06:50 -04:00
..
ChibiOS@948b015c9c enable CAN on H7 (#2393) 2021-03-09 18:54:01 -05:00
ChibiOS-Contrib@fe3cdf8314 fresh 2021-04-15 00:43:19 -04:00
bootloader Lua on f407, try again (#2725) 2021-05-20 23:05:18 +03:00
config progress? 2021-05-20 19:06:50 -04:00
console make the simulator usable (#2717) 2021-05-17 12:44:02 +03:00
controllers lua pwm hooks (#2687) 2021-05-20 19:01:17 -04:00
development Lua on f407, try again (#2725) 2021-05-20 23:05:18 +03:00
docs
ext don't build OS lib (#2700) 2021-05-17 08:38:30 +03:00
ext_algo
hw_layer Lua on f407, try again (#2725) 2021-05-20 23:05:18 +03:00
iar_egt
init don't expose private state (#2696) 2021-05-14 14:56:45 -04:00
integration lua pwm hooks (#2687) 2021-05-20 19:01:17 -04:00
tunerstudio lua pwm hooks (#2687) 2021-05-20 19:01:17 -04:00
util rewrite table3d (#2723) 2021-05-20 22:31:16 +03:00
.cproject
.gitattributes
.gitignore
.project
CHANGELOG.md # 2021 May "Piercing Day" 2021-05-17 04:28:13 -04:00
Doxyfile
DoxygenLayout.xml
Makefile lua pwm hooks (#2687) 2021-05-20 19:01:17 -04:00
build-notes.txt
clean.bat
clean.sh
clean_build.bat
clean_compile_two_versions.bat
clean_compile_two_versions.sh Add two new V8 firing orders (#2423) 2021-03-05 19:28:17 -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
flash_dfu.sh
flash_erase407.bat
flash_erase407.sh
flash_erase767.bat
flash_openocd407.bat
flash_openocd407.sh
flash_openocd767.bat
flash_openocd_h7.bat H7 compilation #2284 2021-02-23 19:11:18 -05:00
flash_reboot_dfu.bat
flash_release.bat
gen_config.bat
gen_config.sh code duplication between hellen boards #2611 2021-05-01 19:45:09 -04:00
gen_config_board.bat
gen_config_board.sh NA6 ini is not uploaded fix #2649 2021-05-07 19:18:43 -04:00
gen_config_default.sh gen_config.sh code duplication #2451 2021-05-11 22:00:36 -04:00
gen_enum_to_string.bat
gen_enum_to_string.sh
gen_firing_order.bat
gen_fsio_example.bat
gen_fsio_example_reverse.bat
gen_live_documentation.bat
gen_live_documentation.sh
gen_ptrace_enums.bat
gen_signature.sh is gen_config invoked too often now? #2387 2021-03-05 20:16:59 -05:00
gen_system_fsio.bat
gen_trigger_images.bat
generate_docs.bat
generate_memory_usage_report.bat
get_performance_trace.bat
global.h compile gpiochips as cpp (#2702) 2021-05-17 08:42:56 +03:00
globalaccess.h
kill_for_coverity.c
license.txt
main.cpp version check (#2673) 2021-05-09 20:26:53 -04:00
main_hardfault.c
make4.bat
os_access.h
readme.md
reboot_ecu.bat
run_hw_test.bat
rusefi.cpp Hw layer rearrangement (#2703) 2021-05-16 06:01:00 -04:00
rusefi.h
rusefi.mk build (#2399) 2021-02-24 21:55:51 -05:00
rusefi_rules.mk
setup_linux_environment.sh progress 2021-05-15 05:46:54 -04:00
svnversion.h poke 2021-03-13 16:33:05 -05:00
update_version.bat
update_version.sh
version_check.h version check (#2673) 2021-05-09 20:26:53 -04: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.

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.