rusefi/firmware
rusefi 75d9417131 miata vvt trigger decoding is broken #1145 2020-02-14 00:37:36 -05:00
..
.vscode vscode usability (#938) 2019-09-16 07:07:42 -04:00
ChibiOS@85cf4582a9 different handling of SD card loss 2019-09-21 12:40:40 -04:00
ChibiOS-Contrib@8f7c2d187b we might not use Contrib at the moment 2019-09-22 09:56:47 -04:00
bootloader The Big Refactoring of 2019: folder structure #723 2019-12-04 00:04:27 -05:00
config laughable gdi progress 2019-12-26 21:33:12 -05:00
console maybe improvent for trigger errors in TS and console, TS still does not know about order error counter 2019-12-25 15:57:47 -05:00
controllers miata vvt trigger decoding is broken #1145 2020-02-14 00:37:36 -05:00
development replacing probably unused engineSnifferHisto with new perf_trace 2019-12-23 20:22:17 -05:00
docs
ext
ext_algo
hw_layer would URLs work? 2019-12-26 22:29:04 -05:00
iar_egt
init Remove sensor reporting loc (#1064) 2019-12-16 22:45:46 -05:00
integration Shrink output channels, now with passing CI (#1077) 2019-12-22 08:12:45 -05:00
tunerstudio maybe improvent for trigger errors in TS and console, TS still does not know about order error counter 2019-12-25 15:57:47 -05:00
util style 2019-12-23 23:05:40 -05:00
.cproject
.gitignore software jump to DFU #809 2019-08-04 00:21:44 -04:00
.project
Doxyfile add sensor framework, tests (#929) 2019-09-21 14:33:38 -04:00
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 notes to self 2019-12-16 01:47:34 -05:00
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 docs 2019-07-28 18:56:23 -04:00
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 Live Data: trigger current gap 2019-09-03 19:30:51 -04:00
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 CI instability: FATAL error: warn stream not initialized for 6039 2019-08-04 13:48:10 -04:00
main_hardfault.c This black magic improves hard fault debugging experience 2019-09-22 21:28:19 -04:00
make4.bat
os_access.h
readme.md skeleton & docs (#995) 2019-11-03 08:41:14 -05:00
reboot_ecu.bat command line utiity to reboot rusEfi 2019-08-23 21:01:37 -04:00
run_hw_test.bat docs :( 2019-12-21 19:50:16 -05:00
rusefi.cpp that's not a worth a file 2019-12-24 00:03:53 -05:00
rusefi.h
rusefi.mk software jump to DFU #809 2019-08-03 22:08:23 -04:00
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.