WIP: Start impl auto switch feature #811

Changelog missing.
Also not sure what this is. To me it looks like the OBSW will always boot to the Target Image, no matter what. Am I missing something? Or is the mechanism not finished yet?

Changelog missing. Also not sure what this is. To me it looks like the OBSW will always boot to the Target Image, no matter what. Am I missing something? Or is the mechanism not finished yet?

muellerr added 1 commit 2023-10-23 13:31:03 +02:00

EIVE/eive-obsw/pipeline/pr-main This commit looks good Details

4fd18e94fd

changelog

muellerr added 1 commit 2023-10-23 13:39:48 +02:00

EIVE/eive-obsw/pipeline/pr-main This commit looks good Details

4e0842c607

add link

muellerr commented

2023-10-23 13:40:48 +02:00

Added changelog entry. For more information, also see new redmine entry: https://egit.irs.uni-stuttgart.de/redmine/projects/eive-flight-manual/wiki/OBC_Auto_Switch_Image

This mechanism will only trigger once it has been activated explicitely. It is also self-clearing / one-shot: The key value pair triggering the mechanism will be cleared after the reboot.

Added changelog entry. For more information, also see new redmine entry: https://egit.irs.uni-stuttgart.de/redmine/projects/eive-flight-manual/wiki/OBC_Auto_Switch_Image This mechanism will only trigger once it has been activated explicitely. It is also self-clearing / one-shot: The key value pair triggering the mechanism will be cleared after the reboot.

meggert commented

2023-10-26 09:19:29 +02:00

Added changelog entry. For more information, also see new redmine entry: https://egit.irs.uni-stuttgart.de/redmine/projects/eive-flight-manual/wiki/OBC_Auto_Switch_Image

This mechanism will only trigger once it has been activated explicitely. It is also self-clearing / one-shot: The key value pair triggering the mechanism will be cleared after the reboot.

I do understand how it works, I am just not sure it is usefull like this. If we update 0 0, what information do we gain about the updated image with this feature, if it reboots more or less instantly.

Also this way a manual reboot SELF will lead to 2 reboots to the same image.

> Added changelog entry. For more information, also see new redmine entry: https://egit.irs.uni-stuttgart.de/redmine/projects/eive-flight-manual/wiki/OBC_Auto_Switch_Image > > This mechanism will only trigger once it has been activated explicitely. It is also self-clearing / one-shot: The key value pair triggering the mechanism will be cleared after the reboot. I do understand how it works, I am just not sure it is usefull like this. If we update 0 0, what information do we gain about the updated image with this feature, if it reboots more or less instantly. Also this way a manual reboot SELF will lead to 2 reboots to the same image.

muellerr commented

2023-10-26 10:17:45 +02:00

It's not about information, it is about safety. If the 0 0 image OBSW binary is updated, but not the firmware/dtb (HPC, connection loss, cosmic snipe whatever..) , the Linux/OBSW might crash horribly. We still have the other reboot mechanism, but I do not 100 % trust only this mechanism. The auto switch image would be a one-shot fallback to just prevent the OBC from booting a (temporarily) broken image. After successfully updating everythng (nominal case unless we're terribly unlucky), we clear the flag and test the image normally. It's just a temporary safety layer for the 0 0 update I guess.

muellerr modified the milestone from v7.2.0 to v7.3.0

2023-10-27 12:49:24 +02:00

muellerr added 1 commit 2023-10-30 14:45:10 +01:00