rusefi-1/firmware
Matthew Kennedy 0e674f7eca ETB Encapsulation & C++ Conventions (#1049)
* encapsulate etb stuff, c++ conventions

* remove DECLARE_ENGINE_PTR/INJECT_ENGINE_REFERENCE

* reduce include dependencies

* Revert "reduce include dependencies"

This reverts commit c529bbbf757cd9070f6e00616f84b1229eeb768e.

* Revert "remove DECLARE_ENGINE_PTR/INJECT_ENGINE_REFERENCE"

This reverts commit ca98b18cd4dae24b993d1263a18daf509dcd54b9.
2019-12-10 19:37:04 -05:00
..
.vscode
ChibiOS@85cf4582a9
ChibiOS-Contrib@8f7c2d187b
bootloader The Big Refactoring of 2019: folder structure #723 2019-12-04 00:04:27 -05:00
config copyArray helper (#1048) 2019-12-10 18:04:50 -05:00
console ETB Encapsulation & C++ Conventions (#1049) 2019-12-10 19:37:04 -05:00
controllers ETB Encapsulation & C++ Conventions (#1049) 2019-12-10 19:37:04 -05:00
development The Big Refactoring of 2019: folder structure #723 2019-12-04 01:11:10 -05:00
docs
ext
ext_algo
hw_layer just a trivial massive rename: TriggerState > TriggerWaveform 2019-12-08 01:09:39 -05:00
iar_egt
init consistency 2019-11-07 15:22:17 -05:00
integration TPS#2 calibration & fixing ETB in TS 2019-12-08 00:37:33 -05:00
tunerstudio TPS#2 calibration & fixing ETB in TS 2019-12-08 00:37:33 -05:00
util copyArray helper (#1048) 2019-12-10 18:04:50 -05:00
.cproject
.gitignore
.project
Doxyfile
DoxygenLayout.xml
Makefile The Big Refactoring of 2019: folder structure #723 2019-12-03 23:52:44 -05:00
build-notes.txt skeleton & docs (#995) 2019-11-03 08:41:14 -05:00
clean.bat
clean_build.bat
clean_compile_two_versions.bat Remove chibios trace flag (#1037) 2019-12-02 19:11:07 -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 A Unix shell script matching the functionality flash_dfu.bat 2019-11-11 20:25:55 -05:00
flash_erase407.bat
flash_erase767.bat
flash_openocd407.bat
flash_openocd767.bat
flash_release.bat
gen_config.bat kinetis into gen_config.bat 2019-11-16 14:44:47 -05:00
gen_config2.bat
gen_config_board.bat
gen_enum_to_string.bat
gen_firing_order.bat firing order tool integration 2019-11-24 23:49:05 -05:00
gen_fsio_example.bat
gen_ptrace_enums.bat PerfTraceTool 2019-11-25 00:57:36 -05:00
gen_system_fsio.bat
gen_trigger_images.bat
generate_docs.bat
generate_memory_usage_report.bat
global.h todo 2019-11-13 22:02:13 -05:00
globalaccess.h refactoring 2019-11-20 01:35:08 -05:00
kill_for_coverity.c
license.txt
main.cpp
main_hardfault.c
make4.bat
os_access.h
readme.md skeleton & docs (#995) 2019-11-03 08:41:14 -05:00
reboot_ecu.bat
rusefi.cpp
rusefi.h
rusefi.mk
rusefi_rules.mk shared GCC settings between projects 2019-12-02 10:26:16 -05:00
svnversion.h poke 2019-11-18 15:37:58 -05: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.