From: D N. <dny...@at...> - 2011-03-21 04:26:20
|
On 3/20/2011 7:04:52 PM, Karl Lunt (kar...@se...) wrote: > Exactly. I've never had good luck using any simulator, AVRStudio's > included. I much prefer to trust the real hardware, even if you > start out using an LED for debug. > > BTW, have you tried out AVRStudio5 yet? It was released just a few > weeks ago and from the release notes, it looks like an excellent > upgrade. > > Karl Well I first saw this effect while running on the hardware, using the dragon, and replicated it in the simulator to eliminate any possible faults in the dragon rider (as it's a newly soldered kit, and I don't much trust it yet). It manifested the same in both environments. I'm using JTAG with dragon; does anyone have data to the effect that this sort of glitch is jtag specific, ie one of the other debug interfaces might behave differently? I would think using simulator would eliminate that variable. I thought of trying 5, and may have to, but they made that one dependent on .net framework 4, which will not install on win2k, so only the xp machine runs that. I had hoped to be able to run the same toolchain at bench and desk. Why they chose to restrict the next version that way I don't know, but they can do whatever they want without my permission. :( If I'm stuck using 5, then that suxxorz, as I'll have to do most of my coding at the bench, rather than the more comfortable desk place. :( |