forked from mainsail-crew/MainsailOS
-
-
Notifications
You must be signed in to change notification settings - Fork 113
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
6aa78eb
commit be9f620
Showing
8 changed files
with
96 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,7 +5,7 @@ | |
|
||
## Firmware installation | ||
|
||
Move the firmware.bin file from the release page to the SD card that goes into your control board, and insert the SD card in to the control board. | ||
Move the `firmware-octopus-11.bin` file from the release page to the SD card that goes into your control board and call it `firmware.bin`, then insert the SD card in to the control board. | ||
|
||
### Firmware installation without an SD-Card | ||
Another option is to jump the boot0 pins on the board, and click the reset button. Then SSH into the pi using something like PuTTy or `ssh [email protected]` via the commandline on OS X and Linux machines. Execute `~/klipper_config/config/boards/btt-octopus-11/make-and-flash-mcu.sh` and the Pi will compile the klipper firmware and flash the board for you. When done, power off the board and remove the boot0 jumper. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,11 @@ | ||
test | ||
# Big Tree Tech SKR Pro V1.2 | ||
?> This page is incomplete, please refer to the [official V-Core 3 wiring diagram](https://v-core.ratrig.com/electronics/#skr-pro-12) and [V-CoreOS setup](https://v-core.ratrig.com/firmware/#v-coreos-klipper-firmware) for the time being. | ||
|
||
## Firmware installation | ||
|
||
Move the `firmware-skr-pro-12.bin` file from the release page to the SD card that goes into your control board and call it `firmware.bin`, then insert the SD card in to the control board. | ||
|
||
## Compiling and flashing the newest firmware via USB | ||
!> Requires an SD card in your SKR Pro 1.2. | ||
|
||
To compile and flash the newest firmware to the board, you need to SSH into the pi using something like PuTTy or `ssh [email protected]` via the commandline on OS X and Linux machines. Execute `~/klipper_config/config/boards/btt-skr-pro-12/make-and-flash-mcu.sh` and the Pi will compile the klipper firmware and flash the board for you. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
# Manual klipper firmware compilation | ||
?> If you don't know what SSH is or how to use the commandline, consider following the instructions for your specific boards instead. There are easier ways to do this. | ||
|
||
If you need to compile the firmware for your board yourself, here's how you do it. | ||
|
||
## SSH into the Raspberry Pi | ||
You're need to log into the Pi via SSH. The default username is `pi` and the password is `raspberry` (sidenote: it's a good idea to change this via `sudo raspi-config`). If you're on linux or Mac OS, you can do this by opening a terminal and type: | ||
```bash | ||
ssh [email protected] | ||
``` | ||
|
||
Now navigate to the klipper directory: | ||
|
||
```bash | ||
cd ~/klipper | ||
``` | ||
|
||
The configuration klipper needs to compile the firmware for your board is stored in `~/klipper_config/config/boards/[BOARD_NAME]/firmware.config`. To list the board names execute the following command: | ||
|
||
```bash | ||
ls -la ~/klipper_config/config/boards | ||
``` | ||
|
||
Let's say we need to compile the firmware for the octopus. We then need to copy the configuration file from `~/klipper_config/config/boards/btt-octopus-11/firmware.config` | ||
|
||
```bash | ||
cp -f ~/klipper_config/config/boards/btt-octopus-11/firmware.config ~/klipper/.config | ||
``` | ||
|
||
Now we're ready to compile the firmware! | ||
|
||
```bash | ||
make olddefconfig | ||
make clean | ||
make | ||
``` | ||
|
||
## Download the firmware from the Pi | ||
Now klipper has compiled it's firmware to `~/klipper/out/klipper.bin`. We can download that to our machine via `scp` or [WinSCP](https://winscp.net/eng/download.php) (for windows users). | ||
|
||
Linux and Mac OS users can use scp from their local machines like this: | ||
|
||
```bash | ||
scp [email protected]:klipper/out/klipper.bin firmware.bin | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters