Hi I'm currently using the following:
Visual Studio 2013 (Ultimate)
Visual Micro 1412.10 Sp6 (registered)
Arduino Due
I've spotted a couple of bugs in relation to the serial console
1. For the first bug
with debug turned off
(Tools -> visual micro -> Auto debugging = unticked, Project properties -> Micro Debug = None)
I've noticed that the serial console window doesn't show data coming in from the board
if I just check the "Connect" tick box on it's own in the serial console window
If I also click on the blue / square button on the main toolbar (show the serial monitor tool window)
even if the window is already shown
then I start to see inbound data from the board via serial.print
this suggests there's some missing init code behind the "Connect" tickbox, which is called when clicking the
show serial console button
2. For the next bug
with debug turned on
(Tools -> visual micro -> Auto debugging = ticked, Project properties -> Micro Debug = Full)
If I hit the Debug button to trigger a compile and upload to the board
it seems to have problems disconnecting the serial console window from the previous session
(I have to manually disconnect in the serial console window before I can do a 2nd upload)
this doesn't seem to be the case with debug turned off
also if the device is physically disconnected while this is going on, this can cause visual studio to crash / bomb out
generally the serial comms seems more unstable with debugging turned on
at a guess it's related to the code that handles recieving breakpoints within VM
having debug turned off seems generally more stable serial wise than with it turned on
3. Colour theme
It looks like any VM WPF windows within Visual Studio use the default colours, instead of inheriting the
colours from the current visual studio set
(so if your using a black theme, you'll still get white / blue windows for the VM serial monitor for example)
that's probably just a bug in relation to WPF theme inheritance
Good work by the way, even without debugging this is a kick ass plugin for studio. Especially since studio now has git supportĀ
The next thing I'll be looking into is using a J-Link segger since the due is arm based, although to get that to work I'll probably have to use visual gdb if that works in this sort of setup.
One idea for the future would be to include gdb support so that you could single step / debug via segger's gdb server since the edu version is fairly cheap from adafruit (although it only works for arm)