Closed per1234 closed 2 years ago
When this kind of prioritised workflows are intiated (we might have something else in the future) we should force close the Serial Monitor and Serial Plotter views/apps and close the connection. Firmware update is a blocking operation anyway, and messing with serial ports in the process will sure lead to failure
Describe the bug
The Arduino IDE includes a "WiFi101 / WiFiNINA Firmware Updater"" tool that can be used to update the firmware on the WiFi radio module of Arduino boards such as the MKR WiFi 1010 and Nano 33 IoT.
If the Serial Monitor is open when a firmware update is attempted, it fails.
To Reproduce
The process fails without any indication of the cause
Expected behavior
Ideally, the IDE's Firmware Updater tool would automatically close the serial port as needed, reopening it in Serial Monitor once done, similar to how it is handled during the Upload process.
If that is not feasible, it should check for open Serial Monitor at the start of the firmware update process and clearly communicate to the user that they must close it. This is the approach taken by the classic IDE's firmware updater tool:
Desktop
Additional context
I think it could be a common occurrence because most often people are motivated to update their firmware after seeing the outdated firmware message that is printed to Serial Monitor by the "CheckFirmwareVersion" example of the WiFiNINA library or by the ArduinoIoTCloud library.