updating
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| updating [2024/01/28 10:34] – created torte | updating [2025/02/19 09:31] (current) – torte | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Sovol KlipperScreen ===== | + | {{page> |
| + | https:// | ||
| + | {{page> | ||
| + | ---- | ||
| + | |||
| + | ===== Sovol KlipperScreen | ||
| ==== Updating ==== | ==== Updating ==== | ||
| + | * see also: https:// | ||
| + | |||
| === Update Manager === | === Update Manager === | ||
| === Problems === | === Problems === | ||
| - | * Host | ||
| - | * Printer (" | ||
| - | * Secondary MCU ("mcu rpi") | ||
| + | == System / Kernel (black screen) == | ||
| + | < | ||
| + | - Updating " | ||
| + | (sometimes even breaks wifi-access) | ||
| + | Cause: Stock armbian kernels are incompatible with KlipperScreen | ||
| + | - kernel on KlipperScreen is linux-5.16.20-rockchip64 (Version: 22.05.0-trunk) | ||
| + | - This kernel is not found on the armbian servers (latest version: 5.16.11-rockchip64) | ||
| + | - All later kernels are incompatible: | ||
| + | - "/ | ||
| + | - my guess: might have to do with the devicetree files | ||
| + | Temporary fix: | ||
| + | - Revert to old kernel | ||
| + | Image location: see https:// | ||
| + | a) Re-flash (kills all prior settings) | ||
| + | - Find image online (armbian-update.deb) | ||
| + | - Flash via USB-stick | ||
| + | b) Revert just kernel (keeps settings) | ||
| + | - upload armbian-update.deb to your klipperscreen | ||
| + | e.g. using the web-frontend: | ||
| + | (or use scp or whatever for uploading) | ||
| + | - use ssh/putty to log into your klipperscreen | ||
| + | - change into the directory where you uploaded armbian-update.deb to | ||
| + | for the mainsail example: "cd ~/ | ||
| + | - Extract kernel package: | ||
| + | " | ||
| + | - install (downgrade) kernel: | ||
| + | " | ||
| + | - install (downgrade) the dtb: | ||
| + | " | ||
| + | - Keep that kernel-version (choose one of the following options): | ||
| + | a) don't update " | ||
| + | b) keep just that kernel-version (allows updating " | ||
| + | - "sudo apt-mark hold linux-image-edge-rockchip64 linux-dtb-edge-rockchip64" | ||
| + | c) freeze the kernel using " | ||
| + | (see https:// | ||
| + | </ | ||
| + | |||
| + | |||
| + | == Klipper-0.12.80+ (secondary mcu update) == | ||
| + | < | ||
| + | - Compiling klipper for " | ||
| + | # cd klipper | ||
| + | # make menuconfig | ||
| + | - select " | ||
| + | # make clean ; make ; make flash | ||
| + | - ("make flash" replaces "/ | ||
| + | - Compiling klipper for "mcu linux" | ||
| + | (as from https:// | ||
| + | # cd klipper | ||
| + | # make menuconfig | ||
| + | - change settings (" | ||
| + | = Enable extra low-level configuration options: [*] | ||
| + | = Micro-controller Architecture: | ||
| + | * Processor model: STM32F103 | ||
| + | * Disable SWD at startup (for GigaDevice stm32f103 clones): [*] | ||
| + | * Bootloader offset: 28KiB bootloader | ||
| + | = Clock Reference: 8 MHz crystal | ||
| + | * Communication interface: Serial (on USART1 PA10/PA9) | ||
| + | = Baud rate for serial port: 250000 | ||
| + | # make clean ; make | ||
| + | - copy " | ||
| + | !!! use a different name than that from prior updates !!! | ||
| + | </ | ||
| + | |||
| + | |||
| + | == Armbian Buster: End Of Life == | ||
| + | Sovol' | ||
| + | The repositories for this version have been taken offline in spring 2024. | ||
| + | * Updating the system packages using apt (e.g. '' | ||
| + | * The missing system updates make it more and more difficult updating the Klipper components. E.g. recent " | ||
| + | * At least one can not accidentally brick the device by updating the kernel or .dtb files any longer, as these files simply do not exist any longer. | ||
| + | * It is possible to flash a recent Armbian version, but it takes more than just a few mouseclicks.\\ See these guides: | ||
| + | * Rebuilding from scratch using Maxim' | ||
| + | * My guide: [[rebuilding|Rebuilding]] | ||
| + | * Vasyl' | ||
| + | * You can also find a readily prepared image (built as on my guide) here: [[image|Image]] | ||
| + | |||
| + | |||
| + | == KlipperScreen / Python 3.8 == | ||
| + | The last version of KlipperScreen that works with python 3.7 is v0.4.1. | ||
| + | I guess the easiest fix is resetting KlipperScreen to that revision and never updating it afterwards. That means: | ||
| + | * Log into the KlipperScreen using SSH or Putty and enter the following commands: | ||
| + | * '' | ||
| + | * '' | ||
| + | (I haven' | ||
| + | |||
| + | Other options are: | ||
| + | * Revert the whole system to its original state by flashing the emmc card with Sovol' | ||
| + | * Flash a recent armbian image to the emmc card (then you can update afterwards). | ||
| + | * Maybe its possible to manually download, compile and install python 3.8, but I'd expect many issues with that (possibly missing dependencies, | ||
| + | |||
| + | |||
| + | == Moonraker Timelapse == | ||
| + | The moonraker timelapse script has a dependency check at the starts, which prevents the installation on the outdated Armbian buster version. | ||
| + | By removing that check, it should be possible to install the timelapse script. | ||
| + | See Gergo' | ||
| + | |||
| + | |||
| + | ---- | ||
| + | Back to [[start]] | ||
updating.1706434493.txt.gz · Last modified: 2024/01/28 10:34 by torte
