Prusa-Firmware/README.md

119 lines
5.2 KiB
Markdown
Raw Normal View History

2018-10-05 15:47:02 +00:00
# Table of contents
<!--ts-->
2018-11-27 13:21:55 +00:00
* [Linux build](#linux)
* [Windows build](#windows)
2018-10-05 15:47:02 +00:00
* [Automated tests](#3-automated-tests)
* [Documentation](#4-documentation)
<!--te-->
2018-11-27 13:21:55 +00:00
# Build
## Linux
Run shell script build.sh to build for MK3 and flash with Sli3er.
2018-11-27 13:33:50 +00:00
If you have different printel model, follow step [2.b](#2b) from Windows build first.
If you wish to flash from Arduino, follow step [2.c](#2c) from Windows build first.
2018-11-27 13:21:55 +00:00
2018-11-27 13:33:50 +00:00
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](#2b) first for non-MK3 printers.
2018-11-27 13:21:55 +00:00
## Windows
### 1. Development environment preparation
2018-04-10 18:02:16 +00:00
2018-11-27 13:33:50 +00:00
a. install `"Arduino Software IDE"` for your preferred operating system
2018-04-10 18:02:16 +00:00
`https://www.arduino.cc -> Software->Downloads`
2019-01-08 21:25:32 +00:00
it is recommended to use version `"1.8.5"`, as it is used on out build server to produce official builds.
_note: in the case of persistent compilation problems, check the version of the currently used C/C++ compiler (GCC) - should be `4.8.1`; version can be verified by entering the command
`avr-gcc --version`
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_
2018-04-10 18:02:16 +00:00
_note: name collision for `"LiquidCrystal"` library known from previous versions is now obsolete (so there is no need to delete or rename original file/-s)_
2018-11-27 13:33:50 +00:00
b. add (`UltiMachine`) `RAMBo` board into the list of Arduino target boards
2018-04-10 18:02:16 +00:00
`File->Preferences->Settings`
into text field `"Additional Boards Manager URLs"`
type location
`"https://raw.githubusercontent.com/ultimachine/ArduinoAddons/master/package_ultimachine_index.json"`
or you can 'manually' modify the item
`"boardsmanager.additional.urls=....."`
at the file `"preferences.txt"` (this parameter allows you to write a comma-separated list of addresses)
_note: you can find location of this file on your disk by following way:
`File->Preferences->Settings` (`"More preferences can be edited in file ..."`)_
than do it
`Tools->Board->BoardsManager`
from viewed list select an item `"RAMBo"` (will probably be labeled as `"RepRap Arduino-compatible Mother Board (RAMBo) by UltiMachine"`
_note: select this item for any variant of board used in printers `'Prusa i3 MKx'`, that is for `RAMBo-mini x.y` and `EINSy x.y` to_
'clicking' the item will display the installation button; select choice `"1.0.1"` from the list(last known version as of the date of issue of this document)
_(after installation, the item is labeled as `"INSTALLED"` and can then be used for target board selection)_
2018-11-27 13:33:50 +00:00
c. modify platform.txt to enable float printf support:
2018-08-09 23:00:02 +00:00
add "-Wl,-u,vfprintf -lprintf_flt -lm" to "compiler.c.elf.flags=" before existing flag "-Wl,--gc-sections"
example:
2018-08-09 22:18:37 +00:00
`"compiler.c.elf.flags=-w -Os -Wl,-u,vfprintf -lprintf_flt -lm -Wl,--gc-sections"`
2018-04-10 18:02:16 +00:00
2018-11-27 13:21:55 +00:00
### 2. Source code compilation
2018-04-10 18:02:16 +00:00
2018-11-27 13:34:35 +00:00
a. place the source codes corresponding to your printer model obtained from the repository into the selected directory on your disk
2018-04-10 18:02:16 +00:00
`https://github.com/prusa3d/Prusa-Firmware/`
2018-11-27 13:21:55 +00:00
2018-11-27 13:33:50 +00:00
b.<a name="2b"></a> 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.
2018-11-27 13:21:55 +00:00
2018-11-27 13:33:50 +00:00
c.<a name="2c"></a> In file `"Firmware/config.h"` set LANG_MODE to 0.
2018-04-10 18:02:16 +00:00
run `"Arduino IDE"`; select the file `"Firmware.ino"` from the subdirectory `"Firmware/"` at the location, where you placed the source codes
`File->Open`
make the desired code customizations; **all changes are on your own risk!**
select the target board `"RAMBo"`
`Tools->Board->RAMBo`
_note: it is not possible to use any of the variants `"Arduino Mega …"`, even though it is the same MCU_
run the compilation
`Sketch->Verify/Compile`
upload the result code into the connected printer
`Sketch->Upload`
or you can also save the output code to the file (in so called `HEX`-format) `"Firmware.ino.rambo.hex"`:
`Sketch->ExportCompiledBinary`
and then upload it to the printer using the program `"FirmwareUpdater"`
_note: this file is created in the directory `"Firmware/"`_
# 3. Automated tests
## Prerequisites
c++11 compiler e.g. g++ 6.3.1
2018-06-11 20:17:51 +00:00
cmake
2018-06-11 20:17:51 +00:00
build system - ninja or gnu make
2018-06-11 20:17:51 +00:00
## Building
Create folder where you want to build tests.
2018-06-11 20:17:51 +00:00
Example:
2018-06-11 20:17:51 +00:00
`cd ..`
`mkdir Prusa-Firmware-test`
Generate build scripts in target folder.
2018-06-11 20:17:51 +00:00
Example:
2018-06-11 20:17:51 +00:00
`cd Prusa-Firmware-test`
`cmake -G "Eclipse CDT4 - Ninja" ../Prusa-Firmware`
2018-06-12 00:30:10 +00:00
or for DEBUG build:
`cmake -G "Eclipse CDT4 - Ninja" -DCMAKE_BUILD_TYPE=Debug ../Prusa-Firmware`
Build it.
2018-06-11 20:17:51 +00:00
Example:
2018-06-11 20:17:51 +00:00
`ninja`
## Runing
2018-06-12 15:30:10 +00:00
`./tests`
2018-10-05 15:47:02 +00:00
# 4. Documentation
2018-10-05 15:50:01 +00:00
run [doxygen](http://www.doxygen.nl/) in Firmware folder