rusefi-1/firmware/config/boards
GitHub build-firmware Action fdc3a83838 Auto-generated configs and docs 2021-10-24 12:31:15 +00:00
..
atlas enable ethernet on atlas (#3348) 2021-10-16 12:31:53 -04:00
f407-discovery
f429-discovery misc ethernet config parameters (#3343) 2021-10-11 15:35:09 -04:00
frankenso
hellen Auto-generated configs and docs 2021-10-24 12:31:15 +00:00
kinetis Auto-generated configs and docs 2021-10-24 12:31:15 +00:00
microrusefi https://rusefi.com/forum/viewtopic.php?p=42392#p42392 2021-09-28 16:21:57 -04:00
nucleo_f767 yet more pch (#3068) 2021-08-03 22:05:01 -04:00
nucleo_h743 yet more pch (#3068) 2021-08-03 22:05:01 -04:00
prometheus dead knock code (#3255) 2021-09-21 20:40:20 -04:00
proteus Honda K 2021-10-23 16:19:28 -04:00
skeleton yet more pch (#3068) 2021-08-03 22:05:01 -04:00
st_stm32f4
subaru_eg33 Auto-generated configs and docs 2021-10-24 12:31:15 +00:00
STM32F407VET6_Black.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