I've just downloaded the debugger and have the following feedback.

[pedantic mode]

The email says

Quote:

Hmm, properties window, normally I right click on an object and select "Properties", no mention of Micro Debug there though, guess I better try the VM site.

I find a page that under the "Simple Example" heading says

Quote:

Nothing happens. But now I notice the Properties tab, so on the assumption that it should also have said "and then select the 'Properties' tab" I do and now

Quote:


is an option. Good, that's done.

But before all that the web page says

Quote:

What part of the "Visual Studio tool bar"?

After searching all the menus I find "Build > Configuration manager...", it's already set to "Debug", looks like I'm off and racing.

Now the worst people in the world to write documentation are those that wrote the product, unfortunately there's not usually anyone else to do it but one really has to put oneself in beginner mode and take every word and every phrase literally. For example

Using the Visual Studio tool bar, change the configuration to "Debug"

What exactly does that mean? Taken literally is doesn't mean anything so the poor user is forced to look through a 1000 menus items.

[/pedantic mode]

Anyway, moving right along, the next step is to define a breakpoint but first I think a compile is in order.

The compile fails

Compiling 'Test' for 'Arduino Duemilanove w/ ATmega328'
Binary sketch size: 2386 bytes (of a 30720 byte maximum) (0.398 secs)
Compiling debug version of 'Test' for 'Arduino Duemilanove w/ ATmega328'
Test.pde : In file included from
VM_DBG.h : No such file or directory
VM_DBG.cpp : In file included from
VM_DBG.h : No such file or directory
VM_DBG.cpp : In file included from
VM_DBG.h : 'uint8_t' does not name a type
... 

And that's where I'm at.

Note this is VS2008 and Arduino 1.5

Any ideas?

______
Rob

Quote:

Yikes, 25 minutes, not on my data plan

I seem to have it installed, just doesn't compile.

Arduino are totally unresponsive to emails, I've tried many times and not had a single response.

I've done a lot of documentation work over the years and it ain't easy I admit, it's also VERY time consuming to do well so I feel your pain. I'm happy to help in small ways and I'm always evangelising the product on the Arduino forum, but I have a dual-processor board to get up and running plus maybe 20 plug in boards, not a lot of spare time I'm afraid. Thank goodness I don't have to work as well

Quote:

Is that the cause of my errors then?

______
Rob

I've downloaded and installed 1.0.2 but still can't compile. Errors same as before I think.

Compiling 'Test' for 'Arduino Duemilanove w/ ATmega328'

Binary sketch size: 1034 bytes (of a 30720 byte maximum) (0.541 secs)
Compiling debug version of 'Test' for 'Arduino Duemilanove w/ ATmega328'
Test.pde : In file included from
VM_DBG.h : No such file or directory
VM_DBG.cpp : In file included from
VM_DBG.h : No such file or directory
VM_DBG.cpp : In file included from
VM_DBG.h : 'uint8_t' does not name a type
VM_DBG.h : 'uint8_t' does not name a type
VM_DBG.h : 'byte' does not name a type
VM_DBG.h : 'uint8_t' does not name a type
VM_DBG.h : 'uint8_t' does not name a type
... 

Bottom line appears to be that it can't find VM_DBG.h, but then some of those errors appear to be in VM_DBG.h

So just as a work around I explicitly included both VM_DBG files

#include "C:\Program Files\Visual Micro\Visual Micro for Arduino\Micro Platforms\Arduino\Templates\Hardware\Debuggers\VM_DBG\VM_DBG.h"
#include "C:\Program Files\Visual Micro\Visual Micro for Arduino\Micro Platforms\Arduino\Templates\Hardware\Debuggers\VM_DBG\VM_DBG.cpp 

"

Spaces in the path seem OK because now it tries to compile the cpp file but still gets a lot of errors (different this time)

Compiling 'Test' for 'Arduino Duemilanove w/ ATmega328'
Test.pde : In file included from
VM_DBG.h : No such file or directory
Test.pde : In file included from
VM_DBG.h : : In member function 'void VisualMicroDebug::setVariable(T&, int, int)':
VM_DBG.h : 'transport' was not declared in this scope
VM_DBG.cpp : In file included from
Test.pde : from
VM_DBG.h : : At global scope:
VM_DBG.h : setVariable(T, int, long int)'
VM_DBG.h : setVariable(T, int, long int)' previously declared here
VM_DBG.h : setVariable(T, long int)'
VM_DBG.h : setVariable(T, long int)' previously declared here
VM_DBG.h : setVariable(T&, int, int)'
VM_DBG.h : setVariable(T&, int, int)' previously declared here
VM_DBG.h : setVariable(T&, int)'
VM_DBG.h : setVariable(T&, int)' previously declared here
Test.pde : In file included from
VM_DBG.cpp : : In member function 'void VisualMicroDebug::sendMessage(const char*)':
VM_DBG.cpp : 'transport' was not declared in this scope
VM_DBG.cpp : : In member function 'uint8_t VisualMicroDebug::readVariableTextDataType()':
VM_DBG.cpp : 'transport' was not declared in this scope
VM_DBG.cpp : : In member function 'uint8_t VisualMicroDebug::readVariableTextLength()':
VM_DBG.cpp : 'transport' was not declared in this scope
VM_DBG.cpp : : In function 'void no_lvalue_err()':
VM_DBG.cpp : 'class VisualMicroDebug' has no member named 'transport'
VM_DBG.cpp : : In member function 'void VisualMicroDebug::fetchVarData()':
VM_DBG.cpp : 'transport' was not declared in this scope
Error compiling
 

Obviously some things are previously declared which implies that the 

#ifndef _VM_DBG_
#define _VM_DBG_

protection isn't working to stop the h file being doubly included. So I remove the explicit h file include and things get a bit better

Continued next post, it's got too long

Please don't make any of these changes or try to fix it. 

We just need to look at what you have installed. It's a simple system that is working for many.

What version of vm do you have installed? "Tools>Options>Visual Micro>Version"

Thanks

ps: The only reason for moving from 1.5 to 1.0.x is that normal non-debug compile will work.  If normal compile works then the debugger will not object to the arduino version.

Thanks that's good info. I sounds like the debug beta upgrade is out of date. A new release was added to the debug page at the same time as 1211.04 was produced.

If this is not the case and you have the latest 3.3 beta upgrade installed, then please go to control panel>add or remove programs and uninstall the Visual Micro Debug Upgrade and then run the install again from the beta page. Sometimes the windows installer doesn't update files which would leave you with an older version of the VM_DBG cpp/h files

Thanks v much

ps: When the debugger is officially released it will be merged with the std plugin installer so the additional step to add the debug support files will no longer be required after each upgrade.