I am having the same or a similar problem with a nano every, I cannot upload to it, or at least not often...
Also, the nano every gets burning hot, sometimes, while trying to upload,
I attach the conf file
for blink:
avrdude: Version 6.3-20190619
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch
System wide configuration file is "/home/bob/.arduino15/packages/arduino/tools/avrdude/6.3.0-arduino17/etc/avrdude.conf"
User configuration file is "/home/bob/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : /dev/ttyACM0
Using Programmer : jtag2updi
Overriding Baud Rate : 115200
avrdude: jtagmkII_getsync(): sign-on command: status -1
[avrdude.conf.zip|attachment](upload://pvl8wW0kC1H3HnbVRQalIv26Hwf.zip) (30.9 KB)
avrdude: jtagmkII_getsync(): sign-on command: status -1
avrdude: jtagmkII_getsync(): sign-on command: status -1
avrdude: jtagmkII_getsync(): sign-on command: status -1
Hi,
I have a similar or the same issue with a nano every...
I can sometimes, but not often upload to it...
The board sometimes, often, gets burning hot.
Below is the output from an attempt to upload blink, (attached my conf file).
I am at a loss, and there seems to be no way to abort the uploading process, which is really painful...
Any help would be greatly appreciated, my project is being killed by these delays... And now I fear that the board is burning up...
for blink:
avrdude: Version 6.3-20190619
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch
System wide configuration file is "/home/bob/.arduino15/packages/arduino/tools/avrdude/6.3.0-arduino17/etc/avrdude.conf"
User configuration file is "/home/bob/.avrduderc"
User configuration file does not exist or is not a regular file, skipping
Using Port : /dev/ttyACM0
Using Programmer : jtag2updi
Overriding Baud Rate : 115200
avrdude: jtagmkII_getsync(): sign-on command: status -1
avrdude: jtagmkII_getsync(): sign-on command: status -1
avrdude: jtagmkII_getsync(): sign-on command: status -1
avrdude: jtagmkII_getsync(): sign-on command: status -1
Cross-posting is against the Arduino forum rules. The reason is that duplicate posts can waste the time of the people trying to help. Someone might spend a lot of time investigating and writing a detailed answer on one topic, without knowing that someone else already did the same in the other topic.
Repeated cross-posting can result in a suspension from the forum.
In the future, please only create one topic for each distinct subject matter. This is basic forum etiquette, as explained in the "How to get the best out of this forum" guide. It contains a lot of other useful information. Please read it.
This might be caused by a short or external circuitry connected to the Arduino board drawing excessive current.
Make sure the board is not sitting on anything conductive that could short the contacts on the bottom of the board. Inspect the board carefully on both sides to make sure there isn't any conductive debris (e.g., strands of wire or component leads) on the board or on the surface the board is sitting on.
If you have a shield or any external circuitry or components connected to your Arduino board, try this experiment:
Disconnect the USB cable of the Arduino board from your computer.
Disconnect any shields, modules, external circuitry, etc. from your board.
Connect the Arduino board to your computer with a USB cable.
Now check to see if the problem still occurs.
This experiment will determine whether the problem was caused by the external circuitry. If so, you can then focus your attention on identifying the specific problem with the circuit and resolving it.
I have found, in Linux, that if I change the Serial monitor to 1200 baud (from the default of 9600), and then upload the sketch, it works. After that I can upload the sketch at any baud rate, including 9600 baud, until the board is power cycled.
For the uploading, I tried the 1200baud setting on the serial montior, that did nothing. The pyhton script seems to do something at least sometimes, so that is sort of a workaround.
For the burning board, it is a nano every and it is sitting on a piece of wood, no longer connected to anything but the USB cable to the PC (linux).
The processor reaches 80C according to my infra red thermometer, and smells like it's on fire. I'm wondering if I burned it out, or if it was simply defective since I only took it out of the box a few days ago and have been very careful with it.
I guess it's time to give up and try a different board.
Which Nano are you using? There are several different ones and not all operate at 5V. Mine do not have a ADV pin but they have a Aref pin. Post a link to technical information on the one you have.
It is a genuine Arduino Nano Every purchased from Arduino.cc; This was the first time I used it. From the outset, there was the uploading problem, and then it burnt out...
I may not replace it because of the difficulties....
Otherwise, I have no issues on Linux, I've been developing from the very first UNO's on a Linux platform. I couldn't imagine doing anything serious on Windows... But what do I know?
As an update, I just received a brand new, genuine Arduino Nano Every, and with nothing connected to it, I still get the same error and cannot upload. The board does not get hot, though.
Sometimes if I set the serial monitor to 1200 baud, i can finally, update. Then, a little while later, it fails again...
Again, this is most annoying, I wonder if the Nano Every just has a design issue?
Yes, the "design issue" with the Nano Every is that it requires a 1200 bps serial touch to put it into programming mode. As you know from the past information in this thread, the implementation of that touch under Linux is problematic and has not been fixed.
My Nano Every came programmed with “Blink”. So: before packaging someone had to connect the board to a computer and push a button. And if this person waits a few seconds looking at the LEDs blinking: voila, Quality Control done. This picks up at least 95% of the possible failures. They must be fools not to do this level of quality control, but then again: I wasn’t there.
However: this level of quality control doesn’t pick up troubles with the 5V regulator, which has proven to be vulnerable / troublesome.
gratefulfrog didn’t describe how his board was powered, using the ADV pin rings an alarm bell. (Might also be a simple typo in the thread.)
I doubt the burning of the board is related to the Linux problem with the 1200 Baud Reset. Two unrelated problems is bad luck.