mirror of
https://github.com/Klipper4FlashForge/firmware.git
synced 2026-10-22 05:12:16 -05:00
Oleksandr Shyshatskyi
12bbd1e7dc
The probe profile was a bring-up aid. It set BUILD_APPLY=0, reinstalled the stock component byte-for-byte and wrote a report to the stick, so you could prove the update chain worked on your own machine -- the filename glob, the DES3 key, the md5 gate, run.sh execution -- before flashing anything that changed a file. That rehearsal has served its purpose. With it gone there was exactly one profile left, so the whole PROFILE indirection goes too: profiles/ is deleted and its six BUILD_* flags are plain defaults in bin/common.sh, which also means config.env now overrides them instead of being silently overridden. make default folds into make build; all-profiles and RECOVERY_PROFILE are gone with it. What is NOT gone is the undo button: flashing the stock FlashForge package still restores every file the mod touches, and case-recovery.sh still proves it. What is gone is the dry run. Note the loss: PROG_MB/DATA_MB used to come out of the probe report. The docs now point at df -h over ssh, which you only have after a successful flash.
46 lines
2.1 KiB
Bash
46 lines
2.1 KiB
Bash
# creator5-custom-firmware -- TEST configuration
|
|
#
|
|
# cp test.env.example test.env
|
|
#
|
|
# Nothing in this file ever reaches a printer. It configures the replica --
|
|
# the printer's real rootfs under qemu-mipsel -- and nothing else. Build
|
|
# inputs and anything that ships live in config.env.
|
|
|
|
# ---- a prebuilt replica image (START HERE) ---------------------------------
|
|
# The fastest and simplest way to run the replica tests: an image that already
|
|
# carries the printer's rootfs, its real /usr/prog and /usr/data, AND the
|
|
# stock package installed on top of them. With it a replica run starts in
|
|
# under a second and PROG_DUMP below is not needed at all.
|
|
#
|
|
# Without it every run unpacks the 182MB factory image (~22s) and installs the
|
|
# stock package under qemu (~37s) before the test even begins.
|
|
#
|
|
# Built by test/build-printer-image.sh. It contains proprietary FlashForge
|
|
# firmware.
|
|
PRINTER_IMAGE="monstrofil/creator5-printer:latest"
|
|
|
|
# ---- the replica's /usr/prog and /usr/data ---------------------------------
|
|
# Only needed when PRINTER_IMAGE is empty -- the image has this baked in.
|
|
# Otherwise REQUIRED for every test that runs inside the replica. It is the factory
|
|
# image -- the printer's real /usr/prog and /usr/data, giving the replica the
|
|
# genuine klipper daemons, nginx, python3, checkEboard, moonraker and, most
|
|
# usefully, the printer's own OpenSSL 1.0.2d, so package decryption is
|
|
# verified against the real implementation. There are no stubs: if this is
|
|
# missing the replica refuses to run rather than test against mocks.
|
|
#
|
|
# One image serves both models. Either take one off your own machine
|
|
#
|
|
# ssh root@printer 'tar -cf - /usr/prog' > prog.tar
|
|
#
|
|
# or use the published factory image
|
|
# (md5 d2fdc0e1deb17c41cbb6016d55ab3031):
|
|
#
|
|
# https://github.com/ghzserg/FF/releases/download/R/Creator5Pro-factory.tar.xz
|
|
PROG_DUMP="$HOME/Desktop/Creator5Pro-factory.tar.xz"
|
|
|
|
# Real partition sizes, as `df -h` reports them on the printer itself.
|
|
# Until these are set the replica's prog/data partitions are unbounded, so an
|
|
# install that runs the machine out of space would pass here and fail there.
|
|
PROG_MB=""
|
|
DATA_MB=""
|