rusefi/firmware
rusefi a0a1a9f9bb "TLE8888 SR Unexpected response" does not work as intended #1466 2020-05-22 08:23:49 -04:00
..
ChibiOS@1a2c5967dc Update chibios (#1364) 2020-04-25 16:32:32 -04:00
ChibiOS-Contrib@8f7c2d187b Revert "Fresh generated - auto" 2020-04-18 19:11:47 -04:00
bootloader binary logging (#1443) 2020-05-17 15:56:37 -04:00
config Fresh generated - auto 2020-05-22 01:36:48 -04:00
console Binary logging to SD (#1461) 2020-05-21 15:52:58 -04:00
controllers Fresh generated - auto 2020-05-22 01:36:48 -04:00
development fix unlock bug (#1384) 2020-04-29 16:42:55 -04:00
docs
ext
ext_algo
hw_layer "TLE8888 SR Unexpected response" does not work as intended #1466 2020-05-22 08:23:49 -04:00
iar_egt
init Redundant tps (#1427) 2020-05-18 14:32:00 -04:00
integration progress 2020-05-22 01:16:55 -04:00
tunerstudio Fresh generated - auto 2020-05-22 00:40:40 -04:00
util dead datalog code (#1439) 2020-05-16 00:11:52 -04:00
.cproject
.gitignore XML export progress 2020-05-20 01:24:26 -04:00
.project
Doxyfile
DoxygenLayout.xml
Makefile binary logging (#1443) 2020-05-17 15:56:37 -04:00
build-notes.txt
clean.bat
clean_build.bat
clean_compile_two_versions.bat
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_erase767.bat
flash_openocd407.bat
flash_openocd767.bat
flash_reboot_dfu.bat command line switch to DFU 2020-05-08 21:11:11 -04:00
flash_release.bat
gen_config.bat automation should be automated 2020-05-20 11:13:42 -04:00
gen_config.sh
gen_config_board.bat progress - firing order logic to be re-evaluated every time we generate 2020-05-04 23:54:28 -04:00
gen_config_board.sh
gen_enum_to_string.bat progress 2020-05-20 09:16:26 -04:00
gen_enum_to_string.sh
gen_firing_order.bat
gen_fsio_example.bat
gen_live_documentation.bat better script name 2020-02-22 15:38:21 -05:00
gen_ptrace_enums.bat
gen_system_fsio.bat
gen_trigger_images.bat :) 2020-05-14 20:53:47 -04:00
generate_docs.bat
generate_memory_usage_report.bat
global.h
globalaccess.h
kill_for_coverity.c
license.txt
main.cpp
main_hardfault.c
make4.bat
os_access.h code style 2020-04-01 21:32:21 -04:00
readme.md
reboot_ecu.bat
run_hw_test.bat
rusefi.cpp HW_CHECK_MODE 2020-05-20 22:15:47 -04:00
rusefi.h
rusefi.mk remove (#1188) 2020-03-13 17:19:29 -04:00
rusefi_rules.mk Fix master (#1134) 2020-02-08 16:34:29 -05:00
svnversion.h rusEFI console start-up time improvements 2020-05-21 01:16:14 -04:00
update_version.bat

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.