Fix a minor issue where once the FILAMENT_EJECTED error screen is shown on the MK3S+, the LEDs will stay blinking red even after the user has removed the filament and clicked "Done". My proposal is to turn the LED off. Steps to reproduce: 1. Boot up printer and MMU in a clean state 2. MK3S+: on the LCD click "Load to Nozzle" 3. Once the loading is done, click "Unload filament" 4. Once unloading is done, click "Eject filament" 5. FILAMENT_EJECTED MMU error screen appears on the printer's UI 6. Remove the filament and select "Done". * Expected behavior: Blinking red LED turns off (or goes green). * Actual behavior: LED continous to blink red with no error screen. Change in memory: Flash: +16 bytes SRAM: 0 bytes |
||
|---|---|---|
| .vscode | ||
| cmake | ||
| lib | ||
| src | ||
| tests | ||
| utils | ||
| .clang-format | ||
| .cmake-format.py | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| CMakeLists.txt | ||
| Doxyfile | ||
| README.md | ||
| version.cmake | ||
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.