custom-board-bundle-sample-.../firmware/config/boards
Andrey 2bc09aca74 gen_config.sh code duplication #2451 2021-07-30 16:55:07 -04:00
..
atlas
f407-discovery gen_config.sh code duplication #2451 2021-07-30 16:55:07 -04:00
f429-discovery
frankenso
hellen +x 2021-07-30 10:10:18 -04:00
microrusefi
nucleo_f767
nucleo_h743
prometheus
proteus make build happy (#3067) 2021-07-26 09:08:05 -04:00
st_stm32f4
subaru_eg33 typos 2021-07-30 16:28:27 -04: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 atlas https://github.com/rusefi/rusefi/blob/master/firmware/config/boards/readme.md 2021-07-26 11:43:32 -04:00

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