Using Mission Planner on Windows, I can choose the primary and secondary flight controllers when trying to flash new firmware, but when I choose to flash the secondary, when the secondary reboots into bootloader mode, a new virtual com port is detected on windows coincident with the chip restart but mission planner fails to see this new port as available for flashing. The primary flashes just fine. It seems like the same driver is used when both the chips reset into bootloader mode. I’m not sure what to look at next
Is it anywhere in here Joshua?
I see @sidbh had this to say elsewhere Cannot connect to Mission Planner using Cube Red - #10 by sidbh
@Dmitriy_La you can only use Mission Planner to flash the primary firmware. Make sure you are running latest Beta Mission Planner. I don’t think QGroundControl supports external flash flashing yet.
The firmware update mechanism is still fluid, there will be another update to bootloader soon for Primary to simplify firmware update process in latest 4.5 beta, this is the PR waiting for backport, if you want to keep track of progress 4.5 Backport Bootloader Fixes for H7 based devices by bugobliterator · Pull Request #27458 · ArduPilot/ardupilot · GitHub