-
-
Notifications
You must be signed in to change notification settings - Fork 904
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
after firmware flashing bootloader mode stands #4156
Comments
Did you give permission to the port before during normal connection ? |
As you can see in the screenshot above, the port is not closed after flashing. |
I'm using Microsoft Edge on Windows 11 23H2 |
Ok, there seems to be a problem with Microsoft Edge, I just installed Chrome and it works without any problems. |
@haslinghuis pls can you reopen this issues ... on latest google chrome now i have the same problem |
@TheIsotopes - Did you accept permission for notifications introduced in 4134 ? |
nope ... was deactivated, activated again and it's working now. I don't think this is how it should be!? |
Where you on the onboard logging tab (blackbox) or firmware flasher tab ? |
In both console screenshot i was on firmware flasher tab. |
@haslinghuis tested latest build, but it's not fixed (tested on edge) ... activated again the notification and it's working |
did the app "update" or did it use a cached version? |
Yes was not ready yet and have it working now in a new PR. But there is one issue if user blocked the first request: And then enabling permissions are still denied and will throw the error. |
With latest iteration users will not be able to enable the checkbox without giving permission. |
Describe the bug
on the latest master the bootloader mode is not exited after flashing a firmware.
i have this problem with f4 and h7 boards.
To Reproduce
flashing a firmware and wait on reboot ... but it stays in bootloader mode
Expected behavior
reset to setup mode after flashing
Configurator version
latest PWA master snapshot
Flight controller configuration
No response
Add any other context about the problem that you think might be relevant here
No response
The text was updated successfully, but these errors were encountered: