Continuing the discussion from Code debug for calculator:
WOW, I never saw an UNO put out that much stats.
Continuing the discussion from Code debug for calculator:
WOW, I never saw an UNO put out that much stats.
Then you don't have the "Show verbose output during: ☐ upload" preference enabled:
Now upload a sketch to an UNO R3 board. You will now see output from the upload process printed in the "Output" panel similar to what @aaron7812 shared.
I uploaded verbose (ALWAYS ON) and my output is a little different. I will post screen grabs of the different parts.
This first one may be a clue. It looks like I have a .avrduderc file overriding the system config. I will remove that file to see what is different.
@ptillisch That first difference was a mis-read (sort of) on my part (will have Q later)
But here is the end of my verbose output with genuine UNO (AFAIK). Why is mine different from OP? His has msgs re fuses and safemode.
@ptillisch Here is the differences at the beginning, why is this happening (BTW there is NO .avrduderc file)
His is
Since it was tangential to the subject of the original topic, I split this interesting discussion out to its own topic.
Carry on.
@sonofcy please post text as text. Posting pictures of text is not very helpful.
Yeah, this part of the output is confusing:
User configuration file is "/Users/ronalexander/.avrduderc"
What it actually means is "if a file exists at this path, it will be used", but the wording of the message doesn't effectively communicate that meaning..
The following line tells us that the file does not exist:
User configuration file does not exist or is not a regular file, skipping
This line is printed by the AVRDUDE uploader tool Arduino IDE uses to upload sketches to the UNO R3 board. For some reason, AVRDUDE doesn't print these lines on a Windows system (maybe they didn't implement the configuration file system for that operating system), so this is why you see it in your output, but not in the output shared by @aaron7812.
Now I understand what you mean. I interpreted the "stats" you mentioned in your post as being this part of the output:
Using Port : COM3
Using Programmer : arduino
Overriding Baud Rate : 115200
AVR Part : ATmega328P
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PC2
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :
Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
eeprom 65 20 4 0 no 1024 4 0 3600 3600 0xff 0xff
flash 65 6 128 0 yes 32768 128 256 4500 4500 0xff 0xff
lfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
efuse 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
lock 0 0 0 0 no 1 0 0 4500 4500 0x00 0x00
calibration 0 0 0 0 no 1 0 0 0 0 0x00 0x00
signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00
Programmer Type : Arduino
Description : Arduino
Hardware Version: 3
Firmware Version: 4.4
Vtarget : 0.3 V
Varef : 0.3 V
Oscillator : 28.800 kHz
SCK period : 3.3 us
But I see now you are referring to these lines:
avrdude: safemode: lfuse reads as 0
avrdude: safemode: hfuse reads as 0
avrdude: safemode: efuse reads as 0
[...]
avrdude: safemode: lfuse reads as 0
avrdude: safemode: hfuse reads as 0
avrdude: safemode: efuse reads as 0
avrdude: safemode: Fuses OK (E:00, H:00, L:00)
These lines are printed when AVRDUDE is in "safemode". AVRDUDE automatically enables this mode when it detects it is not being run from a terminal. The method used by Arduino IDE to run AVRDUDE makes AVRDUDE think it is being run from a terminal, and so it does not enable "safemode".
Likewise, the method Arduino Cloud Agent uses to run AVRDUDE on a macOS or Linux machine makes AVRDUDE think it is being run from a terminal, and so it does not enable "safemode". But the situation is unique when Cloud Agent runs AVRDUDE on a Windows machine. In this case, the environment does not meet the conditions that cause AVRDUDE to think it is being run from a terminal, and so it goes into "safemode". And thus you will see these additional lines in the output only under the following conditions:
You would also see these lines if you were using AVRDUDE directly in a script.
I don't think these lines are very useful, and running in "safemode" can even cause uploads to fail spuriously for certain rare boards (but I don't think this is an issue for Arduino Cloud, since it likely doesn't even support any of those boards), so I don't think you are missing out on anything due to AVRDUDE not running in "safemode" on your system.
In case you are interested in even more boring details on the subject, I'll provide some links: