History

Andrey 54133f21f8 Option to log VVT target #2913		2021-07-06 20:00:53 -04:00
..
f429-discovery	DRAM SDRAM #2551	2021-06-27 12:14:53 -04:00
frankenso	testing yaml automation	2021-05-07 15:34:48 -04:00
hellen	hellen 128 defaults (#2912 )	2021-07-06 01:03:07 -04:00
microrusefi	https://github.com/rusefi/rusefi/issues/2848	2021-07-03 23:47:23 -04:00
nucleo_f767	…
nucleo_h743	…
prometheus	remove cranking dwell angle (#2814 )	2021-06-13 07:52:07 -04:00
proteus	s/controlPin1/controlPin/	2021-06-05 16:19:01 -04:00
st_stm32f4	…
subaru_eg33	Option to log VVT target #2913	2021-07-06 20:00:53 -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

manually add one .h and one .ini files into git - see gen_config.sh comment
update gen_config.sh: add "board board" pair into 'for BOARD' iteration