mirror of https://github.com/FOME-Tech/fome-fw.git
1b07647e72
* s * science * set pin mode * turn stuff off so it fits * filtering maybe * filtering actually works * generate filter parameters internally * shorter window * guard behind enable flag * use checked in filter * add biquad reset * tracing * const * exec order * do it from a thread * smaller buffer, comment * configure with header * only for proteus * oops * unused * not needed * guards * pin config * don't need that include * precook filter steady state * define sample rate * config enable switch |
||
---|---|---|
.. | ||
frankenso | ||
me7_pnp | ||
microrusefi | ||
nucleo_f746 | ||
nucleo_f767 | ||
nucleo_h743 | ||
prometheus | ||
proteus | ||
st_stm32f4 | ||
STM32F407VET6_Black.bat | ||
STM32F407VET6_Mini.bat | ||
clean_env_variables.bat | ||
clean_env_variables.sh | ||
common_make.bat | ||
common_make.sh | ||
readme.md |
readme.md
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