fome-fw/firmware/config/boards
rusefillc d3721823ba helping build 2022-01-08 21:16:31 -05:00
..
atlas
f407-discovery
f429-discovery DRAM SDRAM #2551 2022-01-04 20:21:23 -05:00
frankenso
hellen helping build 2022-01-08 21:16:31 -05:00
microrusefi desperate measures 2022-01-08 18:41:56 -05:00
nucleo_f767 reducing copy-pasta - would this work? 2022-01-04 20:03:41 -05:00
nucleo_h743 reducing copy-pasta - would this work? 2022-01-04 20:03:41 -05:00
prometheus reducing copy-pasta - would this work? 2022-01-04 20:03:41 -05:00
proteus reducing copy-pasta - would this work? 2022-01-04 20:03:41 -05:00
st_stm32f4 reducing copy-pasta - would this work? 2022-01-04 20:03:41 -05:00
subaru_eg33 reducing code duplication 2022-01-05 01:02:50 -05:00
STM32F407VET6_Black.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh
common_make.bat
common_make.sh
hellen_meta.h extracting common hellen to it's own file 2022-01-08 20:16:01 -05:00
mre_meta.h
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