Closed as not planned
Description
Describe the problem
There are 6 sketch build and upload buttons in the Arduino 2 IDE.
Toolbar Verify Button - Builds the sketch
Toolbar Upload Button - Builds the sketch, then uploads to device
Menu Bar Sketch Menu - Verify/Compile MenuButton - Builds the sketch
Menu Bar Sketch Menu - Upload MenuButton - Builds the sketch and then uploads to device
Menu Bar Sketch Menu - Configure and Upload MenuButton - ??
Menu Bar Sketch Menu - Upload Using Programmer MenuButton - Builds the sketch and then uploads to device
- Why does Upload build/verify before uploading ? Can't it just upload the existing binary to the device if there is one already ?
- Whats the difference between the Upload Button, Upload MenuButton, Upload using Programmer and COnfigure and Upload ?
- How can I upload just an existing binary to the device, without any compilation/build/link/config etc, My workflow is sometimes develop, test - compile and upload, experiment with the device causing firmware wipe, then I want to only re-apply/upload the same firmware that I built earlier, I dont weant to rebuilod anything.
To reproduce
- Create a simple project and sketch .ino
- Configure IDE for ESP32 for example (can be any device AFAIK)
- Press Upload (Right Arrow) on Toolbar - IDE will build the sketch first and then upload firmware binary
- Press Upload (Right Arrow) on Toolbar - IDE will build the sketch AGAIN (even without any code changes being made), and then it will upload the newly built firmware binary
Expected behavior
- Create a simple project and sketch .ino
- Configure IDE for ESP32 for example (can be any device AFAIK)
- Press Upload (Right Arrow) on Toolbar - IDE will build the sketch first and then upload firmware binary
- Press Upload (Right Arrow) on Toolbar - IDE will NOT build the sketch AGAIN - it will just upload the existing firmware binary
Arduino IDE version
2.1.0
Operating system
Windows
Operating system version
10
Additional context
No response
Issue checklist
- I searched for previous reports in the issue tracker
- I verified the problem still occurs when using the latest nightly build
- My report contains all necessary details