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
Matthew Kennedy f1a1637a0a nb1 too 2025-03-21 17:03:48 -07:00
..
Benelli_Walbro/connectors update interactive-pinout, update yamls (#5049) 2023-02-10 05:01:05 -05:00
GDI4 update interactive-pinout, update yamls (#5049) 2023-02-10 05:01:05 -05:00
atlas experimental SD card bootloader 2025-03-17 01:44:45 -07:00
core8 move SHORT_BOARD_NAME in to a makefile variable #300 2023-11-07 12:47:24 -08:00
core48 CAN guards cleanup 2025-01-10 21:54:45 -08:00
f407-discovery why did discovery have i2c enabled 2024-11-19 14:34:54 -08:00
f429-discovery move SHORT_BOARD_NAME in to a makefile variable #300 2023-11-07 12:47:24 -08:00
frankenso batch files clogging the world 2023-02-22 15:12:50 -08:00
hellen nb1 too 2025-03-21 17:03:48 -07:00
lambda-x2 update interactive-pinout, update yamls (#5049) 2023-02-10 05:01:05 -05:00
microrusefi dead L9779 driver 2025-03-03 01:03:44 -08:00
nucleo_f429 ethernet console as engine module (#453) 2024-07-23 20:52:37 -07:00
nucleo_f767 all ECUs can use big blocking factor! (#474) 2024-08-30 22:48:37 -07:00
nucleo_h743 H743 nucleo build 2024-12-24 17:45:46 -08:00
prometheus aux serial cleanup/removal #61 2024-09-18 22:38:16 -07:00
proteus enable proteus spi and max31855 egt (#563) 2025-03-07 12:06:51 -08:00
subaru_eg33 dead L9779 driver 2025-03-03 01:03:44 -08:00
tdg-pdm8 update interactive-pinout, update yamls (#5049) 2023-02-10 05:01:05 -05:00
common_make.bat
…
common_make.sh fail on error 2025-03-06 12:30:19 -08:00
hellen_meta.h we often mean inline when we say static 2024-03-28 18:20:40 -07:00
mre_meta.h fix MRE 2023-11-03 15:18:47 -07:00
proteus_meta.h fix proteus 2023-11-03 15:14:17 -07:00
readme.md no qc 2023-02-22 14:53:31 -08: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 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

FAQ

Q: how do I change Primary UART pins via TS?

A: Primary UART, critical error LED pin and maybe a couple more of the most fundamental pins could NOT be chagned via TS. You would need another binary altogether - either another official binary or a custom binary.

Q: I need more info!

A: please remember about https://github.com/rusefi/rusefi/wiki/Hardware#q-this-is-all-very-cool-but-you-guys-do-not-have-a-plugplay-for-my-trabant-i-think-i-will-go-and-make-a-new-rusefi-board-just-for-my-trabant