rusefi-1/firmware/config/boards
BeerMoneyMotorsports b17dd4f600
Update main.yaml (#2896)
2021-07-02 17:52:16 -04:00
..
f429-discovery DRAM SDRAM #2551 2021-06-27 12:14:53 -04:00
frankenso
hellen Update main.yaml (#2896) 2021-07-02 17:52:16 -04:00
kinetis Nissan VVT trigger decoder #2887 2021-07-01 21:48:47 -04:00
microrusefi
nucleo_f767
nucleo_h743
prometheus
proteus
skeleton
st_stm32f4
subaru_eg33 Nissan VVT trigger decoder #2887 2021-07-01 21:48:47 -04:00
STM32F407VET6_Black.bat
STM32F407VET6_Hellen_STM.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh
common_make.bat
common_make.sh
readme.md DRAM SDRAM #2551 2021-06-27 12:31:18 -04:00

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 .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