fome-fw/firmware/config/boards
David Holdeman 3ae34637b8 add info to 4S (#2300) 2021-02-06 16:06:25 -06:00
..
frankenso New board pin-mapping system (#2231) 2021-01-22 12:03:14 -05:00
hellen add info to 4S (#2300) 2021-02-06 16:06:25 -06:00
me7_pnp
microrusefi -g3 to -g (#2256) 2021-01-31 14:13:55 -05:00
nucleo_f746 Chibi os 20 (#2212) 2021-01-19 15:20:35 -05:00
nucleo_f767 that's a bit useless? 2021-02-05 20:14:52 -05:00
nucleo_h743 H7 compilation #2284 2021-02-06 00:07:05 -05:00
prometheus New board pin-mapping system (#2231) 2021-01-22 12:03:14 -05:00
proteus hardware ci tweaks (#2266) 2021-02-02 08:14:24 -06:00
st_stm32f4 Revert "FRANKENSO to use HAL_VSS_USE_PAL" 2021-01-24 00:05:17 -05:00
subaru_eg33 Add subaru eg33 (#2294) 2021-02-06 12:50:34 -06:00
STM32F407VET6_Black.bat
STM32F407VET6_Hellen_STM.bat
STM32F407VET6_Mini.bat
clean_env_variables.bat
clean_env_variables.sh let's build for h7 2021-02-05 20:58:34 -05:00
common_make.bat
common_make.sh
readme.md

readme.md

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