ba4a00d3bb
* Drop SingleChannelStateSequence in favor of MultiChannelStateSequenceWithData Most all the users were Multi* anyways, so just improve that: 1. Allow up to 8 waveforms to share one byte per timestamp. It could be better but this is simple and gets most of the benefit. 2. Use a wrapper structure to handle reserving space for the arrays. Makes the interface simpler and more rigid. Also saves 4 bytes per Multi*. Downside is access is now via -> and *, not . and (nothing). Saves 224 bytes of BSS, 1832 bytes of RAM4/CCM, 952 bytes of TEXT, and 103 bytes of RODATA * Instantiate a base_t to make debugging easier. Also fixes crash on real firmware by using &m_base instead - LTO optimization issue? * No magical templated StaticAlloc thingy. Just virtual functions. |
||
|---|---|---|
| .. | ||
| ChibiOS@e19494fd23 | ||
| ChibiOS-Contrib@fe3cdf8314 | ||
| bootloader | ||
| config | ||
| console | ||
| controllers | ||
| development | ||
| docs | ||
| ext | ||
| ext_algo | ||
| hw_layer | ||
| init | ||
| integration | ||
| pch | ||
| tunerstudio | ||
| util | ||
| .cproject | ||
| .gitattributes | ||
| .gitignore | ||
| .project | ||
| CHANGELOG.md | ||
| Doxyfile | ||
| DoxygenLayout.xml | ||
| Makefile | ||
| 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_release.bat | ||
| egt2can.cpp | ||
| exception.txt | ||
| flash.bat | ||
| flash_dfu.bat | ||
| flash_dfu.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 | ||
| gen_config_common.sh | ||
| gen_config_default.sh | ||
| gen_enum_to_string.bat | ||
| gen_enum_to_string.sh | ||
| gen_live_documentation.bat | ||
| gen_live_documentation.sh | ||
| gen_live_documentation_one_file.sh | ||
| gen_output_channels.sh | ||
| gen_ptrace_enums.bat | ||
| gen_signature.sh | ||
| gen_system_fsio.bat | ||
| 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_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_version.bat | ||
| update_version.sh | ||
| version_check.h | ||
readme.md
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.