Forum Replies Created
-
Posts
-
Hi. It’s VisualGDB 5.3 (build 1836).
p.s. I had already looked for an update check feature in the software itself. I saw (and tried) the “Upgrade” button but that seems to do something else. I know that devtool packages get occasional automatic updates, but I don’t think that applies to the software itself?
Oh – I forgot to mention that I confirmed that if I run VS2010 and open the solution explorer window before opening the solution, then I don’t get the error.
Wow, you’re quite right. Since I don’t use it myself I hadn’t noticed that the Arduino environment doesn’t include a debugger! I guess Arduino is less an IDE, more a place to plug in working code written and debugged by someone else. Oh well, thanks for your help – and in fact with these workarounds I’m now finding VisualGDB AVR support to be perfectly usable: I’ve been having a lot of fun these last few days checking out the sensors I bought for AVR and never found time to write code for.
Perfect, thank you – that’s exactly the sort of workaround I was hoping for (though I’m currently at work so the suggestion is not tested).
Incidentally, I made a discovery since my last post: the JTAGICEv2 has a power toggle switch on it: don’t ask me why, but it’s a godsend. After flashing the AVR I cycle power on the JTAGICEv2. This not only resets the JTAGICEv2 but it also resets my board, killing two birds with one stone: the setup is then ready for my next code iteration.
I’m still surprised by your comment that the underlying tools are unpopular. Are you referring only to the AVaRICE interface? Because of course the Arduino environment is very popular with beginners or so I understand (for me it’s too confining: I’m not a beginner), and that uses presumably pretty much the same toolchain with a different code generator backend – and the IDE of course.
One further feature of the problem: if I program the flash (getting the error), cancel the dialog and then hit reset on the board as instructed, then any subsequent attempt to program the flash or use the debugger will fail. I have to reset my devboard and cycle the power on the JTAGICEv2. So it looks like it’s leaving the JTAGICEv2 in some unexpected state.
Hi. Thanks for replying.
That’s a shame about AVR support being a lower priority, I thought that with the popularity of Arduino, 3D printing, etc that would not be the case. I understand your position however – I just thought it neat that I could use one environment (Visual Studio + VisualGDB) for all three of the development types I’m currently doing: Windows, STM32 and AVR (ATmegaXXX).
Re your question. If I use “Debug | Start Debugging” then the debugger seems to launch normally, without error message… Hmm. Let me just verify that it did actually load new code when I did that… Yes, it definitely programs the flash. So I only get the error message when I use “Debug | Program and Start Without Debugging”.
Incidentally, the last few lines in the GDB log says :-
mon detach
&”mon detach\n”
&”Target does not support this command.\n”
^error,msg=”Target does not support this command.”You raise a point that I hadn’t considered, though it seems obvious in hindsight. I’ve only recently migrated from devices (AD Blackfin) where the code loads from external flash to internal SRAM, so I’m not used to a debug image loaded by JTAG overwriting the flash. Good to know! Is it the intention that when you exit the debugger the original flash image is supposed to be restored?
