Hello Arduino-Debugger,

I recognize an error when I try to upload a big program to my Leonardo.

Situation:
- Load a Programm of 28182 Bytes so, the Debugger
  add some more Bytes - AtmelStudio then says it
  tries to upload
  28544 (used 100% of a 28672 byte maximum)
And then - AtmelStudio raises this error:
---------------------
Connecting to programmer: .
Found programmer: Id = "CATERIN"; type = S
    Software Version = 1.0; No Hardware Version given.
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize=128 bytes.

Programmer supports the following devices:
    Device code: 0x44

avrdude: verification error, first mismatch at byte 0x7000
         0x00 != 0x55
avrdude: verification error; content mismatch
------------------------

After that, no further programs can be uploaded to the Leonardo - AtmelStudio Claims, that there is no connection to the serial port:
------------------
Uploading to I/O board using 'COM4'
Unable to 'touch' hardware serial port
-------------------
And the worse - Arduino doesn't boot/start up (due to the demanged Programm I think).

With the Arduino IDE it is not possible to upload either.
The only way I could recover is, by pressing the reset button while the arduino IDE was compiling the scetch.
Quick after the IDE tries to upload, you have to release the reset button on the arduino.

I can reproduce this behavour with arduino 1.05 or 1.5.4sp2 configured in VisualMicro.
The difference is, that with 1.05 the Programm code is much bigger from the beginning - so you have to reduce the programm code a bit to get the same error state.
You can play with the code length - and you will recognize, that from a certain point of length strange things will happen...

Can You reproduce this problem?
Is there a way to recover within AtmelStudio?
Is it a problem of the VisualMicro-Debugger and its connection to arduino 1.05/1.5.4sp2?
Is it a problem of the arduino 1.05/1.5.4sp2 that do not report the apropriate sizes?
In the end I guess - its something else... 

Kind regards
Thomas

Hello Tim,

I'm familiar with the Arduino upload mechanisme - thank's anyway. 
The Leonardo showed up normaly as an even port number.
(as in the state of an upload, it shows up as an uneven port number)...

I did some more testing on this - and think that you have to have a look at the kind how the sketches are built - there is a missmatch in the sizes between Arduino IDE and Atmel-Studio (and so - may be VisualMicro?):

I built the exactly same sketch in six different ways:
(first number: size of sketch, second: size of `RAM`)
Arduino IDE 1.0.5: 28108  - na
Arduino IDE 1.5.4: 28418  - 1109
Atmel/ArIDE 1.0.5 no Debug: 28108 - na
Atmel/ArIDE 1.5.4 no Debug: 27836 - 527
Atmel/ArIDE 1.0.5 with Debug: 28446 - na
Atmel/ArIDE 1.5.4 with Debug: 28158 - 578

-> compared to the maximal memory size of 28672 Bytes,
     the Debugger allways reports a percentage below 100%

Please note the difference between the sizes that are reported by the Arduino IDE and the Atmel/ArIDE  1.5.4...
The difference is 582bytes - the same for `RAM` and for `ROM`.

So the question is: who and why is not willing to fill my `ROM` and `RAM` ... 
(ok, it should tell me, that the debug-sketch is to big...)


Hope that helps to locate the problem...

Regards
Thomas

... And I thought Arduino is simple... 

I played around to build a script for testing (well, I'm not realy used to program - so I don't dare sharing my `real code` with you...    ) - as I discovered, that you should be able to reproduce the problem by using a script - that does nothing at all.
Simply compare the output of that script compiled by Atmel or ArduinoIDE:

void setup()
{

  /* add setup code here */


}


void loop()
{

  /* add main program code here */
  

}

Add some more code - it still shows different output, does it?

Best regards
Thomas

PS: as for the comparision of the verbose output of the debugger - I can't find any differeneces regarding paths...

It looks like Arduino 1.5.4 has some additional core sources which Visual Micro is supposed to be taking account of but is not.

This will be addressed in the next release, we are often a point release behind Arduino for a week or so after release but this month things have been more delayed.

For now I suggest using an earlier version of 1.5.x or any 1.0.x version.

Sorry for the hassle, you won;t have seen this in the verbose output due to caching in both the Arduino ide and Visual Micro.

Hi,

Can we first check out your visual micro install. There are some new trace messages in the latest release and I don't see them in your useful output above (thanks)

Please try uninstall of visual micro with ide closed then re-install. The run the Ide and see what version and location is displayed under tools>options>visual micro>version>version and location

Thanks

Hello Tim,

The version is 1.1401.24, located  in C:\Program Files (x86)\Visual Micro\Visual Micro for Arduino\Visual.Micro.AS6.dll

Well - how should I say - I did the opposit of what you asked me to to - I added some more lcd.print statement till I got 100% - loading the sketch with VisualMicro-ArduinoIDE-1.0.x works well (without debugger enabled):
Compiling 'TerrariumSteuerung_V009' for 'Arduino Leonardo'
Build folder: 009/leonardo
Binary sketch size: 28670 bytes (used 100% of a 28672 byte maximum) (0.95 secs)
Uploading to I/O board using 'COM3'
Done uploading via 'COM4'

Then I deleted some lcd.print statements till I got 100% with VisualMicro-ArduinoIDE 1.0.x and debugger ON:
Compiling 'TerrariumSteuerung_V009' for 'Arduino Leonardo'
Build folder: 009/leonardo
Binary sketch size: 28238 bytes (used 98% of a 28672 byte maximum) (0.95 secs)
Compiling debug version of 'TerrariumSteuerung_V009' for 'Arduino Leonardo'
Build folder: 009/leonardo
Binary sketch size: 28672 bytes (used 100% of a 28672 byte maximum) (1.28 secs)
Uploading to I/O board using 'COM3'
Done uploading via 'COM4'

So - there is probably no problem to fill the Leonardo up to 100%... 

But there is still a difference betwen the calculation of used size (RAM and ROM) betwen VisualMicro-ArduinoIDE-1.5.x  and the nativ ArduinoIDE 1.5.5-rc2. 

The ArduinoIDE 1.5.5.-rc2 tells me:
Sketch uses 28,548 bytes (99%) of program storage space. Maximum is 28,672 bytes.
Global variables use 1,101 bytes (43%) of dynamic memory, leaving 1,459 bytes for local variables. Maximum is 2,560 bytes.

The VisualMicro-Arduino1.5.x-IDE tells me (for the exact same script):
Binary sketch size: 27986 bytes (used 98% of a 28672 byte maximum) (7.36 secs)
Minimum Memory Usage: 539 bytes (21% of a 2560 byte maximum)

-> VisualMicro calculates less RAM and ROM (ca. 500bytes each - and therefore is not aware that adding some more debuggin-code will overload the wagon...)

What are the differences in the calculation of the sizes?

Thank you for your assistenz. 
Thomas

Hello Tim,

I did some more testing on this.
The difference in size between VM and ArduinoIDE depends on the size of the sketch - but is not related to the size (so it's not the bigger the more...).
It doesn't matter wich Arduino board I use (same problem on a Arduino Uno  - no need to upload - just build the solution...)

But the strangest thing is:
the difference between RAM and ROM is allways RAMDiff=ROMDiff.
(the value differs from sketch to sketch)

Maybe you will explain me, what regex you are using and what input you get... 

Best regards
Thomas

Would you be able to email your sketch to info [at] visualmicro.com. It would help to have a full sketch to test with. Thanks

Nice work thanks. The size specification and calculation should be taken from the platform.txt file provided by the ArduinoIde. 

Below is the size instruction that Visual Micro should follow for avr processors (see arduinoIde/hardware/arduino/avr/platform.txt) 

recipe.size.pattern="{compiler.path}{compiler.size.cmd}" -A "{build.path}/{build.project_name}.elf"
recipe.size.regex=^(?:\.text|\.data|\.bootloader)\s+([0-9]+).*
recipe.size.regex.data=^(?:\.data|\.bss|\.noinit)\s+([0-9]+).*
recipe.size.regex.eeprom=^(?:\.eeprom)\s+([0-9]+).*
 

I notice the verbose compile option in the Visual Micro tools>options doesn't provide verbose detail for the size command. However if you switch on "compiler>show build properties" you should also find the recipe for the size routine in the output after compile.

You are right about the -A from the looks of things, I need to look at what is actually being returned. Maybe print the whole lot when verbose is on.

Thanks

Hello Tim,

... you allready knew it - and let me do the work... 

I`not too familiar with regex. Since there are multiple lines in the output that are to be summarized - does VM iterate through the output but is not aware of the need to summarize the different hits?
(VM has to read the whole output with one regex and summarize all hints, then it has to reread the output with the other regex)

Thomas