swuforwarder-updating of master-slave

[Алексей Першуткин]

Hi Stefano!

I need to update a master-slave system. The images generated for the update must be the same. I have no idea how to do this. In my sw-description file, the update process is described as updating a slave server with swuforwarder, the master server with raw handler. Experience updating the master server with swuforwarder leads to the failing because of the reverse connection. rpi-image.rootfs.ext4.gz is the main image.swu file. So I have a duplicate in the main SWUpdate file.
Can you advise? Thanks.

sw-description file:

software =
{
version = "0.1.0";
rpiupdate = {
         hardware-compatibility: [ "1.0"];
        version = "0.1.0";
        description = "Firmware update for XXXXX Project";
       
stable : {
copy1 : {
images: (
{
filename = "image.swu";
type = "swuforward";

properties:
{
url = ["http://12.0.0.104:8080"];
};
},
{
filename = "rpi-image.rootfs.ext4.gz";
type = "raw";
compressed = "zlib";
device = "/dev/mmcblk0p2";
}
);
scripts: (
{
filename = "emmcsetupMain.lua";
type = "lua";
}
);
bootenv: (
{
name = "rpipart";
value = "2";
},
{
name = "ustate";
value = "1";
}
);
};
copy2 : {
images: (
{
filename = "image.swu";
type = "swuforward";

properties:
{
url = ["http://12.0.0.104:8080"];
};
},
{
filename = "rpi-image.rootfs.ext4.gz";
type = "raw";
compressed = "zlib";
device = "/dev/mmcblk0p3";
}
);
scripts: (
{
filename = "emmcsetupMain.lua";
type = "lua";
}
);
bootenv: (
{
name = "rpipart";
value = "3";
},
{
name = "ustate";
value = "1";
}
);
};
};
}
}

[Stefano Babic]

Hi Alex,

On 8/7/25 12:19, Алексей Першуткин wrote:
> Hi Stefano!
>
> I need to update a master-slave system. The images generated for the
> update must be the same. I have no idea how to do this.

This is of course more complicated to do, but it is doable.

> In my sw-

> description file, the update process is described as updating a slave
> server with swuforwarder, the master server with raw handler. Experience
> updating the master server with swuforwarder leads to the failing
> because of the reverse connection. rpi-image.rootfs.ext4.gz is the main
> image.swu file. So I have a duplicate in the main SWUpdate file.
> Can you advise? Thanks.

I have described this case in my talk, just check on the suppor tpage in
doc:

https://sbabic.github.io/swupdate/help_and_support.html

"Evolution of (OTA) Update in the IoT world by Stefano Babic, ELC 2019,
Slides ELC 2019, Video ELC 2019"

Best regards,
Stefano

> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to swupdate+u...@googlegroups.com
> <mailto:swupdate+u...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/
> swupdate/8e04dbf9-3e15-4ba6-898c-46ca83f6bb8en%40googlegroups.com
> <https://groups.google.com/d/msgid/
> swupdate/8e04dbf9-3e15-4ba6-898c-46ca83f6bb8en%40googlegroups.com?
> utm_medium=email&utm_source=footer>.

[Алексей Першуткин]

Thank you! I started studying it

четверг, 7 августа 2025 г. в 13:25:41 UTC+3, Stefano Babic:

[Алексей Першуткин]

I tried to cache the swu by adding output = "config.swu" but I got the following message:
"[get_common_fields] : Output file set but not enabled with -o, ignored"

четверг, 7 августа 2025 г. в 13:44:11 UTC+3, Алексей Першуткин: