Differences

This shows you the differences between two versions of the page.

--- rebuilding [2024/03/11 10:32] – torte
+++ rebuilding [2025/01/21 12:27] (current) – torte
@@ Line 1: / Line 1: @@
-===== Sovol KlipperScreen =====
+{{page>redirect#this_wiki_has_moved}}
-==== Rebuilding ====
+https://torte71.github.io/InsideSovolKlipperScreen/rebuilding.html
+{{page>redirect#section}}
+----
+====== Sovol KlipperScreen (Makerbase MKS KLIPAD50) ======
+===== Rebuilding =====
 Sovol's KlipperScreen is running on debian buster, which is outdated now, meaning you can no longer update system packages like ssh, etc.
@@ Line 8: / Line 13: @@
 There are recent images provided by Maxim Medvedev (redrathnure) on github, which can be used as a base:\\
 https://github.com/redrathnure/armbian-mkspi \\
-These images do not support the KLIPAD50's internal wifi, so you would have to use an USB-wifi(*) or USB-ethernet adapter instead. But the screen is working and spidev is available. It's spidev0.2 instead of spidev0.0, so adjust your printer.cfg accordingly.\\
+These images do not support the KLIPAD50's internal wifi out of the box, so you would either have to replace a devicetree file (see bottom of the page) or use external USB-wifi(*) or USB-ethernet adapters. But the screen is working and spidev is available. It's spidev0.2 instead of spidev0.0, so adjust your printer.cfg accordingly.\\
-(*) These adapters may require additional firmwares. You can try to install them with ''sudo apt update ; sudo apt install firmware-misc-nonfree'' if yours is not detected automatically)
+(*) These adapters may require additional firmwares. You can try to install them with ''sudo apt update ; sudo apt install firmware-misc-nonfree'' if yours is not detected automatically. On the other hand, this specific firmware package can break the internal wifi, even with the replaced dtb file.
 Steps to set up:
-=== Base system ===
+==== Base system ====
   - Select and download an image from https://github.com/redrathnure/armbian-mkspi/releases
@@ Line 34: / Line 39: @@
     * otherwise, choose the setting according to your location/needs
-=== Klipper ===
+==== Klipper ====
   - Log into device using ssh, putty or serial connection
   - cd into home dir: <code>cd</code>
@@ Line 107: / Line 112: @@
 (unless you've installed the wifi-enabled dtb below - in that case, it will be spidev0.0 again).
-=== Sovol mods ===
+==== Sovol mods ====
-  * List of [[sovol_mods]]
+Modifications from Sovol useful for this image:\\
+(See [[sovol_mods]] for details about the packages)
   * Beeps when pressing touchscreen
-    * Related files: [[makerbase-beep-files]]
     * Download: {{ :wiki:makerbase-beep-service.deb |}}
     * To install:
@@ Line 127: / Line 132: @@
       * ''sudo dpkg -r makerbase-beep-service''
-=== Internal wifi ===
+  * Automounting USB-drive
+    * Download: {{ :wiki:makerbase-automount-service.deb |}}
+    * Install/uninstall with ''dpkg -i''/''dpkg -r'' as shown above
-This is experimental and may not work for you.
+  * Powerloss recovery (plr)
+    * Unofficial package: {{ :wiki:plr-klipper.deb |}}
+    * Install/uninstall with ''dpkg -i''/''dpkg -r'' as shown above
+    * Sovol's {{https://github.com/Sovol3d/SOVOL_KLIPAD50_SYSTEM/tree/main/klipper_configuration|printer.cfg}} makes use of ''plr'', so it's recommended to either install this package, or remove these entries as shown [[sovol_mods#reverting|here]]
-The following change to the source of ''rk3328-roc-cc.dtb'' (Sovol's version) enables the internal wifi of the KLIPAD50 board.
+  * Splash screen
+    * Afaik it's not possible to directly use Sovols original boot animation, as it is in a different format (old kernel based vs. actual plymouth). The file resides in ''/usr/lib/firmware/bootsplash.armbian'' and is ~250MB big. I haven't found a way to decompile it into separate pictures - if someone does, it will probably be possible to "cook" a plymouth style boot animation from it.
+    * Enable plymouth splash screen:
+      * Become root: ''sudo su'' (enter password when asked)
+      * Edit ''/boot/armbianEnv.txt'' and change it to ''bootlogo=true''
+      * List available themes: ''plymouth-set-default-theme -l''
+      * Select a theme (e.g. "solar"): ''plymouth-set-default-theme solar ; update-initramfs -u''
+      * Restart the system: ''reboot''
+      * Themes are defined in ''/usr/share/plymouth/themes/''
+==== Internal wifi + spidev ====
+Replacing the dtb from the ''redrathnure'' image with Sovol's version of ''rk3328-roc-cc.dtb'' enables the internal wifi of the KLIPAD50 board, but does not create the spi device.
+With the following change, ''/dev/spidev0.0'' will be created as well.
 <code>
@@ Line 155: / Line 179: @@
 Additional notes:
-  * I had some performance issues with 6.7.5, not sure if that was just by chance.
+  * I had some wifi-performance issues with 6.7.5, not sure if that was just by chance.
   * The wlan0 device did not show up when "firmware-misc-nonfree" was installed. Reverting to ''armbian-firmware'' fixed this.
+  * To edit the dtb file on your own, use
+    * ''dtc -I dtb -O dts -o rk3328-roc-cc.dts rk3328-roc-cc.dtb'' to decompile it to source form and
+    * ''dtc -I dts -O dtb -o rk3328-roc-cc.dtb rk3328-roc-cc.dts'' to compile it back to binary form
   * The dtb files reside in the fat32 partition, you can easily replace them directly after writing the USB-stick or eMMC. So on the first boot you will automatically be asked to configure wifi. If you set it up using an USB-keyboard instead of a serial line, keep in mind that it uses US-keylayout when entering the passwords.
@@ Line 162: / Line 189: @@
 Download and replace ''/boot/dtb/rockchip/rk3328-roc-cc.dtb'' with this version and reboot.
+==== crowsnest / camera streaming ====
+  * The camera device will probably change after the update. Use ''v4l2-ctl --list-devices'' to check the available devices and change ''crowsnest.conf'' accordingly. (My camera now uses ''/dev/video3'')
+  * crowsnest may have problems initializing the camera after reboot. Workarounds:
+    * Manually restart crowsnest service (works reliably, but sucks)
+    * Add a pause to crowsnest initialization, as described in https://github.com/mainsail-crew/crowsnest/issues/117#issuecomment-1806943132
+      * Adding a pause made the startup more reliably, but still not always (tested 5 and 10 seconds)
+        * ''CROWSNEST_ARGS="-c /home/mks/printer_data/config/crowsnest.conf -s 10"''
+      * Make sure there aren't any backup copies of ''~/printer_data/systemd/crowsnest.env'', as they might override the new setting.
+----
+Back to [[start]]