-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
3DR radio flashing: please let user choose firmware, ask for confirmation. #4336
Comments
Also when choosing Custom Firmware for PX4/ArduPilot radio buttons should disable or hide so user isn't confused. |
this is still an issue, connecting a radio, means flashing it with current SiK , instead of at least confirming that the user want that, or offer to choose a firmware file.. |
Can the check for firmware be done in advance, and refrain from even putting the radio into bootloader mode if there isn't an appropriate firmware for it? Or, if firmware isn't found, can the radio be taken back out of bootloader mode and restored to functionality? What it's doing right now is just bricking radios and I need to go dig out a Windows box with MP to unbrick them. (The radio in the above example is an RFD900+ by the way.) |
You should just need to remove power from them and they go out of command mode. |
I wish, but the red LED is on solid no matter how many times I power cycle it, until I go find something with valid firmware for it. Numerous similar tales of woe over here: https://discuss.ardupilot.org/t/3dr-radio-in-bootloader-mode-after-failed-firmware-update/14911 |
So three years ago for the first forum post and nobody bothers to notify QGC dev of the problem. Sigh! |
No. The id needed to know which firmware to flash comes from the bootloader.
Yes. Working on that. |
I believe this is supported now but SiK Radio flashing in general seems busted right now. Will verify once that's fixed. |
For consistent experience, when 3DR radio is about to be flashed: please make the behavior more like Ardupilot flashing:
Ask user for confirmation, and offer to flash custom file, instead of just flashing right away.
The text was updated successfully, but these errors were encountered: