rusefi/firmware/config/boards
rusefillc 26fb3e60d4 pinout fix
only:alphax-8chan
2024-11-17 22:32:10 -05:00
..
Benelli_Walbro/connectors
GDI4
at_start_f435 saving the planet with some skip rates 2024-06-20 23:10:50 -04:00
atlas
core8
cypress only:dead 2024-09-06 19:05:43 -04:00
f407-discovery f407-discovery: fix mc33810 config 2024-09-25 00:36:34 -04:00
f429-208
f429-discovery
f469-discovery
frankenso_na6 fixing Frankenso build 2024-09-06 23:46:32 -04:00
hellen pinout fix 2024-11-17 22:32:10 -05:00
kinetis only:dead 2024-09-06 19:05:43 -04:00
lambda-x2
m74_9 saving the planet with some skip rates 2024-06-20 23:10:50 -04:00
microrusefi lua script to turn a rusEFI into an IO-BOX for another rusEFI #7075 2024-11-15 20:06:33 -05:00
nucleo_f413
nucleo_f429 saving the planet with some skip rates 2024-06-20 23:10:50 -04:00
nucleo_f767 only:default f767 build 2024-10-30 22:15:53 -04:00
nucleo_h743
prometheus aux serial/WBO cleanup/removal 2024-09-20 00:08:44 -04:00
proteus one step back 2024-11-11 20:57:12 -05:00
s105 only:getAnalogInputDividerCoefficient 2024-07-06 22:00:56 -04:00
subaru_eg33 subaru eg33: fix mc33810 config 2024-09-25 00:36:34 -04:00
tdg-pdm8
test-build-guards
STM32F407VET6_Black.bat
STM32F407VET6_Mini.bat
board_id.cpp mcFaultToString 2024-08-25 18:49:24 -04:00
board_id.h
common_script_read_meta_env.inc
hellen_meta.h only:datasheet 2024-11-14 17:05:54 -05:00
hellen_mm64_meta.h
hellen_mm100_meta.h only:datasheet 2024-11-14 17:05:54 -05:00
hellen_mm176_meta.h only:datasheet 2024-11-14 17:05:54 -05:00
mre_meta.h
proteus_meta.h
readme.md

readme.md

Boards Directory

TL,DR: for community edition see f407-discovery.

rusEFI supports quite a wide array of hardware:

  • most supported platforms are stm32f4 and stm32f7
  • alpha version support stm32h7
  • experimental support kinetis
  • experimental support cypress MCUs.

Looking for most default firmware for your own hardware? See f407-discovery

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_BOARD_NAME 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 changed 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

Q: I insist on custom

A: https://github.com/rusefi/rusefi/wiki/Custom-Firmware