Go to file
Yuri D'Elia 392298c3da Uniform gcc-avr => avr-gcc for consistency 2022-07-27 17:04:52 +02:00
.vscode Add the AvrGcc toolchain to lock gcc version 2022-07-27 17:04:52 +02:00
cmake Uniform gcc-avr => avr-gcc for consistency 2022-07-27 17:04:52 +02:00
lib USB cdc stdout stream 2021-10-14 14:27:56 +02:00
src Upgrade build system to gcc 7.3 2022-07-27 17:04:52 +02:00
tests Unit test ErrDisengageIdler: make sure it never sets error while disengaging 2022-07-20 16:23:43 +02:00
utils Uniform gcc-avr => avr-gcc for consistency 2022-07-27 17:04:52 +02:00
.clang-format Disable preprocessor code indentation 2021-07-07 16:33:03 +02:00
.cmake-format.py Prepare parts of the build system 2021-04-19 07:03:47 +02:00
.gitignore Prepare parts of the build system 2021-04-19 07:03:47 +02:00
.pre-commit-config.yaml Add lufa to pre-commit's exception list 2021-09-06 15:56:43 +02:00
CMakeLists.txt Fix filename passing to hex modifier 2022-07-27 17:04:52 +02:00
Doxyfile Update doxyfile + document modules namespace 2021-06-30 07:39:31 +02:00
README.md Uniform gcc-avr => avr-gcc for consistency 2022-07-27 17:04:52 +02:00
version.txt Update vscode settings 2022-07-27 17:04:52 +02:00

README.md

Prusa-Firmware-MMU-Private

How to prepare build env and tools

Run ./utils/bootstrap.py

bootstrap.py will now download all the "missing" dependencies into the .dependencies folder:

  • clang-format-9.0.0-noext
  • cmake-3.22.5
  • ninja-1.10.2
  • avr-gcc-7.3.0

How to build the preliminary project so far:

Now the process is the same as in the Buddy Firmware:

./utils/build.py

builds the firmware.hex in build/mmu_release

In case you'd like to build the project directly via cmake you can use an approach like this:

mkdir build
cd build
cmake .. -G Ninja -DCMAKE_TOOLCHAIN_FILE=../cmake/AvrGcc.cmake
ninja

Should produce a MM-control-01.hex file as well.