rusefi/firmware/config/boards
GitHub gen-configs Action 33187b1231 Auto-generated configs and docs 2023-06-12 17:33:19 +00:00
..
48way switch boards to mostly not use LED config 2023-06-05 14:12:32 -04:00
BB_V2 dead cleanup 2023-06-05 13:03:58 -04:00
BB_V3 dead cleanup 2023-06-05 13:03:58 -04:00
Benelli_Walbro/connectors
GDI4 only:gdi4 2023-06-10 10:22:35 -04:00
atlas
core8 switch boards to mostly not use LED config 2023-06-05 14:12:32 -04:00
coreECU switch boards to mostly not use LED config 2023-06-05 14:12:32 -04:00
cypress Auto-generated configs and docs 2023-06-12 17:33:19 +00:00
f407-discovery humans are __weak__ 2023-06-06 21:15:43 -04:00
f429-208 progress 2023-06-05 14:52:34 -04:00
f429-discovery switch boards to mostly not use LED config 2023-06-05 14:12:32 -04:00
frankenso
hellen small board 2023-06-10 23:44:31 -04:00
kinetis Auto-generated configs and docs 2023-06-12 17:33:19 +00:00
lambda-x2
m74_9 progress 2023-06-05 14:52:34 -04:00
microrusefi switch boards to mostly not use LED config 2023-06-05 14:12:32 -04:00
nucleo_f429 switch boards to mostly not use LED config 2023-06-05 14:12:32 -04:00
nucleo_f767 only:it's going to be painful 2023-04-29 09:40:25 -04:00
nucleo_h743 switch boards to mostly not use LED config 2023-06-05 14:12:32 -04:00
prometheus switch boards to mostly not use LED config 2023-06-05 14:12:32 -04:00
proteus switch boards to mostly not use LED config 2023-06-05 14:09:14 -04:00
s105 progress 2023-06-05 14:52:34 -04:00
subaru_eg33 Auto-generated configs and docs 2023-06-12 17:33:19 +00:00
tdg-pdm8 only:tdg_pdm8 2023-05-23 16:25:45 -04:00
test-build-guards test-build-guards 2023-06-01 19:22:03 -04:00
STM32F407VET6_Black.bat
STM32F407VET6_Mini.bat
common_make.bat
common_make.sh https://github.com/rusefi/rusefi/issues/5284 2023-05-23 15:42:08 -04:00
hellen_meta.h small board 2023-06-10 23:44:31 -04:00
mre_meta.h copy-pasta kills best intentions 2023-06-03 21:38:54 -04:00
proteus_meta.h
readme.md

readme.md

Boards Directory

rusEFI supports quite a wide array of hardware - we support stm32f4 and we support stm32h7, we have kinetis and we support cypress MCUs. 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 misc/jenkins/compile_other_versions/run.bat which is executed by build server.

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_BOARDNAME becomes BUNDLE_NAME

New board procedure once you have new folder in this boards directory

  1. update gen_config.sh: add "board board" pair into 'for BOARD' iteration - this would produce new signature*.h file and new rusefi*.ini file

  2. update build-firmware.yaml to get new firmware bundle on https://rusefi.com/build_server/

  3. 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 chagned 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