fome-fw/firmware/config/boards
Matthew Kennedy 56240cb668 we have other places to set these MCU values (#3875)
* we have other places to set these values

* missing parts

Co-authored-by: rusefillc <rusefillc@gmail.com>
2022-02-01 18:18:16 -05:00
..
atlas
f407-discovery
f429-discovery
frankenso
hellen SD card UI cleanup (#3870) 2022-02-01 15:42:23 -05:00
microrusefi SD card UI cleanup (#3870) 2022-02-01 15:42:23 -05:00
nucleo_f767 Remove fsio part 1 (#3871) 2022-02-01 15:42:04 -05:00
nucleo_h743
prometheus Remove fsio part 1 (#3871) 2022-02-01 15:42:04 -05:00
proteus SD card UI cleanup (#3870) 2022-02-01 15:42:23 -05:00
subaru_eg33 we have other places to set these MCU values (#3875) 2022-02-01 18:18:16 -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
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