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

Reboot-to-bootloader is extremely unreliable #369

Open
Brycey92 opened this issue Dec 5, 2022 · 2 comments
Open

Reboot-to-bootloader is extremely unreliable #369

Brycey92 opened this issue Dec 5, 2022 · 2 comments
Assignees
Labels
bug Something isn't working future

Comments

@Brycey92
Copy link
Collaborator

Brycey92 commented Dec 5, 2022

I only very rarely am able to get the Swadge to reboot into bootloader automatically from the main menu. I receive such failure modes as:

  • reboot-to-bootloader.exe can't find the port
  • reboot-to-bootloader.exe exits saying Error sending feature report on command 3 (-1)
  • Possibly more?

This was a great feature that I would like to have working again.

@Brycey92 Brycey92 added bug Something isn't working future labels Dec 14, 2022
@cnlohr
Copy link
Collaborator

cnlohr commented Jan 18, 2023

One thing I forgot to mention - should find out about - is (1) Is this only Windows and ...

(2) The intended behavior (coincidental to the only behavior possible) is that after reflashing you can't talk to the USB normally without a reboot. This is also a blessing because if you do unattended reboot-to-bootloader-flash-reboot cycles, it means you don't put a swadge into a constantly-reboot-and-flash loop.

@Brycey92
Copy link
Collaborator Author

I have only been testing this on Windows, and I can say with certainty that in my testing, manual reboots prior to auto reboot-to-bootloader don't solve the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working future
Projects
None yet
Development

No branches or pull requests

2 participants