rusefi-full/firmware
David Holdeman 49f8daae14
More untested transmission features (#4093)
* use ISS for gearbox ratio, add gauge for TC ratio

* measure shift time

* add shift time gauge, todo notes for pc

* do conversion in the right direction

* switch to Timer and seconds

* try fixing build

* try fixing build again

* try defines, remove include

* use shift pcs

* add 3-2 pct curve

* control 3-2 solenoid

* move 3-2 to persistent config

* fix param
2022-04-23 07:34:39 -04:00
..
ChibiOS@8f0926be79
ChibiOS-Contrib@63b50e410c
bootloader
config More untested transmission features (#4093) 2022-04-23 07:34:39 -04:00
console More untested transmission features (#4093) 2022-04-23 07:34:39 -04:00
controllers More untested transmission features (#4093) 2022-04-23 07:34:39 -04:00
development
docs
ext
ext_algo
hw_layer knock threshold table fix (#4077) 2022-04-18 08:03:16 -04:00
init Add ISS sensor, rearrange some transmission config (#4089) 2022-04-21 09:07:52 -04:00
integration More untested transmission features (#4093) 2022-04-23 07:34:39 -04:00
pch
tunerstudio More untested transmission features (#4093) 2022-04-23 07:34:39 -04:00
util Set sensible default for dwell by voltage multiplier table fix #4067 2022-04-13 15:21:44 -04:00
.cproject
.gitattributes
.gitignore
.project
CHANGELOG.md logging of live data structs was: data points #3614 2022-04-18 10:03:27 -04:00
Doxyfile
DoxygenLayout.xml
Makefile
build-notes.txt
check.c
clean.bat
clean.sh
clean_build.bat
clean_compile_two_versions.bat
clean_compile_two_versions.sh
common.mk
compile.bat
compile_and_program.bat
cov_config.bat
cov_run.bat
coverity.yml
dump.bat
dump_release.bat
egt2can.cpp
exception.txt
flash.bat
flash_can.sh
flash_dfu.bat
flash_dfu.sh
flash_dfu_erase.sh
flash_dfu_openblt_only.sh
flash_erase407.bat
flash_erase407.sh
flash_erase767.bat
flash_erase_dfu.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
gen_config_board.bat
gen_config_board.sh sorry .ini file has grown! reminds me that someone was suggesting to use array definition syntax to reduce size 2022-04-18 12:21:35 -04:00
gen_config_common.sh documentation/readbility 2022-04-18 11:05:04 -04:00
gen_config_default.sh
gen_enum_to_string.bat
gen_enum_to_string.sh
gen_live_documentation.bat
gen_live_documentation.sh
gen_output_channels.sh this was also broken recently 2022-04-17 03:29:34 -04:00
gen_ptrace_enums.bat
gen_signature.sh
gen_trigger_images.bat
generate_docs.bat
generate_memory_usage_report.bat
generate_memory_usage_report.sh
get_performance_trace.bat
global.h
globalaccess.h
kill_for_coverity.c
license.txt
main.cpp
main_hardfault.c
make4.bat
openblt.mk
os_access.h
readme.md
reboot_dfu.sh
reboot_ecu.bat
run_hw_test.bat
rusefi.cpp
rusefi.h
rusefi.mk
rusefi_pch.mk
rusefi_rules.mk
send_command.bat
setup_linux_environment.sh
svnversion.h Update date 2022-04-23 00:17:35 +00:00
update_version.bat
update_version.sh

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.

See setup_linux_environment.sh

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.