Repository navigation
RAUC support on NanoPi R2S #288
Description
Activity
There are a few things one needs to get right in order to enable full RAUC support, as we've integrated it in Infix.
RAUC is governed by its config file in
/etc/rauc/system.conf, in which we find this snippet:... [slot.rootfs.0] device=/dev/disk/by-partlabel/primary bootname=primary [slot.rootfs.1] device=/dev/disk/by-partlabel/secondary bootname=secondary ...So you need a GPT partition table on your MMC, with partition labels that match what RAUC expects.
At the moment, we use
/libexec/infix/prod/provisionto provision Infix to a blank MMC. Use it by:- Placing the Infix upgrade bundle (
images/infix-aarch64.pkg) next to the netboot image (images/rootfs.itb) on the TFTP server - Netbooting the target
- Ensure that Infix can reach the TFTP server
- Ensure that the date is properly set, so that the upgrade bundle's signature can be verified
- Run
/libexec/infix/prod/provision tftp://host/path/to/infix-aarch64.pkg /dev/mmcblk0
This designed to work in combination with all of our boot scripts (and the features needed to support them) in
board/common/uboot. So the answer to your question is: it depends.Fundamentally, the primary and secondary partitions house regular SquashFS images (see also boot.md). So you can boot Infix with no special requirements on U-Boot. Here's an example:
(board) sqfsload mmc 0:3 ${kernel_addr_r} /boot/Image 27269632 bytes read in 1558 ms (16.7 MiB/s) (board) sqfsload mmc 0:3 ${fdt_addr_r} /boot/vendor/board.dtb 31636 bytes read in 46 ms (670.9 KiB/s) (board) setenv bootargs "root=PARTLABEL=primary" (board) booti ${kernel_addr_r} - ${fdt_addr_r}If you want to verify image signatures, then I would look at integrating the existing scripts in the U-Boot build for the NanoPi.
Reacted by Joachim Wiberg- Placing the Infix upgrade bundle (
@minexn would you be OK with my converting this to a Discussion? I'd like to keep nuggets like this reply as part of our common "Knowledge Base".
- Please proceed…________________________________ From: Joachim Wiberg ***@***.***> Sent: Friday, February 2, 2024 12:18:58 AM To: kernelkit/infix ***@***.***> Cc: Andrew Campbell ***@***.***>; Mention ***@***.***> Subject: Re: [kernelkit/infix] RAUC support on NanoPi R2S (Issue #288) @minexn<https://github.com/minexn> would you be OK with my converting this to a Discussion? I'd like to keep nuggets like this reply as part of our common "Knowledge Base". — Reply to this email directly, view it on GitHub<#288 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A623N6EKWTZZQNUA5L3B7MLYRSOPFAVCNFSM6AAAAABCSP2C5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTGMYDCMRSG4>. You are receiving this because you were mentioned.Message ID: ***@***.***>Reacted by Joachim Wiberg
- locked and limited conversation to collaborators
on Feb 2, 2024
I'm testing Rauc support on the NanoPi and getting the following error.
Do we need to add support in uboot?