Rebuild v1.1.0 - Revision history

Elias: Pin the STM32 config download to the v1.1.0 tag; the file moves on main

2026-09-30T12:15:09Z

Pin the STM32 config download to the v1.1.0 tag; the file moves on main

← Older revision		Revision as of 12:15, 30 September 2026
Line 285:		Line 285:
	sudo -u printer -i		sudo -u printer -i
	cd ~/klipper		cd ~/klipper
	wget https://raw.githubusercontent.com/intelligent-agent/Rebuild/refs/~~heads~~/~~main~~/userpatches/overlay/klipper/stm32f031-32KB-serial.config		wget https://raw.githubusercontent.com/intelligent-agent/Rebuild/refs/tags/v1.1.0/userpatches/overlay/klipper/stm32f031-32KB-serial.config
	cp stm32f031-32KB-serial.config .config		cp stm32f031-32KB-serial.config .config
	make olddefconfig		make olddefconfig

Elias: Explain the debian and printer users, add hardening for v1.1.0, and use /home/printer/klipper in the build instructions

2026-09-29T20:47:13Z

Explain the debian and printer users, add hardening for v1.1.0, and use /home/printer/klipper in the build instructions

← Older revision		Revision as of 20:47, 29 September 2026
Line 126:		Line 126:
	SSH access is only enabled for user '''debian''' using the password '''temppwd'''.		SSH access is only enabled for user '''debian''' using the password '''temppwd'''.
	The first time you log in, you will be prompted to change the password. After the password has been changed, you will need to log in again. If you do not log in within an hour of enabling SSH, '''the SSH access will be disabled'''. This is for security reasons, it's not good to have an open SSH port with the default password. If the SSH access is disabled, it can be enabled again from the user interface.		The first time you log in, you will be prompted to change the password. After the password has been changed, you will need to log in again. If you do not log in within an hour of enabling SSH, '''the SSH access will be disabled'''. This is for security reasons, it's not good to have an open SSH port with the default password. If the SSH access is disabled, it can be enabled again from the user interface.

			===Two users: debian and printer===
			Since v1.1.0 Rebuild has two users, for security:
			* '''debian''' is the account you log in as, over SSH or the serial port. The first login forces you to change its default password.
			* '''printer''' runs Klipper, Moonraker and KlipperScreen. Klipper is in <code>/home/printer/klipper</code> and the configuration in <code>/home/printer/printer_data/config</code>.
			The printer software runs under its own account because a service cannot run under an account whose password has expired: Moonraker restarts services through <code>sudo</code>, and <code>sudo</code> refuses an expired account. The separate account is what makes the forced password change on '''debian''' possible.

			To work in Klipper's files, for example to install a Klipper plugin, log in as '''debian''' and switch to '''printer''':
			<pre>
			sudo -u printer -i
			</pre>
			Run the plugin's own commands there. Anything that needs <code>sudo</code>, such as <code>apt install</code> or restarting Klipper, is run as '''debian''': type <code>exit</code> to get back.

			====Recommended hardening on v1.1.0====
			In v1.1.0 the '''printer''' account can still log in with a password and belongs to the <code>sudo</code> group. It does not need either. Remove both once, logged in as '''debian''':
			<pre>
			sudo gpasswd -d printer sudo
			sudo passwd -l printer
			</pre>
			Klipper, Moonraker and KlipperScreen keep working: the rights they need do not depend on either. The next release of Rebuild will be built this way.

	==Serial port acccess==		==Serial port acccess==
Line 205:		Line 225:
	To configure klipper for AR100 and build the binary:		To configure klipper for AR100 and build the binary:
	<pre>		<pre>
	cd ~~/home/debian~~/klipper/		sudo -u printer -i
			cd ~/klipper
	cp test/configs/ar100.config .config		cp test/configs/ar100.config .config
	make olddefconfig		make olddefconfig
	make		make
			exit
	</pre>		</pre>

	This will produce a bin file located in out/ar100.bin, so it should be ~~moved~~ to /opt/firmware		This will produce a bin file located in out/ar100.bin, so it should be copied to /opt/firmware
	<pre>		<pre>
	mv out/ar100.bin /opt/firmware/		sudo cp /home/printer/klipper/out/ar100.bin /opt/firmware/
	</pre>		</pre>
	Once the AR100 binary has been updated, klipper.service can be restarted which then loads the new AR100 binary.		Once the AR100 binary has been updated, klipper.service can be restarted which then loads the new AR100 binary.
	<pre>		<pre>
	systemctl restart klipper		sudo systemctl restart klipper
	</pre>		</pre>

Line 245:		Line 267:
	In the olden days, we used to do it manually.		In the olden days, we used to do it manually.
	<pre>		<pre>
	cd ~~/home/debian~~/klipper		sudo -u printer -i
			cd ~/klipper
	cp test/configs/stm32f031.config .config		cp test/configs/stm32f031.config .config
	make menuconfig		make menuconfig
Line 260:		Line 283:
	In the newer days, you can copy the config that is used by Rebuild. Please note that this is for Recore A8, which has the 32 KB flash version of the STM32.		In the newer days, you can copy the config that is used by Rebuild. Please note that this is for Recore A8, which has the 32 KB flash version of the STM32.
	<pre>		<pre>
	cd ~~/home/debian~~/klipper		sudo -u printer -i
			cd ~/klipper
	wget https://raw.githubusercontent.com/intelligent-agent/Rebuild/refs/heads/main/userpatches/overlay/klipper/stm32f031-32KB-serial.config		wget https://raw.githubusercontent.com/intelligent-agent/Rebuild/refs/heads/main/userpatches/overlay/klipper/stm32f031-32KB-serial.config
	cp stm32f031-32KB-serial.config .config		cp stm32f031-32KB-serial.config .config
Line 267:		Line 291:
	</pre>		</pre>
	====Flashing STM32 firmware====		====Flashing STM32 firmware====
	To flash the STM32 firmware:		To flash the STM32 firmware, type <code>exit</code> to get back to '''debian''' first:
	<pre>		<pre>
	sudo mv /opt/firmware/stm32-32KB.bin /opt/firmware/stm32-32KB_old.bin		sudo mv /opt/firmware/stm32-32KB.bin /opt/firmware/stm32-32KB_old.bin
	sudo cp out/klipper.bin /opt/firmware/stm32-32KB.bin		sudo cp /home/printer/klipper/out/klipper.bin /opt/firmware/stm32-32KB.bin
	sudo flash-stm32		sudo flash-stm32
	</pre>		</pre>

Elias at 18:44, 18 September 2026

2026-09-18T18:44:03Z

← Older revision		Revision as of 18:44, 18 September 2026
Line 370:		Line 370:
	===A display connected after boot is not detected===		===A display connected after boot is not detected===
	The panel is driven from the framebuffer U-Boot set up, so the mode is whatever U-Boot read from the display's EDID at power-on. A display plugged in while the board is running will not be picked up - reboot with it connected. A different panel that is present at boot works normally, because U-Boot reads its EDID too. This is the trade for a flicker-free boot: there is no KMS and no runtime hotplug on this path.		The panel is driven from the framebuffer U-Boot set up, so the mode is whatever U-Boot read from the display's EDID at power-on. A display plugged in while the board is running will not be picked up - reboot with it connected. A different panel that is present at boot works normally, because U-Boot reads its EDID too. This is the trade for a flicker-free boot: there is no KMS and no runtime hotplug on this path.

	~~===Having both Ethernet and Wi-Fi creates problems with mDNS===~~
	~~When having both ethernet and Wi-Fi connected there can be a problem with hostname resolution.~~
	~~The workaround is to either remove Wi-Fi or ethernet.~~

Elias: Add what is new in v1.1.0; fix unclosed div, connector names for simpledrm, and two typos

2026-09-12T07:42:41Z

Add what is new in v1.1.0; fix unclosed div, connector names for simpledrm, and two typos

@@ Line 3: / Line 3: @@
 Rebuild has now been released as v1.1.0
 =Installing Rebuild on Recore=
-Recore has eMMC (embedded MMC), so in order to install sotware on the board, a USB drive must be used. For instructions on making a flasher image, have a look at [[Reflash]]
+Recore has eMMC (embedded MMC), so in order to install software on the board, a USB drive must be used. For instructions on making a flasher image, have a look at [[Reflash]]
 <div class="alert alert-warning">
 ===='''Note'''====
@@ Line 110: / Line 149: @@
 <div class="res-img">
 [[File:Mainsail.png]]
 ==Using KlipperScreen==
@@ Line 119: / Line 159: @@
 <pre>
 Section "Monitor"
-     Identifier "HDMI-1"
+     Identifier "None-1"
      Option "Rotate" "left"
 EndSection
 </pre>
 After that, KlipperScreen can be restarted.
 <pre>
@@ Line 237: / Line 282: @@
 The log for Klipper is located in /tmp. It can be viewed as:
 <pre>
-tail -f /tmk/klippy.log
+tail -f /tmp/klippy.log
 </pre>
@@ Line 256: / Line 301: @@
 [output]
 name=HDMI-A-1
 transform=rotate-90
 </pre>
 After that, Weston can be restarted.
 <pre>
@@ Line 317: / Line 368: @@
 == Known issues==
 ===Having both Ethernet and Wi-Fi creates problems with mDNS===
 When having both ethernet and Wi-Fi connected there can be a problem with hostname resolution.
 The workaround is to either remove Wi-Fi or ethernet.

Elias at 20:25, 7 September 2026

2026-09-07T20:25:21Z

← Older revision		Revision as of 20:25, 7 September 2026
Line 1:		Line 1:
	[[File:Rebuild header.png\|center]]		[[File:Rebuild header.png\|center]]
	Rebuild is a complete Linux image for [[Recore A8\|Recore]] 3D printer controller boards. Rebuild comes with Klipper installed and the choice of either [https://docs.mainsail.xyz/ MainSail], [https://docs.fluidd.xyz/ Fluidd] or [https://octoprint.org/ OctoPrint]. The name Rebuild is a reflection of the [https://www.armbian.com/ Armbian] build system, but adapted for Recore boards.		Rebuild is a complete Linux image for [[Recore A8\|Recore]] 3D printer controller boards. Rebuild comes with Klipper installed and the choice of either [https://docs.mainsail.xyz/ MainSail], [https://docs.fluidd.xyz/ Fluidd] or [https://octoprint.org/ OctoPrint]. The name Rebuild is a reflection of the [https://www.armbian.com/ Armbian] build system, but adapted for Recore boards.

	~~===Rebuild and Refactor===~~
	Rebuild and Refactor are very similar from a user standpoint, but the build system is different. Recore A7 and A6 come with some version of Refactor (v3.1.x), while Recore A8 comes with Rebuild (v1.0.x) pre-installed.

	Rebuild has now been released as v1.1.0		Rebuild has now been released as v1.1.0
Line 11:		Line 8:
	<div class="alert alert-warning">		<div class="alert alert-warning">
	===='''Note'''====		===='''Note'''====
	In order to install Rebuild v1.0.2, you need to use Reflash v1.0.1. There is a blog post explaining this new way to install an image on Recore: https://www.iagent.no/2024/05/08/reflash-a-new-way-to-upgrade-firmware/		In order to install Rebuild v1.1.0, you need to use Reflash v1.1.0. There is a blog post explaining this new way to install an image on Recore: https://www.iagent.no/2024/05/08/reflash-a-new-way-to-upgrade-firmware/
	</div>		</div>

Elias: Created page with "center Rebuild is a complete Linux image for Recore 3D printer controller boards. Rebuild comes with Klipper installed and the choice of either [https://docs.mainsail.xyz/ MainSail], [https://docs.fluidd.xyz/ Fluidd] or [https://octoprint.org/ OctoPrint]. The name Rebuild is a reflection of the [https://www.armbian.com/ Armbian] build system, but adapted for Recore boards. ===Rebuild and Refactor=== Rebuild and Refactor are ver..."

2026-09-07T20:23:49Z

Created page with "center Rebuild is a complete Linux image for Recore 3D printer controller boards. Rebuild comes with Klipper installed and the choice of either [https://docs.mainsail.xyz/ MainSail], [https://docs.fluidd.xyz/ Fluidd] or [https://octoprint.org/ OctoPrint]. The name Rebuild is a reflection of the [https://www.armbian.com/ Armbian] build system, but adapted for Recore boards. ===Rebuild and Refactor=== Rebuild and Refactor are ver..."

New page

[[File:Rebuild header.png|center]]
Rebuild is a complete Linux image for [[Recore A8|Recore]] 3D printer controller boards. Rebuild comes with Klipper installed and the choice of either [https://docs.mainsail.xyz/ MainSail], [https://docs.fluidd.xyz/ Fluidd] or [https://octoprint.org/ OctoPrint]. The name Rebuild is a reflection of the [https://www.armbian.com/ Armbian] build system, but adapted for Recore boards.

===Rebuild and Refactor===
Rebuild and Refactor are very similar from a user standpoint, but the build system is different. Recore A7 and A6 come with some version of Refactor (v3.1.x), while Recore A8 comes with Rebuild (v1.0.x) pre-installed.

Rebuild has now been released as v1.1.0

=Installing Rebuild on Recore=
Recore has eMMC (embedded MMC), so in order to install sotware on the board, a USB drive must be used. For instructions on making a flasher image, have a look at [[Reflash]]
<div class="alert alert-warning">
===='''Note'''====
In order to install Rebuild v1.0.2, you need to use Reflash v1.0.1. There is a blog post explaining this new way to install an image on Recore: https://www.iagent.no/2024/05/08/reflash-a-new-way-to-upgrade-firmware/
</div>

==Latest images==
The latest images for Recore are available from github. You can choose to download an image directly from within Reflash, or you can choose to download first and then upload it. Here are the latest images: https://github.com/intelligent-agent/Rebuild/releases

=Getting started=
[[File:USB-C.png|thumb]]
[[File:Ethernet.png|thumb]]
[[File:Blink.png|thumb]]
[[File:Http.png|thumb]]

It can be a good idea to test the board on the bench before installing it in the printer. Use the USB-C connector or the 24V power plug to power the board and connect the ethernet cable between the board and your local network.

Once power is applied, you should see a white LED light up in the middle of the board. After a few seconds, there should be activity on the eMMC LED, the CPU LED and on the heartbeat LED.

Once the board is powered up, use a computer to access the web interface provided by OctoPrint/MainSail/Fluidd (the UI).
In order to get access the UI, a network cable must be connected to the board and to a network switch. It is also possible to use a wifi dongle, be please see "Known issues" at the bottom of the page for issues regarding Hotspot/AP.
If a network cable is used, the board should respond to the address:
http://recore.local
If using a wifi dongle, the default wifi network password is 12345678.

For OctoPrint, once the interface is visible, run through the wizard to set up a new printer.
After the wizard is done, go to the Klipper tab in OctoPrint and edit the Klipper config file.
This is where the bulk of the work will happen.

On the MainSail or Fluidd image, there should not need to be any configuration necessary. Verify that the web interface comes up and that Klipper is running as expected.

== Klipper configuration ==
There is a standard klipper configuration file that comes with Refactor/Rebuild. The configuration file is set up
to work out of the box without anything connected on the pins of the board. The default Klipper config can be used as a starting point for building a custom config file for the printer at hand.

After the Klipper configuration is complete, do a test print to make sure everything is working.

<br clear=all>
<div class="alert alert-success">
===='''Important'''====
If you get in a situation where Klipper is unable to start normally, replace the content of the "printer.cfg" file with the default config file that came with Rebuild. The default config file should be available in the "config examples" folder in Fluidd and Mainsail. You might need to do a full reboot of the board after going back to that default config. This is a good way to get back to a known working image.
<div class="res-img">
[[File:Config-examples.png]]
</div>
</div>

==Wifi on Recore==
Recore does not have wifi built in, but wifi can be added by using a USB dongle. There is a great dual band wifi dongle that has been tested with Recore and Rebuild and should work out of the box [[Rexfer_A0]]. Wifi can be set up to be either an access point (Hotspot) or to connect to an existing access point (wifi router). If nothing is set, the default will be to create a wifi hotspot called "Recore" with password 12345678.

=== Wifi access point===
The first time Rebuild boots up, it will set up the wifi as an Access Point (AP). This is done by automatically changing the configuration of NetworkManager. The Wifi AP is called '''Recore''' and the password is '''12345678'''. This is meant as a temporary setup, so the password should be changed as soon as access is available. The default IP address for the AP is '''192.168.50.1'''. Once you have connected to the AP, either with a computer or a phone, it should be possible to gain ssh access.
<pre>
ssh debian@192.168.50.1
</pre>

=== Connecting to an external Wifi access point ===
If you have a Wifi dongle connected, you can connect to a local Wifi access point by using the '''nmtui''' program.

<div class="alert alert-success">
===='''Using nmtui'''====
nmtui is a Text UI tool to assist in managing network settings.
nmtui is mainly navigated using the arrow, space, enter, tab & escape keys.
</div>
# Use SSH or the serial port to log in to the device.
# Start '''nmtui'''
# Select Activate connection
# Select wifi network and enter credentials
# Exit nmtui and verify connection to the wifi network with '''ip addr''' (If you connect via wifi hotspot, you will be disconnected)

<div class="res-img">
[[File:Nmtui.gif]]

</div>

==SSH access==
Most of the configuration for Klipper can be handled via the UI, but sometimes it is necessary to have SSH access to the board. By default, the SSH access is disabled, but it can be enabled in three ways.
# You can choose "enable SSH on new image" in the Reflash user interface
# You can start the SSH service from Mainsail/Fluidd
# You can start the ssh service from the serial port. The ssh service will then be persistent on next boot. <pre>systemctl start ssh</pre>.
SSH access is only enabled for user '''debian''' using the password '''temppwd'''.
The first time you log in, you will be prompted to change the password. After the password has been changed, you will need to log in again. If you do not log in within an hour of enabling SSH, '''the SSH access will be disabled'''. This is for security reasons, it's not good to have an open SSH port with the default password. If the SSH access is disabled, it can be enabled again from the user interface.

==Serial port acccess==
The USB-C port can be used to get a serial port interface to the board. Once the board is connected and booted, you should be able to see the board show up as a USB device. The serial interface can be used with Minicom on Linux, and PuTTY on Windows.

===Upgrading Debian via apt upgrade===
The /boot partition of Rebuild is mounted "read only", so it will have to be remounted as Read Write before running an upgrade. This is handled automatically by apt in this version:
<pre>
sudo apt update
sudo apt upgrade
</pre>

=== Enable host mode on the USB-C connector ===
On Recore A7, the host mode for the USB C connector is activated using a device tree overlay. On A8, this is handled automatically.
To enable the host mode on Recore A7 write the following on the command line. First SSH into the board. Recore A6 and A5 can not operate in host mode with +5V output.
<pre>
sudo mount -o remount,rw /boot
sudo armbian-add-overlay /boot/overlay-user/sun50i-a64-usb-host.dts
sudo mount -o remount,ro /boot
</pre>

==Using Moonraker and Mainsail==
<div class="res-img">
[[File:Mainsail.png]]

==Using KlipperScreen==
KlipperScreen is running on X, so a new config should allow rotating the screen.
<pre>
sudo nano /usr/share/X11/xorg.conf.d/90-monitor.conf
</pre>
Add the following:
<pre>
Section "Monitor"
Identifier "HDMI-1"
Option "Rotate" "left"
EndSection
</pre>
After that, KlipperScreen can be restarted.
<pre>
sudo systemctl restart KlipperScreen
</pre>

If it is necessary to rotate the touch panel as well, here is a useful section that can be added to the bottom of that same file. Uncomment the rotation that matches your setup.
<pre>
Section "InputClass"
Identifier "Coordinate Transformation Matrix"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
MatchDriver "libinput"
Option "CalibrationMatrix" "1 0 0 0 1 0 0 0 1" # 0 degrees
#Option "CalibrationMatrix" "0 1 0 -1 0 1 0 0 1" # 90 degrees
#Option "CalibrationMatrix" "-1 0 1 0 -1 1 0 0 1" # 180 degrees
#Option "CalibrationMatrix" "0 -1 1 1 0 0 0 0 1" # 270 degrees

EndSection
</pre>

==Recompiling and installing binaries==
===Update u-boot on Recore===
This is not something the regular user would need to do, but documented here for convenience.
Place u-boot-sunxi-with-spl.bin in sector 15 (8KB offset)
Flash the binary
<pre>
dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk2 bs=1024 seek=8 conv=notrunc
</pre>

===AR100 firmware===
The AR100 CPU needs a binary file that is loaded on startup by the systemd file klipper.service
The AR100 binary file comes pre-compiled in Refactor, so most users should not have to re-compile it.
For experiments the AR100 binary can be recompiled on Recore (architecture aarch64) or on a host computer (amd64 or similar).

====Compiling the ar100 binary====
To configure klipper for AR100 and build the binary:
<pre>
cd /home/debian/klipper/
cp test/configs/ar100.config .config
make olddefconfig
make
</pre>

This will produce a bin file located in out/ar100.bin, so it should be moved to /opt/firmware
<pre>
mv out/ar100.bin /opt/firmware/
</pre>
Once the AR100 binary has been updated, klipper.service can be restarted which then loads the new AR100 binary.
<pre>
systemctl restart klipper
</pre>

====Cross compilation toolchain for ARM64====
The AR100 needs a cross compilation toolchain. For ARM64, it can be downloaded from feeds.iagent.no:

http://feeds.iagent.no/toolchains/

The toolchain has been built with

https://github.com/richfelker/musl-cross-make

GCC version: 11.2.0

====Cross compilation toolchain for x86_64====
The toolchain used during automatic testing and is the same used for the CRUST firmware project:

https://github.com/crust-firmware/crust#building-the-firmware

===STM32 firmware===

The firmware for the stm32f031 mcu that is responsible for ADC
conversions and PWM for heaters and fans comes pre-installed in the flash of the MCU.
It can be recreated on the board using the Klipper build system.

In the olden days, we used to do it manually.
<pre>
cd /home/debian/klipper
cp test/configs/stm32f031.config .config
make menuconfig
-> Enable extra low-level configuration options
-> Processor model (STM32F031)
-> Bootloader offset (No bootloader)
-> Clock Reference (Internal clock)
-> (16) Internal clock trim override
-> Communication interface (Serial (on USART2 PA15/PA14))
-> Baud rate for serial port: 250000
make
</pre>

In the newer days, you can copy the config that is used by Rebuild. Please note that this is for Recore A8, which has the 32 KB flash version of the STM32.
<pre>
cd /home/debian/klipper
wget https://raw.githubusercontent.com/intelligent-agent/Rebuild/refs/heads/main/userpatches/overlay/klipper/stm32f031-32KB-serial.config
cp stm32f031-32KB-serial.config .config
make olddefconfig
make
</pre>
====Flashing STM32 firmware====
To flash the STM32 firmware:
<pre>
sudo mv /opt/firmware/stm32-32KB.bin /opt/firmware/stm32-32KB_old.bin
sudo cp out/klipper.bin /opt/firmware/stm32-32KB.bin
sudo flash-stm32
</pre>

===Running Klipper===
Klipper is run as a systemd service. It should not normally need to be restarted from the command line, but during development it can be necessary.
<pre>
systemctl restart klipper
</pre>

The log for Klipper is located in /tmp. It can be viewed as:
<pre>
tail -f /tmk/klippy.log
</pre>

Klipper can also be restarted from the OctoPrint interface. On the "Klipper" tab, press "Firmware" to restart the Klipper firmware.
<div class="res-img">
[[File:Klipper-firmware-press.png]]
</div>

===Running Toggle===
Toggle is started automatically by the systemd service toggle.service. A user is created for Toggle on first boot, but the credentials are not set until a user is created in OctoPrint. Once the wizard has been completed, the Toggle user is active, but the credentials will not be valid until OctoPrint is restarted. Therefore, if Toggle is needed, restart OctoPrint after the wizard is complete.

Toggle is running on Weston, so a new config should allow rotating the screen.
<pre>
sudo nano /etc/xdg/weston/weston.ini
</pre>
Edit the section about rotation:
<pre>
[output]
name=HDMI-A-1
transform=rotate-90
</pre>
After that, Weston can be restarted.
<pre>
sudo systemctl restart weston
</pre>

See the Ubuntu documentation for valid rotations: [https://manpages.ubuntu.com/manpages/jammy/man5/weston.ini.5.html weston.ini]
== Recore booting ==
There are several stages to booting Recore, and depending on which media is installed, the boot process will
try and boot either from eMMC, USB host or USB device (FEL).

The board can be booted by either pressing the "BOOT" button for 2 seconds or by applying power to either the 24V connector or the USB C connector. To shut down the board, either use the "shutdown" button from the UI or press the "BOOT" button once. It's not ideal to shut off the board by removing power directly as this can cause a corrupted file system.

<tabs>
<tab name="From eMMC">
===Booting Recore from eMMC (the normal way)===
# Turn on power
# The BROM will load u-boot SPL from eMMC
# The u-boot SPL will load u-boot
# u-boot will load Linux
# Linux will load the rootfs from eMMC.
</tab>
<tab name="From USB">
===Loading u-boot from eMMC but load kernel and rootfs from USB===
Starting with Rebuild v1.0.0, u-boot will do a scan for a USB mass storage device and if a working version of Reflash or Rebuild or Refactor is found, it will boot to that image.
# Download Refactor/Rebuild/Reflash and flash it to a USB drive.
# Insert the USB drive in the board.
# Boot the board normally (Use the Boot button/apply power)
The board should now be have the kernel/rootfs from the USB drive.
</tab>
<tab name="From FEL">
===Boot Recore from a USB stick using the FEL button===
If u-boot should be loaded from a host computer and kernel and rootfs is loaded from a USB drive:
# Flash the [[Reflash]] Linux distro to a USB drive.
# Insert the USB drive in the Recore board in one of the two host connectors close to the HDMI.
# Hold down the FEL button while applying power to the board via the USB-C connector.
# Download the Recore repository https://github.com/intelligent-agent/Recore
# Install the sunxi-tools program
# Run the fel command ('''make fel''') from the host computer. All the necessary binarys are in the Recore repository:
You can read more about the steps needed to boot aboard in FEL mode on the Sunxi wiki: https://linux-sunxi.org/FEL

'''Note:''' Depending on what linux platform you're running from, sunxi-tools will require the following dependencies to compile properly:
* libftd-dev
* libusbx-dev
* libudev-dev
(These are Debian/ubuntu names. For Fedora, change -dev to -devel)

This should upload u-boot from the host computer to the board via the USB cable. u-boot will then boot from the connected USB drive.
Please note that in some instances, the USB drive is not detected as a mass storage device without also having the VIN power connector inserted. See more in [[Recore_A6#USB_connectors_not_discovered_when_powered_by_USB_device|in the "known errors" section of Recore A6]]
</tab>
</tabs>

===Running OctoPrint===
OctoPrint is stated on boot. If there is a need to restart the daemon, use this command
<pre>
systemctl restart octoprint
</pre>

== Known issues==
===Having both Ethernet and Wi-Fi creates problems with mDNS===
When having both ethernet and Wi-Fi connected there can be a problem with hostname resolution.
The workaround is to either remove Wi-Fi or ethernet.