f0cf4f38ff
* carve out UART specific * implement channel * config cleanup * use new config * bootloader * dead code * s * h7 inherits f7 * oops * ok now it's right * tests * cleanup * call setup * put that in its own file * cleanup * format * guard * not needed * improve guarding * portable * allow override of uart mode * fixes for bootloader Co-authored-by: Matthew Kennedy <makenne@microsoft.com> |
||
|---|---|---|
| .. | ||
| frankenso | ||
| hellen | ||
| kinetis | ||
| me7_pnp | ||
| microrusefi | ||
| nucleo_f767 | ||
| nucleo_h743 | ||
| prometheus | ||
| proteus | ||
| skeleton | ||
| st_stm32f4 | ||
| subaru_eg33 | ||
| STM32F407VET6_Black.bat | ||
| STM32F407VET6_Hellen_STM.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