Mirror of official Prusa firmware with custom changes.
Guðni Már Gilbert 13732f162b Fix build error when TMC2130_SERVICE_CODES_M910_M918 is enabled | 3 роки тому | |
---|---|---|
.github | 4 роки тому | |
Catch2 | 6 роки тому | |
Firmware | 2 роки тому | |
Tests | 4 роки тому | |
lang | 3 роки тому | |
tools | 3 роки тому | |
.editorconfig | 4 роки тому | |
.gitattributes | 4 роки тому | |
.gitignore | 3 роки тому | |
.travis.yml | 5 роки тому | |
CMakeLists.txt | 5 роки тому | |
LICENSE | 8 роки тому | |
MK404-build.sh | 3 роки тому | |
PF-build.sh | 3 роки тому | |
README.md | 3 роки тому | |
README_cz.md | 6 роки тому | |
build.sh | 3 роки тому | |
prepare_winbuild.ps1 | 5 роки тому | |
test.sh | 6 роки тому |
This repository contains the source code and the development versions of the firmware running on the Original Prusa i3 MK3S/MK3/MK2.5S/MK2.5 line of printers.
The latest official builds can be downloaded from Prusa Drivers. Pre-built development releases are also available here.
The firmware for the Original Prusa i3 printers is proudly based on Marlin 1.0.x by Scott Lahteine (@thinkyhead) et al. and is distributed under the terms of the GNU GPL 3 license.
Clone this repository and checkout the correct branch for your desired release version.
Set your printer model.
Install GNU AWK sudo apt-get install gawk
If you use mawk instead of gawk you get strange errors when multi language support is generated like:
awk: line 2: function strtonum never defined
sed: couldn't write 4 items to stdout: Broken pipe
./lang-build.sh: 121: ./lang-build.sh: arithmetic expression: expecting EOF: "0x"awk: line 2: function strtonum never defined
sed: couldn't write 4 items to stdout: Broken pipe
tr: write error: Broken pipe
./lang-build.sh: 121: ./lang-build.sh: arithmetic expression: expecting EOF: "0x"awk: line 2: function strtonum never defined
sed: couldn't write 4 items to stdout: Broken pipe
tr: write error: Broken pipe
tr: write error
cut: write error: Broken pipeNG! - some texts not found in lang_en.txt! updating binary:
primary language ids...awk: line 2: function strtonum never defined
sed: couldn't flush stdout: Broken pipe
Run ./build.sh
"PrusaFirmware/lang/firmware.hex"
. In the same folder you can hex files for other languages as well.Connect your printer and flash with PrusaSlicer ( Configuration --> Flash printer firmware ) or Slic3r PE.
Notes:
The script downloads Arduino with our modifications and Rambo board support installed, unpacks it into folder PF-build-env-\<version\>
on the same level, as your Prusa-Firmware folder is located, builds firmware for MK3 using that Arduino in Prusa-Firmware-build folder on the same level as Prusa-Firmware, runs secondary language support scripts. Firmware with secondary language support is generated in lang subfolder. Use firmware.hex for MK3 variant. Use firmware_\<lang\>.hex
for other printers. Don't forget to follow step 2.b first for non-MK3 printers.
Note: Multi language build is not supported.
a. Install "Arduino Software IDE"
from the official website https://www.arduino.cc -> Software->Downloads
It is recommended to use version "1.8.5"
, as it is used on out build server to produce official builds.
b. Setup Arduino to use Prusa Rambo board definition
"Additional Boards Manager URLSs"
add https://raw.githubusercontent.com/prusa3d/Arduino_Boards/master/IDE_Board_Manager/package_prusa3d_index.json
Tools->Board->Board manager
), and install Prusa Research AVR Boards by Prusa Research
c. Modify compiler flags in platform.txt
file
The platform.txt file can be found in Arduino installation directory, or after Arduino has been updated at: "C:\Users\(user)\AppData\Local\Arduino15\packages\arduino\hardware\avr\(version)"
If you can locate the file in both places, file from user profile is probably used.
Add "-Wl,-u,vfprintf -lprintf_flt -lm"
to "compiler.c.elf.flags="
before existing flag "-Wl,--gc-sections"
For example: "compiler.c.elf.flags=-w -Os -Wl,-u,vfprintf -lprintf_flt -lm -Wl,--gc-sections"
Notes:
In the case of persistent compilation problems, check the version of the currently used C/C++ compiler (GCC) - should be at leas 4.8.1
;
If you are not sure where the file is placed (depends on how "Arduino Software IDE"
was installed), you can use the search feature within the file system
Name collision for "LiquidCrystal"
library known from previous versions is now obsolete (so there is no need to delete or rename original file/-s)
a. Clone this repositoryhttps://github.com/prusa3d/Prusa-Firmware/
to your local drive.
b. In the subdirectory "Firmware/variants/"
select the configuration file (.h
) corresponding to your printer model, make copy named "Configuration_prusa.h"
(or make simple renaming) and copy it into "Firmware/"
directory.
c. In file "Firmware/config.h"
set LANG_MODE to 0.
d. Run "Arduino IDE"
; select the file "Firmware.ino"
from the subdirectory "Firmware/"
at the location, where you placed the source code File->Open
Make the desired code customizations; all changes are on your own risk!
e. Select the target board "Tools->Board->PrusaResearch Einsy RAMBo"
f. Run the compilation Sketch->Verify/Compile
g. Upload the result code into the connected printer Sketch->Upload
HEX
-format) "Firmware.ino.rambo.hex"
: Sketch->ExportCompiledBinary
and then upload it to the printer using the program "FirmwareUpdater"
"Firmware/"
notes: Script and instructions contributed by 3d-gussner. Use at your own risk. Script downloads Arduino executables outside of Prusa control. Report problems there. Multi language build is supported.
Tested versions are at this moment
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install zip
sudo apt-get install dos2unix
dos2unix PF-build.sh
to convert the windows line endings to unix line endings~/.bashrc
by running sudo nano ~/.bashrc
export OS="Linux" export JAVA_TOOL_OPTIONS="-Djava.net.preferIPv4Stack=true" export GPG_TTY=$(tty)
use CRTL-X
to close nano and confirm to write the new entries
PF-build.sh
script and compile your firmware correctlyC:\Users\<your-username>\Downloads\Prusa-Firmware-MK3
cd /mnt/c/Users/<your-username>/Downloads/Prusa-Firmware-MK3
to change to the right folder"$'\r': command not found"
errorapt-get install dos2unix
If your Windows isn't in English the Paths may look different Example in other languages
English /mnt/c/Users/<your-username>/Downloads/Prusa-Firmware-MK3
will be on a German Windows/mnt/c/Anwender/<your-username>/Downloads/Prusa-Firmware-MK3
open Ubuntu bash
change to your source code folder (case sensitive)
run ./PF-build.sh
follow the instructions
notes: Script and instructions contributed by 3d-gussner. Use at your own risk. Script downloads Arduino executables outside of Prusa control. Report problems there. Multi language build is supported.
Git-Bash
under Administrator privilegeln -s /c/Program\ Files/7-Zip/7z.exe zip.exe
If your Windows isn't in English the Paths may look different Example in other languages
/mnt/c/Users/<your-username>/Downloads/Prusa-Firmware-MK3
will be on a German Windows/mnt/c/Anwender/<your-username>/Downloads/Prusa-Firmware-MK3
English ln -s /c/Program\ Files/7-Zip/7z.exe zip.exe
will be on a Spanish Windows ln -s /c/Archivos\ de\ programa/7-Zip/7z.exe zip.exe
open Git-bash
change to your source code folder
run bash PF-build.sh
follow the instructions
Create a folder where you want to build tests.
Example:
cd ..
mkdir Prusa-Firmware-test
Generate build scripts in target folder.
Example:
cd Prusa-Firmware-test
cmake -G "Eclipse CDT4 - Ninja" ../Prusa-Firmware
or for DEBUG build:
cmake -G "Eclipse CDT4 - Ninja" -DCMAKE_BUILD_TYPE=Debug ../Prusa-Firmware
Build it.
Example:
ninja
./tests
run doxygen in Firmware folder or visit https://prusa3d.github.io/Prusa-Firmware-Doc for doxygen generated output
Q:I built firmware using Arduino and I see "?" instead of numbers in printer user interface.
A:Step 1.c was omitted or you updated Arduino and now platform.txt located somewhere in your user profile is used.
Q:I built firmware using Arduino and printer now speaks Klingon (nonsense characters and symbols are displayed @^#$&*°;~ÿ)
A:Step 2.c was omitted.
Q:What environment does Prusa use to build the firmware in the first place?
A:Our production builds are 99.9% equivalent to https://github.com/prusa3d/Prusa-Firmware#linux this is also easiest way to build as only one step is needed - run single script, which downloads patched Arduino from github, builds using it, then extracts translated strings and creates language variants (for MK2x) or language hex file for external SPI flash (MK3x). But you need Linux or Linux in virtual machine. This is also what happens when you open pull request to our repository - all variants are built by Travis http://travis-ci.org/ (to check for compilation errors). You can see, what is happening in .travis.yml. It would be also possible to get hex built by travis, only deploy step is missing in .travis.yml. You can get inspiration how to deploy hex by travis and how to setup travis in https://github.com/prusa3d/MM-control-01/ repository. Final hex is located in ./lang/firmware.hex Community reproduced this for Windows in https://github.com/prusa3d/Prusa-Firmware#using-linux-subsystem-under-windows-10-64-bit or https://github.com/prusa3d/Prusa-Firmware#using-git-bash-under-windows-10-64-bit .
Q:Why are build instructions for Arduino mess.
Y:We are too lazy to ship proper board definition for Arduino. We plan to switch to cmake + ninja to be inherently multiplatform, easily integrate build tools, suport more IDEs, get 10 times shorter build times and be able to update compiler whenever we want.