fome-fw/firmware/config/boards
David Holdeman c61d11e3d0 Pinout links (#3037)
* add support for links

* add undefined check and remove pdiv ref

* add MRE id

* clear search
2021-07-23 09:20:13 -04:00
..
f429-discovery
frankenso
hellen Nissan 2021-07-22 23:44:25 -04:00
microrusefi Pinout links (#3037) 2021-07-23 09:20:13 -04:00
nucleo_f767
nucleo_h743
prometheus
proteus Button to apply nDBANK #2996 2021-07-20 13:44:45 -04:00
st_stm32f4
subaru_eg33 board: subaru eg33: fix pinouts, add aux connector (#2986) 2021-07-18 14:58:22 -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

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

See also https://github.com/rusefi/rusefi/wiki/Hardware