EIVE System Reboot Logic #762

Closed
opened 2023-07-31 10:45:43 +02:00 by meggert · 2 comments
Owner

The error handling within EIVE System leading to a reboot calls the sendFullRebootCommand() function. This function will not only reboot, but boot onto the image 0 0. I don't think this is actually what we want here. A reboot self should be sufficient, especially given that our image 0 0 will lag behind for the foreseeable future.

Maybe we should also add a delay between triggering the reboot event and the actual reboot, to ensure that the event can be triggered and stored before actaully rebooting.

The error handling within [EIVE System](https://egit.irs.uni-stuttgart.de/eive/eive-obsw/src/branch/main/mission/system/EiveSystem.cpp) leading to a reboot calls the `sendFullRebootCommand()` function. This function will not only reboot, but boot onto the image 0 0. I don't think this is actually what we want here. A reboot self should be sufficient, especially given that our image 0 0 will lag behind for the foreseeable future. Maybe we should also add a delay between triggering the reboot event and the actual reboot, to ensure that the event can be triggered and stored before actaully rebooting.
muellerr was assigned by meggert 2023-07-31 10:45:43 +02:00
Owner

I think reboot self is better here as well. I would keep the reboot until the PDEC issue is understood bette. A delay sounds reasonable.

I think reboot self is better here as well. I would keep the reboot until the PDEC issue is understood bette. A delay sounds reasonable.
Owner

This was fixed, including the PDEC bug itself.

This was fixed, including the PDEC bug itself.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: eive/eive-obsw#762
No description provided.