rusefi/firmware
Andrey 3ffd340409 Option to log VVT target #2913
boring details
2021-07-06 20:54:39 -04:00
..
ChibiOS@948b015c9c
ChibiOS-Contrib@fe3cdf8314 fresh 2021-04-15 00:43:19 -04:00
bootloader Fix bootloader build #2907 2021-07-05 15:08:11 -04:00
config Unified cyl count macro (#2914) 2021-07-06 20:14:08 -04:00
console Unified cyl count macro (#2914) 2021-07-06 20:14:08 -04:00
controllers Unified cyl count macro (#2914) 2021-07-06 20:14:08 -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 Doxygen titles (#2728) 2021-05-22 22:10:58 +03:00
hw_layer more graceful chibios assertion failure (#2859) 2021-07-05 18:18:58 -04:00
iar_egt
init don't expose private state (#2696) 2021-05-14 14:56:45 -04:00
integration Option to log VVT target #2913 2021-07-06 20:54:39 -04:00
tunerstudio Option to log VVT target #2913 2021-07-06 20:00:53 -04:00
util Fix swap macro (#2904) 2021-07-04 18:03:17 -04:00
.cproject
.gitattributes
.gitignore
.project
CHANGELOG.md Nissan VVT trigger decoder #2887 2021-07-03 12:57:14 -04:00
Doxyfile
DoxygenLayout.xml
Makefile Chibios-Contrib for stm32 (#2903) 2021-07-05 09:53:45 -04:00
build-notes.txt
clean.bat
clean.sh
clean_build.bat
clean_compile_two_versions.bat
clean_compile_two_versions.sh
compile.bat
compile_and_program.bat
cov_config.bat
cov_run.bat
coverity.yml
dump.bat
dump_iar.bat
dump_release.bat
egt2can.cpp more graceful chibios assertion failure (#2859) 2021-07-05 18:18:58 -04:00
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
flash_reboot_dfu.bat
flash_release.bat
gen_config.bat
gen_config.sh DRAM SDRAM #2551 2021-06-27 11:23:16 -04:00
gen_config_board.bat
gen_config_board.sh mkfs.fat phase kills gen_config #2736 2021-05-24 15:35:35 -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 human readable warning codes into TS #2898 2021-07-03 21:01:42 -04:00
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
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 Unified cyl count macro (#2914) 2021-07-06 20:14:08 -04:00
rusefi.h
rusefi.mk helping build? 2021-07-05 10:57:40 -04:00
rusefi_rules.mk
setup_linux_environment.sh progress 2021-05-15 05:46:54 -04:00
svnversion.h poke 2021-05-24 09:18:14 -04: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.