custom-board-bundle-sample-.../firmware/config/boards
Matthew Kennedy b83fc540de enable ethernet on atlas (#3348)
* enable h7 ethernet

* some ethernet settings while we're here

* mac address

* misc

* extra spaces

Co-authored-by: Matthew Kennedy <makenne@microsoft.com>
2021-10-16 12:31:53 -04:00
..
atlas enable ethernet on atlas (#3348) 2021-10-16 12:31:53 -04:00
f407-discovery
f429-discovery misc ethernet config parameters (#3343) 2021-10-11 15:35:09 -04:00
frankenso
hellen https://github.com/rusefi/hellen-NB1-issues/issues/22 2021-10-14 21:44:09 -04:00
microrusefi https://rusefi.com/forum/viewtopic.php?p=42392#p42392 2021-09-28 16:21:57 -04:00
nucleo_f767
nucleo_h743
prometheus
proteus Proteus yaml has issues about reserved pins fix #3291 2021-10-08 06:13:07 -04:00
st_stm32f4
subaru_eg33
STM32F407VET6_Black.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 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