I haven't had any problems with USB power.
I've run it directly off my desktop and my dell d620 laptop and an acer netbook,
but I never use the dragon to power the target circuit and I've not done any
HV programming.
I also use a 3 foot cable. I'd use shorter if I could find a shorter one.
Maybe the cable was the real issue?
pico:
What are the 6 lines of code needed to get avrdude able to work under the Arduino IDE with the Dragon? It's just for SPI programming mode, I'd guess, or can it be configured by avrdude options to do HV programming as well?
Its an interaction with USB enumeration and how the IDE uses ide.
The IDE does 2 avrdude commands instead of one and avrdude resets the USB when it exits.
Have a read of the bug report for the details.
Anyway, thanks for your help. How come lots of people aren't doing this???
Ignorance and Laziness.....
I presume mostly it is from a lack of understanding of available development tools
from years of using Windows.
It is also a total pain to use with the Arduino IDE - But then the Arduino is a pain to use
anyway for anything but simple sketch builds because of the build methodology they used.
It tends to force you into their way of doing things which has many limitations.
If the IDE had done things a bit differently not only would it have been simpler to implement
but it would have been able to easily interface with external tools like debuggers
all without making the novice user experience any different from what it is today.
At least with the 1.5 version of the IDE and its configuration capabilities,
it looks like it will be possible and won't be that difficult to create an uploader script
that can upload the code as well as bring up all the debugger tools from the Arduino IDE.
(Well, at least on non Windows environments).
I just had a discussion with some folks on another thread about
using source level debugging vs "print" and "led" debugging.
To me, for any serious development work,
part of getting your environment set up is to get the
debugging environment up and working and that means
getting gdb working.
using LEDs and debug prints does have its place but those needs
are quite rare.
I still see many people including in their professional work careers
using "printf" style debugging on their projects.
The same types of things could be said for not using a
source control system.
--- bill