ArduPilot / ArduPilot/MissionPlanner
Firmware Wizard uploading wrong firmware
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 2.9k
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 4
Description
#### Issue details
There have been reports of MANY users uploading FMUV2 when FMUV3 should have been uploaded. It's been discussed on the last 2 Dev Calls by @rmackay9.
I have personally experienced the same issue before, and I believe it is stemming from the wizard not identifying hardware properly. When that happens, new pop-up menus guide the user with choices such as "Is this a Linux board?", and "Is this an APM board?". No choice is given for the majority of boards, and after the 3 or 4 "NO" selections, an arbitrary firmware upload is attempted. This wizard really needs to change to allow users to select their board as appropriate. The automatic detection is not working reliably, and should change.
For FMUv2 and v3, we really should try to install FMUv3 to everything, and only try v2 if that install fails due to lack of flash.
The bottom right boxes to upload custom firmware are the only way I upload firmware any more because of the trust I've lost from the wizard trying to upload the wrong firmware many times.
#### Version
All
#### Platform
[X] All
[ ] AntennaTracker
[ ] Copter
[ ] Plane
[ ] Rover
[ ] Sub
#### Hardware type
ALL
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Firmware Wizard's hardware-identification and firmware-upload entry points, then reproduce the incorrect FMUv2 selection on supported boards. Review how the wizard handles FMUv2 and FMUv3 choices and fallback behavior. Done means the wizard reliably identifies or lets users select the board and does not upload arbitrary firmware.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100