fome-fw/firmware/config/boards
rusefi de8bb682be meta & fixing default config 2021-10-27 16:42:45 -04:00
..
atlas idle closed loop vs open loop ui, etc (#3413) 2021-10-26 15:04:09 -04:00
f407-discovery
f429-discovery misc ethernet config parameters (#3343) 2021-10-11 15:35:09 -04:00
frankenso generate java enum from C enum? generate both C and java from yaml? #2102 2021-10-24 11:52:07 -04:00
hellen meta & fixing default config 2021-10-27 16:42:45 -04:00
microrusefi export board-specific macro for stm32 pins based on board yaml #3298 2021-10-26 10:27:10 -04:00
nucleo_f767
nucleo_h743
prometheus dead knock code (#3255) 2021-09-21 20:40:20 -04:00
proteus idle closed loop vs open loop ui, etc (#3413) 2021-10-26 15:04:09 -04:00
st_stm32f4
subaru_eg33 placing all logs into same folder 2021-10-23 20:18:09 -04:00
STM32F407VET6_Black.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh
common_make.bat
common_make.sh
mre_meta.h export board-specific macro for stm32 pins based on board yaml #3298 2021-10-26 10:27:10 -04:00
proteus_meta.h export board-specific macro for stm32 pins based on board yaml #3298 2021-10-26 10:27:10 -04:00
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