Nano every : avrdude: jtagmkII_initialize(): ....

i connected the Nano every with USB to PC and no further hardware. I followed the first steps ( Driver...Settings,.. ) and i try to download "Blink"
but than this message is coming:

Build-Optionen wurden verändert, alles wird neu kompiliert
Der Sketch verwendet 1370 Bytes (2%) des Programmspeicherplatzes. Das Maximum sind 49152 Bytes.
Globale Variablen verwenden 22 Bytes (0%) des dynamischen Speichers, 6122 Bytes für lokale Variablen verbleiben. Das Maximum sind 6144 Bytes.
avrdude: jtagmkII_initialize(): Cannot locate "flash" and "boot" memories in description

Please do this:

  • (In the Arduino IDE) File > Preferences
  • Uncheck the checkbox next to "Show verbose output during: compilation"
  • Check the checkbox next to "Show verbose output during: upload
  • Click "OK"
  • Sketch > Upload
  • After the upload fails, you'll see a button on the right side of the orange bar "Copy error messages" (or the icon that looks like two pieces of paper at the top right corner of the black console window in the Arduino Web Editor). Click that button.
  • In a forum reply here, click on the reply field.
  • Click the </> button on the forum toolbar. This will add the forum's code tags markup to your reply.
  • Press "Ctrl + V". This will paste the upload output between the code tags.
  • Move the cursor outside of the code tags before you add any additional text to your reply.
Der Sketch verwendet 1370 Bytes (2%) des Programmspeicherplatzes. Das Maximum sind 49152 Bytes.
Globale Variablen verwenden 22 Bytes (0%) des dynamischen Speichers, 6122 Bytes für lokale Variablen verbleiben. Das Maximum sind 6144 Bytes.
Erzwinge Reset durch öffnen/schließen mit 1200 bps auf dem Port COM7
C:\Users\Familie Schulz\Documents\ArduinoData\packages\arduino\tools\avrdude\6.3.0-arduino16/bin/avrdude -CC:\Users\Familie Schulz\Documents\ArduinoData\packages\arduino\tools\avrdude\6.3.0-arduino16/etc/avrdude.conf -v -patmega4809 -cjtag2updi -PCOM7 -b115200 -e -D -Uflash:w:C:\Users\FAMILI~1\AppData\Local\Temp\arduino_build_465129/Blink.ino.hex:i -Ufuse2:w:0x01:m -Ufuse5:w:0xC9:m -Ufuse8:w:0x00:m {upload.extra_files} 

avrdude: Version 6.3-20171130
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

         System wide configuration file is "C:\Users\Familie Schulz\Documents\ArduinoData\packages\arduino\tools\avrdude\6.3.0-arduino16/etc/avrdude.conf"

         Using Port                    : COM7
         Using Programmer              : jtag2updi
         Overriding Baud Rate          : 115200
JTAG ICE mkII sign-on message:
Communications protocol version: 1
M_MCU:
  boot-loader FW version:        1
  firmware version:              6.00
  hardware version:              1
S_MCU:
  boot-loader FW version:        1
  firmware version:              6.00
  hardware version:              1
Serial number:                   00:00:00:00:00:00
Device ID:                       JTAGICE mkII
         AVR Part                      : ATmega4809
         Chip Erase delay              : 0 us
         PAGEL                         : P00
         BS2                           : P00
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 0
         StabDelay                     : 0
         CmdexeDelay                   : 0
         SyncLoops                     : 0
         ByteDelay                     : 0
         PollIndex                     : 0
         PollValue                     : 0x00
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
           prodsig        0     0     0    0 no         61   61      0     0     0 0x00 0x00
           fuses          0     0     0    0 no          9    0      0     0     0 0x00 0x00
           fuse0          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse1          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse2          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse4          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse5          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse6          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse7          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           fuse8          0     0     0    0 no          1    0      0     0     0 0x00 0x00
           lock           0     0     0    0 no          1    0      0     0     0 0x00 0x00
           data           0     0     0    0 no          0    0      0     0     0 0x00 0x00
           usersig        0     0     0    0 no         64   64      0     0     0 0x00 0x00
           flash          0     0     0    0 no      49152  128      0     0     0 0x00 0x00
           eeprom         0     0     0    0 no        256   64      0     0     0 0x00 0x00

         Programmer Type : JTAGMKII_PDI
         Description     : JTAGv2 to UPDI bridge
         M_MCU hardware version: 1
         M_MCU firmware version: 6.00
         S_MCU hardware version: 1
         S_MCU firmware version: 6.00
         Serial number:          00:00:00:00:00:00
         Vtarget         : 5.0 V

avrdude: jtagmkII_initialize(): Cannot locate "flash" and "boot" memories in description
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.27s

avrdude: Device signature = 0x1e9651 (probably m4809)
avrdude: erasing chip
avrdude: reading input file "C:\Users\FAMILI~1\AppData\Local\Temp\arduino_build_465129/Blink.ino.hex"
avrdude: writing flash (1370 bytes):

Writing | ################################################## | 100% 1.03s

avrdude: 1370 bytes of flash written
avrdude: verifying flash memory against C:\Users\FAMILI~1\AppData\Local\Temp\arduino_build_465129/Blink.ino.hex:
avrdude: load data flash data from input file C:\Users\FAMILI~1\AppData\Local\Temp\arduino_build_465129/Blink.ino.hex:
avrdude: input file C:\Users\FAMILI~1\AppData\Local\Temp\arduino_build_465129/Blink.ino.hex contains 1370 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 0.29s

avrdude: verifying ...
avrdude: 1370 bytes of flash verified
avrdude: reading input file "0x01"
avrdude: writing fuse2 (1 bytes):

Writing | ################################################## | 100% 0.02s

avrdude: 1 bytes of fuse2 written
avrdude: verifying fuse2 memory against 0x01:
avrdude: load data fuse2 data from input file 0x01:
avrdude: input file 0x01 contains 1 bytes
avrdude: reading on-chip fuse2 data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...
avrdude: 1 bytes of fuse2 verified
avrdude: reading input file "0xC9"
avrdude: writing fuse5 (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of fuse5 written
avrdude: verifying fuse5 memory against 0xC9:
avrdude: load data fuse5 data from input file 0xC9:
avrdude: input file 0xC9 contains 1 bytes
avrdude: reading on-chip fuse5 data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...
avrdude: 1 bytes of fuse5 verified
avrdude: reading input file "0x00"
avrdude: writing fuse8 (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of fuse8 written
avrdude: verifying fuse8 memory against 0x00:
avrdude: load data fuse8 data from input file 0x00:
avrdude: input file 0x00 contains 1 bytes
avrdude: reading on-chip fuse8 data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...
avrdude: 1 bytes of fuse8 verified

avrdude done.  Thank you.

Like This ?? I didnt find the buttons for copy the error massage...

That message indicates that the part has been programmed successfully. "avrdude: jtagmkII_initialize(): Cannot locate "flash" and "boot" memories in description" is a spurious warning and can be safely ignored.

JensSchulz:
I didnt find the buttons for copy the error massage...

That button only appears when the upload failed. I didn't realize this was only about a warning, not an error. I apologize for any confusion.

Thank you very much for the quick an successfull response. From my side everything is OK! i can live with this warning.
I think it is only a litttle confusing....

Thanks again..

I agree. It is confusing. I just got the Nano Very and was testing it out, only to come onto this warning.
I'm happy that it can be ignored and in fact, my test sketch did upload successfully and is working,

I do have a question though.
For "Registers Emulation" which option should we use?

  • ATMEGA 328
    or
  • None (ATMEGA4809)

Am I right in that choosing the first option, ATMEGA 328 would mean that there is an emulator to emulate a regular Nano that interpolates the registers you may request to the actual registers that the VERY has?

And am I right that the 2nd option, None (ATMEGA4809) means that the Nano Very will be addressed in its own native more (registers) so you'd have to build your sketches using SPECIFIC Nano Very registers and trying to upload a normal Nano sketch (with registers in the code) would fail or just not work??

BlondieSL:
Am I right in that choosing the first option, ATMEGA 328 would mean that there is an emulator to emulate a regular Nano that interpolates the registers you may request to the actual registers that the VERY has?

And am I right that the 2nd option, None (ATMEGA4809) means that the Nano Very will be addressed in its own native more (registers) so you'd have to build your sketches using SPECIFIC Nano Very registers and trying to upload a normal Nano sketch (with registers in the code) would fail or just not work??

That's correct, though "an emulator" may not quite be the right terminology. You can see the emulation code here:

Another thing to note is that the emulation isn't absolutely comprehensive. Even with the setting on, you will still find that some programs that use low level ATmega328P-specific code won't compile.