FOME-Tech
/
fome-fw
mirror of https://github.com/FOME-Tech/fome-fw.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
fome-fw/firmware/config/boards
History
rusefillc 9cae07cfd2 reducing code duplication 2022-05-24 15:45:06 -04:00
..
GDI4
…
atlas Brain pin is enum class (#4108) 2022-04-28 17:32:39 -04:00
core8 Auto-generated configs and docs 2022-05-18 20:52:56 +00:00
f407-discovery
…
f429-discovery Brain pin is enum class (#4108) 2022-04-28 17:32:39 -04:00
frankenso Auto-generated configs and docs 2022-04-28 22:06:22 +00:00
hellen Auto-generated configs and docs 2022-05-23 05:22:14 +00:00
microrusefi reducing code duplication 2022-05-24 15:45:06 -04:00
nucleo_f767 Brain pin is enum class (#4108) 2022-04-28 17:32:39 -04:00
nucleo_h743 Brain pin is enum class (#4108) 2022-04-28 17:32:39 -04:00
prometheus Brain pin is enum class (#4108) 2022-04-28 17:32:39 -04:00
proteus reducing code duplication 2022-05-24 15:45:06 -04:00
subaru_eg33 OpenBLT: disable BOOT_CPU_USER_PROGRAM_START_HOOK for all supported boards (#4158) 2022-05-10 06:15:46 -04:00
tdg-pdm8 Auto-generated configs and docs 2022-05-18 04:16:08 +00:00
STM32F407VET6_Black.bat Brain pin is enum class (#4108) 2022-04-28 17:32:39 -04:00
STM32F407VET6_Mini.bat Brain pin is enum class (#4108) 2022-04-28 17:32:39 -04:00
clean_env_variables.bat
…
clean_env_variables.sh Export PROJECT_BOARD, we need it while compiling OpenBLT with separate make call (#4146) 2022-05-07 06:12:07 -04:00
common_make.bat
…
common_make.sh progress? 2022-05-10 10:51:56 -04:00
hellen_meta.h hellen meta 2022-05-23 00:20:41 -04:00
mre_meta.h Brain pin is enum class (#4108) 2022-04-28 17:32:39 -04:00
proteus_meta.h proteus meta 2022-05-04 17:00:38 -04:00
readme.md Update readme.md 2022-05-22 20:31:30 -04:00

readme.md

Boards Directory

rusEFI supports quite a wide array of hardware - we support stm32f4 and we support stm32h7, we have kinetis and we support cypress MCUs. We support on-board a number of smart GPIO chips, overall we support quite a wide array of hardware. With all those options our goal is to provide nice user experience which means upfront investment by board designer.

For best user experience we have more than a dozen of different binaries which are all compiled from same firmware files with different configuration. This folder is all about that process.

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 once you have new folder in this boards directory

  1. update gen_config.sh: add "board board" pair into 'for BOARD' iteration - this would produce new signature*.h file and new rusefi*.ini file

  2. update build-firmware.yaml to get new firmware bundle on https://rusefi.com/build_server/

  3. add connector pinout mapping yaml file see examples of yaml files in 'connectors' subfolders here.

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