From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Tue, 25 Jan 2022 14:11:50 +0100 Received: from metis.ext.pengutronix.de ([2001:67c:670:201:290:27ff:fe1d:cc33]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nCLby-00CrLl-T8 for lore@lore.pengutronix.de; Tue, 25 Jan 2022 14:11:50 +0100 Received: from localhost ([127.0.0.1] helo=metis.ext.pengutronix.de) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1nCLby-000542-4r; Tue, 25 Jan 2022 14:11:50 +0100 Received: from [70.184.225.181] (helo=mail.steinkuehler.net) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1nCLbh-00052s-PS for rauc@pengutronix.de; Tue, 25 Jan 2022 14:11:38 +0100 Received: (qmail 21482 invoked from network); 25 Jan 2022 07:11:32 -0600 Received: from 152.ks.newtek.dhcp (HELO ?10.34.1.152?) (charles@10.34.1.152) by mail.steinkuehler.net with SMTP; 25 Jan 2022 07:11:32 -0600 Message-ID: <7f363e23-fa86-59f7-96dd-ea24d3d459e8@steinkuehler.net> Date: Tue, 25 Jan 2022 07:11:29 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 To: rauc@pengutronix.de Content-Language: en-US From: Charles Steinkuehler X-Host-Lookup-Failed: Reverse DNS lookup failed for 70.184.225.181 (failed) X-Broken-Reverse-DNS: no host name for IP address 70.184.225.181 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.ext.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=0.9 required=4.0 tests=AWL, BAYES_00, PTX_BROKEN_RDNS, RDNS_NONE,SPF_HELO_NONE,T_SPF_PERMERROR autolearn=no autolearn_force=no version=3.4.2 Subject: [RAUC] Initial rauc.status file X-BeenThere: rauc@pengutronix.de X-Mailman-Version: 2.1.29 Precedence: list List-Id: RAUC Project - Discussion List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "RAUC" X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: rauc-bounces@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false In my Buildroot+RAUC example (https://github.com/cdsteinkuehler/br2rauc) by default the slots are not writable so I am using a rauc.status file on the partition used for storing state and configuration data. The issue is when I create a new image the rauc.status file is empty although the created uSD image includes valid data for all of the slots. My image build process is roughly: Create vfat bootfs -> Write bootfs to boot-mbr-switch uSD primary slot -> Write bootfs to boot-mbr-switch uSD secondary slot -> Create RAUC bundle using bootfs Create rootfs image -> Write rootfs image to uSD primary slot -> Write rootfs image to uSD secondary slot -> Create RAUC bundle using rootfs Create empty writable data partition (where rauc.status lives) Questions: Is there a suggested method of getting from update bundles to a disk image that includes the proper contents in rauc.status? Can I use the rauc command to "cross install", eg: use rauc to write the aarch64 contents to the loopback image file on my x86 development system and update the rauc.status file in the process, or do I need to do this on the target system? -- Charles Steinkuehler charles@steinkuehler.net _______________________________________________ RAUC mailing list