rusefi-1/firmware/config/boards
GitHub build-firmware Action d75e0ec18c Auto-generated configs and docs 2022-01-04 04:48:36 +00:00
..
atlas
f407-discovery
f429-discovery
frankenso
hellen Auto-generated configs and docs 2022-01-04 04:48:36 +00:00
kinetis Auto-generated configs and docs 2022-01-04 04:48:36 +00:00
microrusefi MRE meta 2021-12-31 01:21:42 -05:00
nucleo_f767
nucleo_h743
prometheus
proteus Dual CAN for H7 #3718 2021-12-23 23:08:30 -05:00
skeleton
st_stm32f4
subaru_eg33 Auto-generated configs and docs 2022-01-04 04:48:36 +00:00
STM32F407VET6_Black.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh
common_make.bat
common_make.sh
hellen_meta.h https://rusefi.com/forum/viewtopic.php?f=2&t=2202 2021-12-30 19:14:32 -05:00
mre_meta.h MRE 2022-01-02 00:21:22 -05:00
proteus_meta.h
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