fome-fw/firmware/config/boards
Matthew Kennedy 8cc6ef83f9 h7 flash, guard against no CAN (#2317)
* h7 flash

* guard some other stuff

* I guess it just builds now?

* maybe ci too
2021-02-08 16:24:38 -05:00
..
frankenso New board pin-mapping system (#2231) 2021-01-22 12:03:14 -05:00
hellen move f4 board.h (#2313) 2021-02-08 15:29:07 -05:00
me7_pnp move board.h for f7/h7 (#2316) 2021-02-08 15:46:48 -05:00
microrusefi move board.h for f7/h7 (#2316) 2021-02-08 15:46:48 -05:00
nucleo_f767 move board.h for f7/h7 (#2316) 2021-02-08 15:46:48 -05:00
nucleo_h743 h7 flash, guard against no CAN (#2317) 2021-02-08 16:24:38 -05:00
prometheus include board.c from hw_ports.mk (#2311) 2021-02-08 07:52:31 -06:00
proteus move board.h for f7/h7 (#2316) 2021-02-08 15:46:48 -05:00
st_stm32f4 move f4 board.h (#2313) 2021-02-08 15:29:07 -05:00
subaru_eg33 include board.c from hw_ports.mk (#2311) 2021-02-08 07:52:31 -06:00
STM32F407VET6_Black.bat
STM32F407VET6_Hellen_STM.bat Hellen says merge #1772 getting closer? 2020-09-10 21:12:25 -04:00
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 Cypress artifact needs .hex file #1835 2020-09-29 18:50:51 -04:00
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