48ab85d636
cypress trying to start TS TS connect success! blind code ready for GPT,ADC,SPI SPI basic test works on 9201 and 8860 Timer is working ADC fix? Flash kinda works... in debug mode DRV8860 driver works! ADC partially works! Flash works! adc 1 channel works fix for ADC channels>16 & fastADC problem ADC works! EXTINT first attempt... no IRQ? Led3 blinks EXTINT works! trigger_adc EXTINT part works! trigger_ADC analog preparations... not working yet ADC now 100% works! But fast is NOT 10kHz! Fast ADC works... Almost - strange adcToVoltage values... fastADC working only first 22secs + fatal error after 33secs + USB not connecting fastADC is working again, problems solved! triggerADC - It works! (Still no timeshift compensation) Forgot drv8860 ADC->EXTI trigger switching works! (but not seamlessly) ADC->EXTI trigger switching now seamless? Needs more testing ADC->EXTI trigger switching works! trigger+RPM works but still trgerrors... trying to impl. adaptive threshold... No luck so far :( trigger detector almost works - trgerr=0 but no rpm<200? triggerADC finally works!!! For now... backup_ram for cypress main_relay, stepper better main_relay+stepper USB VBus detection CAN driver draft CAN update CAN interrupts fix update update update update update main.cpp clean-up rusefi.ini clean-up compilation fix compilation fix compilation fix |
||
|---|---|---|
| .. | ||
| .vscode | ||
| ChibiOS@85cf4582a9 | ||
| ChibiOS-Contrib@8f7c2d187b | ||
| bootloader | ||
| config | ||
| console | ||
| controllers | ||
| development | ||
| docs | ||
| ext | ||
| ext_algo | ||
| hw_layer | ||
| iar_egt | ||
| init | ||
| integration | ||
| tunerstudio | ||
| util | ||
| .cproject | ||
| .gitignore | ||
| .project | ||
| Doxyfile | ||
| DoxygenLayout.xml | ||
| Makefile | ||
| build-notes.txt | ||
| clean.bat | ||
| clean_build.bat | ||
| clean_compile_two_versions.bat | ||
| 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 | ||
| flash_erase407.bat | ||
| flash_erase767.bat | ||
| flash_openocd407.bat | ||
| flash_openocd767.bat | ||
| flash_release.bat | ||
| gen_config.bat | ||
| gen_config.sh | ||
| gen_config2.bat | ||
| gen_config_board.bat | ||
| gen_config_board.sh | ||
| gen_enum_to_string.bat | ||
| gen_enum_to_string.sh | ||
| gen_firing_order.bat | ||
| gen_fsio_example.bat | ||
| gen_ptrace_enums.bat | ||
| gen_system_fsio.bat | ||
| gen_trigger_images.bat | ||
| generate_docs.bat | ||
| generate_memory_usage_report.bat | ||
| global.h | ||
| globalaccess.h | ||
| kill_for_coverity.c | ||
| license.txt | ||
| main.cpp | ||
| main_hardfault.c | ||
| make4.bat | ||
| os_access.h | ||
| readme.md | ||
| reboot_ecu.bat | ||
| run_hw_test.bat | ||
| rusefi.cpp | ||
| rusefi.h | ||
| rusefi.mk | ||
| rusefi_rules.mk | ||
| svnversion.h | ||
| update_version.bat | ||
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.
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.