Windows 7 Pro x64
VS 2010 - 10.0.30319.1 RTMrel
Arduino 1.0.1

when compiling existing sketch with debugger I am getting

===

Compiling 'Version_1_xnp_uno_Temp' for 'Arduino Uno'
Binary sketch size: 17866 bytes (of a 32256 byte maximum) (1.6958223 secs)
Compiling debug version of 'Version_1_xnp_uno_Temp' for 'Arduino Uno'
Version_1_xnp_uno_Temp.ino : In function 'void setup()'
Version_1_xnp_uno_Temp.ino : 'MicroDebug' was not declared in this scope
Error compiling 

====

if I create a new sketch it seems to work though..

any ideas?

still doesn't compile with the old sketch after Build, Clean Solution.   

I just copy and pasted into a new project from with in VS and it compiles successfully.

running is another matter, I can debug simple sketches, but some of my bigger ones dont even start after compiling and uploading.

should I be developing on a Mega to get the extra horsepower?

Email sent..

xml file from the sketch that does not compile, and the sketch that does compile but has issues running..

Thanks..

Got all the files thanks.

From your config I can see the following:-

1) You have the local debug port set to COM3. 

2) You are expecting the debug to use the main arduino "Serial" for debug (which is also upload port). I can see this because the RemotePort and RemoteTansport properties are empty therefore using the defaults.

Are you sure that COM3 is the correct port?, if not clear out COM3 from the project properties and the debug will default to whatever you are using for an upload port.

In my test of your project, I cleared COM3 and added a breakpoint to the loop() function. After debug upload I could correctly see trace messages.

By the way in terms of memory usage, the debug stuff has added very little extra memory and your sketch is still well within the limits of a 328/uno type chip. No mega required. Your sketch is 17850 bytes without debug and 18044 bytes with debug + a single breakpoint. So you have plenty of room for more code and more breakpoints. The limit of a 328 is 30720 bytes.

Let me know how you get on or if I am missing the point.

Thanks

Yes it's just re-booting all the time, something is going wrong just after the "void setup() {"

I need you to explain which settings you have changed and where you have placed breakpoints with what properties. OR, It might be easier for you to zip and email the sketch folder (and sub folders). You also need to include the visual studio solution files that contain your project (.sln and.slo) because the breakpoints are stored in the solution.

Thanks

Thanks for the files they were very useful.

I think I've got to the bottom of the problems, when you asked about memory the other day I should have given it more thought.

This certainly appears to be memory related but it easily fixed. Once we fix the memory issues we can see if vm is working correctly in a shared serial senario, if not it can be addressed.

I used the new memory reporting options that are standard in the next release to discover that all of your manual debug messages have nearly blown the 2048Kb limit on your arduino (see below). 

You are so close to the limit that even in "release" (normal) mode your program soon starts to fail with a a few more serial.print("big string") calls.

Switching on vm debug currently has a fixed overhead of about 40 bytes + each breakpoint can consume further bytes. 

A simple visual micro breakpoint with a "When Hit" message will consume 8 bytes REGARDLESS of the length of the text in the message. Adding {expressions} will consume a few bytes per expression.

In your sketch the code after the "hihi" message can  causes extra memory bytes to be consumed by the arduino which, with debug enabled, can just push things over the limit and cause the arduino to crash.

Commenting out the following two unrelated but memory consuming lines in your program stopped the crash.

Serial.println("CRC is not valid!");
Serial.print("Device is not recognized"); 

Below are the memory reports for release and debug compilations...

Compiling release version of 'XNP_TEMP_V2' for 'Arduino Duemilanove w/ ATmega328'

Data:       1892 bytes (92.4% Full)

Compiling debug version of 'XNP_TEMP_V2' for 'Arduino Duemilanove w/ ATmega328'

Data:       1932 bytes (94.3% Full)

Solutions

I can see two possible solutions

1) 

Move all your "strings" to using PROGMEM memory(limited to 1kb I think)

OR

2) 

Swap out all your Serial.print() manual debug stuff for Visual Micro breakpoints using the "When Hit" property for nicely formatted information messages. Doing so should save you about 1800 bytes of memory out of 2048

Don't forget that you can add multiple {expressions} and/or  text into the "When Hit" breakpoint property. So a single breakpoint might tell a big story.

You can also format your expressions as required. 

Example:-

Function xyz has returned {myExpression,HEX} and x={expression1/expression2}

Thanks for the update. I enjoyed using the memory checker that Joe Sto recommended to solve this puzzle

If you read this thread you see the AVR Memory Report that can be optional enabled. The report shows how much memory has been consumed immediately after compile, prior to upload.

http://www.visualmicro.com/forums/YaBB.pl?num=1330632829

More recent posts in the same thread shows an additional graphical view of real-time available memory (via the debugger) while the arduino is running.

I used the memory report (after compile) option to see how much memory your program was using. 

Commenting or adding strings and clicking compile immediately showed the impact of the code changes.

+ When building a debug version you get to see both memory reports (release and debug) so we can clearly see the overhead of the debugger.