Skip to content
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

Remove legacy option of rebooting fc without using MSP #9970

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

mmosca
Copy link
Collaborator

@mmosca mmosca commented Apr 23, 2024

This can cause some issues with some devices, eg.:

betaflight/betaflight#13572

Kudos to @hydra for identifying this on BF.

This can cause some issues with some devices, eg.:

betaflight/betaflight#13572

Kudos to @hydra for identifying this on BF.
@mmosca mmosca added this to the 8.0 milestone Apr 23, 2024
@stronnag
Copy link
Collaborator

This is a useful function for scripts / tools.
I would be sorry to see it removed ... we have a guard time around it to prevent misuse.

@mmosca
Copy link
Collaborator Author

mmosca commented Apr 23, 2024

I understand it is pratical for simple scripts, but Cli reboot/dfu command or MSP_REBOOT messages would still work.

Would that be a good enough replacement for the single character reboot?

@stronnag
Copy link
Collaborator

I understand it is pratical for simple scripts, but Cli reboot/dfu command or MSP_REBOOT messages would still work.

Would that be a good enough replacement for the single character reboot?

Having to enter the CLI is not really convenient either.
If this is a problem for INAV, even with the guard time, then fine, remove it.
Hacking up MSP_REBOOT in the shell is not so big a deal.

@mmosca
Copy link
Collaborator Author

mmosca commented Apr 23, 2024

I didn't realize there was supposed to be a guard time, I have run into some random issues where the fc would reboot when I was trying to do something over msp, but that was probably due to my own buggy code. This is not written as merged yet.

@hydra
Copy link
Contributor

hydra commented Apr 29, 2024

As noted in the BF PR, using MSP_REBOOT is the correct way to tell the FC to enter a specific bootloader mode. IMHO guard times, arming checks and whatever other workaround/preventions/hacks that are put in place to prevent accidental reboots are all extra code and all require additional tests, maintenance, flash-space, etc. Less is more, YAGNI, etc...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants