Hello,
I’m currently working on a project to test the SWUpdate solution on a system involving multiple Raspberry Pi devices.
I’ve reviewed the documentation but still face challenges in understanding how to adapt it to my specific setup.
Here’s what I aim to achieve:
1. A Raspberry Pi acting as a “master/server” to generate update files.
• These updates would be created either for USB-based deployment or Over-The-Air (OTA) distribution.
2. Multiple Raspberry Pi clients, each configured with an A/B partitioning architecture to ensure seamless updates.
• The system should automatically switch between partitions A and B during updates.
• The initial focus is to configure automated A/B partition switching independently of SWUpdate before integrating it fully.
3. The master/server and clients will all use Raspberry Pi 5 devices.
Here are the main challenges I’m facing:
•I’m unsure of the best way to generate a system image for the Raspberry Pi that supports A/B partitioning and is compatible with SWUpdate.
• I’m struggling to understand how SWUpdate handles both USB-based and OTA updates in this scenario.
• I would also appreciate clarification on how to structure the SWUpdate configuration files to manage this setup effectively.
Has anyone in the community worked on a similar setup? If so:
• Is my proposed solution feasible given these constraints?
• Are there specific steps, tools, or configurations you’d recommend to streamline the process?
Thank you in advance for your guidance and support. I’m happy to provide additional details if needed.
Hello,
I’m currently working on a project to test the SWUpdate solution on a system involving multiple Raspberry Pi devices.
I’ve reviewed the documentation but still face challenges in understanding how to adapt it to my specific setup.
Here’s what I aim to achieve:
1. A Raspberry Pi acting as a “master/server” to generate update files.
• These updates would be created for USB-based deployment or Over-The-Air (OTA) distribution.
2. Multiple Raspberry Pi clients configured with an A/B partitioning architecture to enable seamless updates with rollback capability.
3. The updates must be compatible with SWUpdate, meaning I need to generate a base system image for the clients that works correctly with SWUpdate and integrates A/B partitioning.
Here are the main challenges I’m facing:
• I’m unsure of the best way to generate a system image for the Raspberry Pi that supports A/B partitioning and is compatible with SWUpdate.
• I need guidance on configuring SWUpdate to handle both USB-based and OTA updates effectively.
• I would also appreciate help with structuring the SWUpdate configuration files to manage this type of setup.
Has anyone in the community worked on a similar setup? If so:
• Is my proposed solution feasible given these constraints?
• Are there specific tools, steps, or configurations you’d recommend to create the system image and set up A/B partitioning?
Thank you in advance for your guidance and support. I’m happy to provide additional details if needed.
Best regards