Cant close failed upload 2.04

Development Tools IDE 2.x
1

if the upload is blocked there seems no way to stop or restart it.
Even closing the ide and re-opening doesnt work.

The only work-around I've found is to close the ide, re-open it, and connect to a different usb port

2

Hi @johnerrington. I'm not sure I understood correctly what you mean by "blocked". Please provide a more detailed description to help me to understand it.

3

I'm using an external serial port monitor (Termite) to record data from the arduino - because I can generate a .csv formatted log file.

If I forget to disconnect it before trying an upload, then its already using the port, so the IDE cant upload.

But if I then disconect termite - or even close it down - the IDE continues to show its trying to update.
What I think it SHOULD do:
fail gracefully or
provide a facility to stop the attempted upload.

4

Which board do you have selected from the Tools > Port menu in Arduino IDE?

I just gave it a try with my Mega board and that is exactly what it does. But it is possible the upload tools of other boards might have different behavior.

I haven't experienced the problem with a busy port, but under other conditions the 3rd party AVRDUDE tool used to upload to the AVR-based boards has an annoying behavior of retrying a failed upload 10 times. It does finally error out, but it takes a long time and I've never once seen an upload pass on a subsequent retry after AVRDUDE's first attempt failed.

The feature request is tracked by the Arduino IDE developers here:

If you have a GitHub account, you can subscribe to that issue to get notifications of any new developments related to this subject.

5

Thanks @ptillisch
yesterday this behaviour was so consistent as to be quite frustrating.
I tried it this am with a micro - and after about 10 sec it says "failed uploading exit status 1"
I cant get it to replicate the behaviour I was seeing yesterday.
I also tried it again with a Mega - same results.

I guess we'll put it down to "just one of those things".

I'm very much a github newbie, but I've had a go at putting a comment on the thread.

6

Thanks for the update! Even though it is not so satisfying as identifying the cause and fix for the problem, I'm just glad it is working now. If the problem comes back, feel free to comment here and I'll try to investigate further.

7

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.