-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add graceful shutdown support #623
Labels
Comments
jonasdn
added a commit
that referenced
this issue
Sep 3, 2021
Currently to shut-down the Crazyflie, the nRF51 simply cut the power to thae system. This was working fine until we started implementing SD-card functionality: when shutting down the system that way we have huge chances of corrupting the SD-card filesystem. This has lead to implementation of very inefficient sd-car logging procedure to decrease the probability of corruption. A better solution for the shutdown problem would be to implement a graceful shutdown in the system ... ... when the nRF51 wants to shutdown the system (ie. after a button press), it sends a message to the stm32 requesting shutdown ... in the stm32, modules that wants to be notified of shutdown are called in sequence and return when they are ready for shutdown ... when all the module have returned, the stm32 sends to the nRF51 a "ready for shutdown" message ... the nRF51 cuts the power. If no "ready to shutdown" was received after a timeout, the power is cut anyway Closes #623
jonasdn
added a commit
that referenced
this issue
Sep 3, 2021
Currently to shut-down the Crazyflie, the nRF51 simply cut the power to thae system. This was working fine until we started implementing SD-card functionality: when shutting down the system that way we have huge chances of corrupting the SD-card filesystem. This has lead to implementation of very inefficient sd-car logging procedure to decrease the probability of corruption. A better solution for the shutdown problem would be to implement a graceful shutdown in the system ... ... when the nRF51 wants to shutdown the system (ie. after a button press), it sends a message to the stm32 requesting shutdown ... in the stm32, modules that wants to be notified of shutdown are called in sequence and return when they are ready for shutdown ... when all the module have returned, the stm32 sends to the nRF51 a "ready for shutdown" message ... the nRF51 cuts the power. If no "ready to shutdown" was received after a timeout, the power is cut anyway Closes #623
jonasdn
added a commit
that referenced
this issue
Sep 3, 2021
Currently to shut-down the Crazyflie, the nRF51 simply cut the power to thae system. This was working fine until we started implementing SD-card functionality: when shutting down the system that way we have huge chances of corrupting the SD-card filesystem. This has lead to implementation of very inefficient sd-car logging procedure to decrease the probability of corruption. A better solution for the shutdown problem would be to implement a graceful shutdown in the system ... ... when the nRF51 wants to shutdown the system (ie. after a button press), it sends a message to the stm32 requesting shutdown ... in the stm32, modules that wants to be notified of shutdown are called in sequence and return when they are ready for shutdown ... when all the module have returned, the stm32 sends to the nRF51 a "ready for shutdown" message ... the nRF51 cuts the power. If no "ready to shutdown" was received after a timeout, the power is cut anyway Closes #623
jonasdn
added a commit
that referenced
this issue
Sep 8, 2021
Currently to shut-down the Crazyflie, the nRF51 simply cut the power to thae system. This was working fine until we started implementing SD-card functionality: when shutting down the system that way we have huge chances of corrupting the SD-card filesystem. This has lead to implementation of very inefficient sd-car logging procedure to decrease the probability of corruption. A better solution for the shutdown problem would be to implement a graceful shutdown in the system ... ... when the nRF51 wants to shutdown the system (ie. after a button press), it sends a message to the stm32 requesting shutdown ... in the stm32, modules that wants to be notified of shutdown are called in sequence and return when they are ready for shutdown ... when all the module have returned, the stm32 sends to the nRF51 a "ready for shutdown" message ... the nRF51 cuts the power. If no "ready to shutdown" was received after a timeout, the power is cut anyway Closes #623
cafeciaojoe
pushed a commit
to cafeciaojoe/crazyflie-firmware
that referenced
this issue
Sep 27, 2024
hide labels based on basestation availability
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently to shut-down the Crazyflie, the nRF51 simply cut the power to the system. This was working fine until we started implementing SD-card functionality: when shutting down the system that way we have huge chances of corrupting the SD-card filesystem. This has lead to implementation of very inefficient sd-car logging procedure to decrease the probability of corruption.
A better solution for the shutdown problem would be to implement a graceful shutdown in the system:
This will for now only be used for the SD-card, but it could be useful for other part of the system as well in the future.
The text was updated successfully, but these errors were encountered: