From 11fa5780e244bc3095f7e7c149eb2df480b8e7fd Mon Sep 17 00:00:00 2001 From: Moritz Barsnick Date: Wed, 3 Jun 2026 11:48:56 +0200 Subject: [PATCH 1/2] Firmware: modify image type description Signed-off-by: Moritz Barsnick --- firmware_upgrade.inc | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/firmware_upgrade.inc b/firmware_upgrade.inc index 5946816..20cd045 100644 --- a/firmware_upgrade.inc +++ b/firmware_upgrade.inc @@ -47,13 +47,17 @@ Release Images vs Development Images There are two types of firmware images available for chargebyte devices: -- Release images: These images are tested and verified by chargebyte and are recommended for - production use. The image size is optimized for production use and contains only the necessary - components. -- Development images: These images are used for development purposes and are not tested or verified - by chargebyte. They are intended for developers who want to implement and test new features or - applications before they are released. The image size is larger than the release image and - contains additional development tools and libraries that are not necessary for production use. +- **Release images** are optimized for deployment and contain only the components required to run + the system. Their smaller size reduces download and installation times and leaves more storage + space available on the target device for customer-specific applications, services, and data. + These images are tested and verified by chargebyte and are recommended as the basis for deployed + systems. + +- **Development images** contain the same runtime environment as release images, but additionally + include development packages such as libraries and header files. They are intended primarily for + development workflows that use the target filesystem as a sysroot for cross-compilation and for + building customized software components. Because of the additional development content, these + images are significantly larger than release images. .. note:: Before installation of a chargebyte EVerest image, please check whether you are installing a From 8a051b346f6882793631bab5e3c0810a241c4df3 Mon Sep 17 00:00:00 2001 From: Moritz Barsnick Date: Wed, 3 Jun 2026 11:52:23 +0200 Subject: [PATCH 2/2] Firmware: drop rauc signing key section This was never valid for EVerest builds. Even the newly provided "Release" builds are signed with the devel key, and their symbolic link reflects this correctly. Signed-off-by: Moritz Barsnick --- firmware_upgrade.inc | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/firmware_upgrade.inc b/firmware_upgrade.inc index 20cd045..ffa42ab 100644 --- a/firmware_upgrade.inc +++ b/firmware_upgrade.inc @@ -59,29 +59,6 @@ There are two types of firmware images available for chargebyte devices: building customized software components. Because of the additional development content, these images are significantly larger than release images. -.. note:: - Before installation of a chargebyte EVerest image, please check whether you are installing a - developer or release image. In order to update the firmware with a chargebyte EVerest developer - image, the developer key must be set in the :code:`"/etc/rauc"` directory to pass the internal - validation process of the RAUC firmware update mechanism. The image type can be identified by the - file name. - - Depending on the image type, the key must be adapted as follows: - - Change to developer key: - - .. code-block:: bash - - cd /etc/rauc - ln -sf i2se-devel.crt keyring.pem - - Change to release key: - - .. code-block:: bash - - cd /etc/rauc - ln -sf i2se-release.crt keyring.pem - Device Access -------------