b10ba4ddf5
use script to find meta-info-<bundle name>.env |
||
|---|---|---|
| .. | ||
| Benelli_Walbro/connectors | ||
| GDI4 | ||
| at_start_f435 | ||
| atlas | ||
| core8 | ||
| cypress | ||
| f407-discovery | ||
| f429-208 | ||
| f429-discovery | ||
| f469-discovery | ||
| frankenso_na6 | ||
| hellen | ||
| kinetis | ||
| lambda-x2 | ||
| m74_9 | ||
| microrusefi | ||
| nucleo_f413 | ||
| nucleo_f429 | ||
| nucleo_f767 | ||
| nucleo_h743 | ||
| prometheus | ||
| proteus | ||
| s105 | ||
| subaru_eg33 | ||
| tdg-pdm8 | ||
| test-build-guards | ||
| STM32F407VET6_Black.bat | ||
| STM32F407VET6_Mini.bat | ||
| board_id.cpp | ||
| board_id.h | ||
| common_make.bat | ||
| common_make.sh | ||
| common_script.sh | ||
| common_script_hex2dfu_init.inc | ||
| common_script_post_build_without_blt.inc | ||
| common_script_read_meta_env.inc | ||
| hellen_meta.h | ||
| hellen_mm64_meta.h | ||
| hellen_mm100_meta.h | ||
| hellen_mm176_meta.h | ||
| mre_meta.h | ||
| proteus_meta.h | ||
| readme.md | ||
readme.md
Boards Directory
TL,DR: for community edition see f407-discovery.
rusEFI supports quite a wide array of hardware:
- most supported platforms are stm32f4 and stm32f7
- alpha version support stm32h7
- experimental support kinetis
- experimental support cypress MCUs.
Looking for most default firmware for your own hardware? See f407-discovery
We support on-board a number of smart GPIO chips, overall we support quite a wide array of hardware. With all those options our goal is to provide nice user experience which means upfront investment by board designer.
For best user experience we have more than a dozen of different binaries which are all compiled from same firmware files with different configuration. This folder is all about that process.
See https://rusefi.com/build_server/
By definition, BOARD_NAME is a folder in firmware\config\boards
One BOARD_NAME could be producing a number of artifacts via compile_$BUNDLE_NAME.sh scripts
Work in progress: SHORT_BOARD_NAME becomes BUNDLE_NAME
New board procedure once you have new folder in this boards directory
-
update gen_config.sh: add "board board" pair into 'for BOARD' iteration - this would produce new signature*.h file and new rusefi*.ini file
-
update build-firmware.yaml to get new firmware bundle on https://rusefi.com/build_server/
-
add connector pinout mapping yaml file see examples of yaml files in 'connectors' subfolders here.
See also https://github.com/rusefi/rusefi/wiki/Hardware
FAQ
Q: how do I change Primary UART pins via TS?
A: Primary UART, critical error LED pin and maybe a couple more of the most fundamental pins could NOT be changed via TS. You would need another binary altogether - either another official binary or a custom binary.
Q: I need more info!
A: please remember about https://github.com/rusefi/rusefi/wiki/Hardware#q-this-is-all-very-cool-but-you-guys-do-not-have-a-plugplay-for-my-trabant-i-think-i-will-go-and-make-a-new-rusefi-board-just-for-my-trabant