rusefi/firmware/config/boards
GitHub build-firmware Action 3a5c7bd85c Auto-generated configs and docs 2022-01-12 01:53:19 +00:00
..
atlas
f407-discovery
f429-discovery F429 discovery ram dev (#3761) 2022-01-10 16:14:39 -05:00
frankenso
hellen Auto-generated configs and docs 2022-01-12 01:53:19 +00:00
kinetis Auto-generated configs and docs 2022-01-12 01:53:19 +00:00
microrusefi GDI red FATAL led on cranking #3766 2022-01-10 16:42:31 -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 per-board pre-low-power handlers (#3752) 2022-01-10 08:37:05 -05:00
skeleton 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 Auto-generated configs and docs 2022-01-12 01:53:19 +00:00
STM32F407VET6_Black.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh
common_make.bat
common_make.sh
hellen_meta.h Hellen mcu module detector (experimental) (#3756) 2022-01-09 17:40:08 -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