rusefi/firmware/config/boards
rusefi 1edb9f279d https://github.com/rusefi/hellen-NB1-issues/issues/15 2021-09-29 11:51:25 -04:00
..
atlas
f407-discovery
f429-discovery
frankenso
hellen https://github.com/rusefi/hellen-NB1-issues/issues/15 2021-09-29 11:51:25 -04:00
kinetis Auto-generated configs and docs 2021-09-27 21:22:53 +00:00
microrusefi https://rusefi.com/forum/viewtopic.php?p=42392#p42392 2021-09-28 16:21:57 -04:00
nucleo_f767
nucleo_h743
prometheus dead knock code (#3255) 2021-09-21 20:40:20 -04:00
proteus HTML title for pinout pages fix #2882 2021-08-15 14:22:34 -04:00
skeleton
st_stm32f4
subaru_eg33 Auto-generated configs and docs 2021-09-27 21:22:53 +00:00
STM32F407VET6_Black.bat
STM32F407VET6_Hellen_STM.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh
common_make.bat
common_make.sh
readme.md

readme.md

Boards Directory

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

  1. manually add one signature*.h and one .ini files into git - see gen_config.sh comment

  2. update gen_config.sh: add "board board" pair into 'for BOARD' iteration

See also https://github.com/rusefi/rusefi/wiki/Hardware