rusefi/firmware/config/boards
rusefillc d6dea65b80 https://github.com/rusefi/alphax-2chan/issues/15 2022-01-15 10:41:05 -05:00
..
atlas refactoring? 2022-01-14 22:45:49 -05:00
f407-discovery
f429-discovery refactoring? 2022-01-14 23:10:48 -05:00
frankenso dead vss flag (#3499) 2021-11-07 14:36:46 -05:00
hellen https://github.com/rusefi/alphax-2chan/issues/15 2022-01-15 10:41:05 -05:00
kinetis refactoring? 2022-01-14 23:10:48 -05:00
microrusefi refactoring? 2022-01-14 23:10:48 -05:00
nucleo_f767 refactoring? 2022-01-14 22:45:49 -05:00
nucleo_h743 refactoring? 2022-01-14 23:10:48 -05:00
prometheus Code style for methods with zero arguments #3535 2022-01-11 22:26:24 -05:00
proteus refactoring? 2022-01-14 22:45:49 -05:00
skeleton refactoring? 2022-01-14 22:45:49 -05:00
st_stm32f4 refactoring - one step back 2022-01-14 23:37:50 -05:00
subaru_eg33 refactoring? 2022-01-14 22:45:49 -05:00
STM32F407VET6_Black.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh
common_make.bat
common_make.sh Openblt deliver (#3486) 2021-11-07 13:50:01 -05:00
hellen_meta.h export board-specific macro for stm32 pins based on board yaml #3298 2022-01-12 13:34:21 -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