Michal
/
Prusa-Firmware-MMU
mirror of https://github.com/prusa3d/Prusa-Firmware-MMU
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
824 Commits
5 Branches
5 Tags
8.1 MiB
C 64%
C++ 29%
CMake 2.2%
Python 2.1%
Makefile 1.9%
Other 0.7%
 
 
 
 
 
 
Go to file
D.R.racer 93a344bde8 Push the compiler into the optimization 
It looks like copying the RegisterRec into a local variable (as it has been here before)
seems to confuse the compiler which then refuses to optimize the calls.
With this simple tweak the code is actually 8B shorter than before (while retaining the saved ~170B of RAM)
 		2023-08-10 08:11:52 +02:00
.vscode Sync with MK3 2022-12-18 17:41:22 +00:00
cmake cmake: Uniform Avr toolchain build with MK3 2022-10-17 17:26:08 +02:00
lib catch2: Fix build with gcc13 2023-07-24 12:38:44 +02:00
src Push the compiler into the optimization 2023-08-10 08:11:52 +02:00
tests CircularIndex: add tests for non-power-of-two sizes 2023-07-28 15:48:14 +02:00
utils Update build server config 2023-07-13 16:24:06 +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 hooks: Update cmake-format to 0.6.13 2022-10-10 11:50:05 +02:00
CMakeLists.txt Fix bootloader file generation 2022-11-15 10:43:34 +01:00
Doxyfile Update doxyfile + document modules namespace 2021-06-30 07:39:31 +02:00
README.md README: Mention the correct output filename 2022-07-27 17:04:52 +02:00
version.cmake Tag 2.1.9 as 3.0.0 2023-07-20 10:28:58 +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

It will produce a MMU2SR_<version>.hex file.